[24985] in Perl-Users-Digest
Perl-Users Digest, Issue: 7235 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 12 14:16:56 2004
Date: Tue, 12 Oct 2004 11:15:15 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 12 Oct 2004 Volume: 10 Number: 7235
Today's topics:
Re: reading a list of files (Gerhard M)
Re: reading a list of files (Gerhard M)
Re: reducing regex to common function name <toreau@gmail.com>
regex: match at least one of two expression <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Re: regex: match at least one of two expression (Gerhard M)
Re: regex: match at least one of two expression <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Re: regex: match at least one of two expression <usa1@llenroc.ude.invalid>
Re: regex: match at least one of two expression <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Re: regex: match at least one of two expression <usa1@llenroc.ude.invalid>
Re: regex: match at least one of two expression <usenet@morrow.me.uk>
Re: regex: match at least one of two expression (Anno Siegel)
Re: regex: match at least one of two expression <nobull@mail.com>
Re: Top 10 list algorithm (Anno Siegel)
Re: Using a string as a variable name. <uri@stemsystems.com>
Re: Using a string as a variable name. <uri@stemsystems.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 12 Oct 2004 00:28:21 -0700
From: notruf_1102003@yahoo.de (Gerhard M)
Subject: Re: reading a list of files
Message-Id: <942c5b0d.0410112328.78995e8@posting.google.com>
john_williams4321@hotmail.com (john williams) wrote in message news:<298e5c19.0410040652.4a8732e2@posting.google.com>...
> ....
> due to the large number of files, I need this to be automated.
# ls basename* | perl -ne 'chomp; /(.*)\_(.*)/ && {print "YOUR_CMD $_
> $1_out_$2\n" | sh
------------------------------
Date: 12 Oct 2004 00:29:51 -0700
From: notruf_1102003@yahoo.de (Gerhard M)
Subject: Re: reading a list of files
Message-Id: <942c5b0d.0410112329.2accb19d@posting.google.com>
john_williams4321@hotmail.com (john williams) wrote in message news:<298e5c19.0410040652.4a8732e2@posting.google.com>...
> ....
> due to the large number of files, I need this to be automated.
# ls basename* | perl -ne 'chomp; /(.*)\_(.*)/ && {print "YOUR_CMD $_
> $1_out_$2\n";}' | sh
------------------------------
Date: Mon, 11 Oct 2004 10:25:14 +0200
From: Tore Aursand <toreau@gmail.com>
Subject: Re: reducing regex to common function name
Message-Id: <pan.2004.10.11.08.25.14.247284@gmail.com>
On Sat, 09 Oct 2004 13:37:34 -0700, Thomas Randall wrote:
> $out =~ s/^\s*//;
> $out =~ s/\s*$//;
>
> These two lines will trim white space from the front and back of the
> string $out.
I would say that the regular expression is slightly wrong, although it
will work perfectly.
What you really want is something which removes _one or more_ whitespaces
from the front and/or the back of the string;
$out =~ s/^\s+//;
$out =~ s/\s+$//;
--
Tore Aursand <toreau@gmail.com>
"A teacher is never a giver of truth - he is a guide, a pointer to the
truth that each student must find for himself. A good teacher is
merely a catalyst." (Bruce Lee)
------------------------------
Date: Tue, 12 Oct 2004 09:07:27 GMT
From: Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Subject: regex: match at least one of two expression
Message-Id: <j9Nad.276377$jh6.14216310@phobos.telenet-ops.be>
Hi,
I am trying to build a regex expression that holds two expressions, and
I'd like the main expression to match if at least one of those two
sub-expressions match, or if they both match. I am using this to parse
URL's.
Example URL's:
/brand/hpe/category/wi (catch this)
/brand/hpe (catch this)
/category/wi/brand/hpe (catch this)
/category/wi (catch this)
/otherpage (do not catch this)
the only thing i came up with is this huge thing:
(\/brand\/(\w)+)|(\/category\/(\w)+)|(\/category\/(\w)+\/brand\/(\w)+)|(\/brand\/(\w)+\/category\/(\w)+)
So a URL is built up of a brand section, a category section or both. Is
there a better way to capture those 4 possible URL's than the expression
I came up with?
thanks a lot,
Vincent
------------------------------
Date: 12 Oct 2004 09:40:57 -0700
From: notruf_1102003@yahoo.de (Gerhard M)
Subject: Re: regex: match at least one of two expression
Message-Id: <942c5b0d.0410120840.5240d52@posting.google.com>
Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in message news:<j9Nad.276377$jh6.14216310@phobos.telenet-ops.be>...
> Example URL's:
> /brand/hpe/category/wi (catch this)
> /brand/hpe (catch this)
> /category/wi/brand/hpe (catch this)
> /category/wi (catch this)
> /otherpage (do not catch this)
what's up with
/brand/xx/category/yy/yy1
and
/brand/xx/category
and
/category/xx/
ignoring above remarks
this one will be a possible way:
my $p="brand|category";
if (m#^/($p)/(\w+)($|/($p)/(\w+)$)#) {
# may you wana check check $1 to $5
your_code($_);
}
gerhard
------------------------------
Date: Tue, 12 Oct 2004 14:41:49 GMT
From: Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Subject: Re: regex: match at least one of two expression
Message-Id: <N2Sad.276571$%43.14126211@phobos.telenet-ops.be>
Brian McCauley wrote:
>
>
> Vincent Mouton wrote:
>
>> I am trying to build a regex expression that holds two expressions,
>> and I'd like the main expression to match if at least one of those two
>> sub-expressions match, or if they both match.
>
>
> /This|That/
>
>> Example URL's:
>> /brand/hpe/category/wi (catch this)
>> /brand/hpe (catch this)
>> /category/wi/brand/hpe (catch this)
>> /category/wi (catch this)
>> /otherpage (do not catch this)
>>
>> the only thing i came up with is this huge thing:
>>
>> (\/brand\/(\w)+)|(\/category\/(\w)+)|(\/category\/(\w)+\/brand\/(\w)+)|(\/brand\/(\w)+\/category\/(\w)+)
>
>
>
> I suspect there's more to what you are wanting than you originally told
> us. I suspect when you say 'catch' you mean 'capture'.
>
>> So a URL is built up of a brand section, a category section or both.
>> Is there a better way to capture those 4 possible URL's than the
>> expression I came up with?
>
>
> If you can assume that you don't mind if you also capture repeated brand
> or category then it simplifes a lot.
>
> /((\/(brand|category)\/\w+)+)/
>
>
Hi,
thank You. It seems obvious, but i didn't think of it this way. And yes,
that does help me a great deal. It's much cleaner. I don't mind catching
repeated brand or category. I know the URL i will check using this regex
will always be one of the 5 examples i gave.
Thank you and thanks Anno for taking time to look into this.
vincent
------------------------------
Date: 12 Oct 2004 14:53:12 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: regex: match at least one of two expression
Message-Id: <Xns95806F05FC314asu1cornelledu@132.236.56.8>
Vincent Mouton
<vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in
news:j9Nad.276377$jh6.14216310@phobos.telenet-ops.be:
> I am trying to build a regex expression that holds two expressions,
> and I'd like the main expression to match if at least one of those two
> sub-expressions match, or if they both match. I am using this to parse
> URL's.
>
> Example URL's:
> /brand/hpe/category/wi (catch this)
> /brand/hpe (catch this)
> /category/wi/brand/hpe (catch this)
> /category/wi (catch this)
> /otherpage (do not catch this)
Do you want:
/otherpage/brand/hpe/category
as well?
Sinan
------------------------------
Date: Tue, 12 Oct 2004 15:07:02 GMT
From: Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>
Subject: Re: regex: match at least one of two expression
Message-Id: <qqSad.276607$B75.14193702@phobos.telenet-ops.be>
A. Sinan Unur wrote:
> Vincent Mouton
> <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in
> news:j9Nad.276377$jh6.14216310@phobos.telenet-ops.be:
>
>
>>I am trying to build a regex expression that holds two expressions,
>>and I'd like the main expression to match if at least one of those two
>>sub-expressions match, or if they both match. I am using this to parse
>>URL's.
>>
>>Example URL's:
>>/brand/hpe/category/wi (catch this)
>>/brand/hpe (catch this)
>>/category/wi/brand/hpe (catch this)
>>/category/wi (catch this)
>>/otherpage (do not catch this)
>
>
> Do you want:
>
> /otherpage/brand/hpe/category
>
> as well?
>
> Sinan
Hi,
No. Only the first 4 matches.
greetings,
Vincent
------------------------------
Date: 12 Oct 2004 15:43:57 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: regex: match at least one of two expression
Message-Id: <Xns9580779FE790asu1cornelledu@132.236.56.8>
Vincent Mouton
<vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in
news:qqSad.276607$B75.14193702@phobos.telenet-ops.be:
> A. Sinan Unur wrote:
>> Vincent Mouton
>> <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in
>> news:j9Nad.276377$jh6.14216310@phobos.telenet-ops.be:
>>>Example URL's:
>>>/brand/hpe/category/wi (catch this)
>>>/brand/hpe (catch this)
>>>/category/wi/brand/hpe (catch this)
>>>/category/wi (catch this)
>>>/otherpage (do not catch this)
>> Do you want:
>>
>> /otherpage/brand/hpe/category
>>
>> as well?
..
> No. Only the first 4 matches.
I am a little confused, so the following might be completely irrelevant. It
seems to me that one would like to know, upon a succesful match, whether
one matched a category or a brand or both and which one is which. In that
case, I would be inclined to write that out in full:
#! perl
use strict;
use warnings;
use Data::Dumper;
my @s = qw(
/brand/hpe/category/wi
/brand/hpe
/category/wi/brand/hpe
/category/wi
/otherpage
);
for my $s (@s) {
if(my $r = extract_brand_category($s)) {
print Dumper $r;
}
}
sub extract_brand_category {
my $s = shift;
my %r;
if($s =~ m{^/(brand)}) {
$r{brand} = $1;
if($s =~ m{/(category)/}) {
$r{category} = $1;
}
} elsif($s =~ m{^/(category)}) {
$r{category} = $1;
if($s =~ m{/(brand)/}) {
$r{brand} = $1;
}
}
return \%r if %r;
return;
}
__END__
I know it does not look as neat as a mind-blowing one-line regex, but I
leave that to experts.
Sinan.
------------------------------
Date: Tue, 12 Oct 2004 12:57:54 +0100
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: regex: match at least one of two expression
Message-Id: <2fts32-cl5.ln1@osiris.mauzo.dyndns.org>
Quoth Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe>:
> Hi,
>
> I am trying to build a regex expression that holds two expressions, and
> I'd like the main expression to match if at least one of those two
> sub-expressions match, or if they both match. I am using this to parse
> URL's.
>
> Example URL's:
> /brand/hpe/category/wi (catch this)
> /brand/hpe (catch this)
> /category/wi/brand/hpe (catch this)
> /category/wi (catch this)
> /otherpage (do not catch this)
>
> the only thing i came up with is this huge thing:
>
> (\/brand\/(\w)+)|(\/category\/(\w)+)| # regex wrapped
> (\/category\/(\w)+\/brand\/(\w)+)|
> (\/brand\/(\w)+\/category\/(\w)+)
Perl supports other delimiters so's you don't need all those \/s.
> So a URL is built up of a brand section, a category section or both. Is
> there a better way to capture those 4 possible URL's than the expression
> I came up with?
I'd use Perl instead of regexen.
my ($brand, $category);
if (($brand) = $uri =~ m{/brand/(\w+)}g or
($category) = $uri =~ m{/category/(\w+)}g
){
# do stuff with $brand, $category
}
Ben
--
We do not stop playing because we grow old;
we grow old because we stop playing.
ben@morrow.me.uk
------------------------------
Date: 12 Oct 2004 11:02:09 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: regex: match at least one of two expression
Message-Id: <ckgdjh$ec6$1@mamenchi.zrz.TU-Berlin.DE>
Vincent Mouton <vincentNOSPAMPLEASE_SOREMOVETHIS@marlon.andthentheextentionbe> wrote in comp.lang.perl.misc:
> Hi,
>
> I am trying to build a regex expression that holds two expressions, and
> I'd like the main expression to match if at least one of those two
> sub-expressions match, or if they both match. I am using this to parse
> URL's.
>
> Example URL's:
> /brand/hpe/category/wi (catch this)
> /brand/hpe (catch this)
> /category/wi/brand/hpe (catch this)
> /category/wi (catch this)
> /otherpage (do not catch this)
>
> the only thing i came up with is this huge thing:
>
> (\/brand\/(\w)+)|(\/category\/(\w)+)|(\/category\/(\w)+\/brand\/(\w)+)|(\/brand\/(\w)+\/category\/(\w)+)
You don't have to escape "/" when you use alternative delimiters for
the regex.
> So a URL is built up of a brand section, a category section or both. Is
> there a better way to capture those 4 possible URL's than the expression
> I came up with?
It really depends what you want out of the match. I see capturing
parentheses, but it isn't clear how you are going to use the captures.
I'd break the regex down to its elementary parts and combine matches
in an if/else structure. That way, each regex is simple, and you
get to deal with the four different cases in four different code
branches.
if ( m{/brand/\w+}g ) {
if ( m{/category}g ) {
print "$_: brand & category\n";
} else {
print "$_: brand only\n";
}
} elsif ( m{/category/\w+}g ) {
if ( m{/brand} ) {
print "$_: category and brand\n";
} else {
print "$_: category only\n";
}
}
Note how //g is used to let each secondary match start where the
first one has left off.
Anno
------------------------------
Date: Tue, 12 Oct 2004 12:53:31 +0100
From: Brian McCauley <nobull@mail.com>
Subject: Re: regex: match at least one of two expression
Message-Id: <ckggba$opr$1@sun3.bham.ac.uk>
Vincent Mouton wrote:
> I am trying to build a regex expression that holds two expressions, and
> I'd like the main expression to match if at least one of those two
> sub-expressions match, or if they both match.
/This|That/
> Example URL's:
> /brand/hpe/category/wi (catch this)
> /brand/hpe (catch this)
> /category/wi/brand/hpe (catch this)
> /category/wi (catch this)
> /otherpage (do not catch this)
>
> the only thing i came up with is this huge thing:
>
> (\/brand\/(\w)+)|(\/category\/(\w)+)|(\/category\/(\w)+\/brand\/(\w)+)|(\/brand\/(\w)+\/category\/(\w)+)
I suspect there's more to what you are wanting than you originally told
us. I suspect when you say 'catch' you mean 'capture'.
> So a URL is built up of a brand section, a category section or both. Is
> there a better way to capture those 4 possible URL's than the expression
> I came up with?
If you can assume that you don't mind if you also capture repeated brand
or category then it simplifes a lot.
/((\/(brand|category)\/\w+)+)/
------------------------------
Date: 11 Oct 2004 08:15:32 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Top 10 list algorithm
Message-Id: <ckdff4$cis$1@mamenchi.zrz.TU-Berlin.DE>
Shawn Corey <shawn.corey@sympatico.ca> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
> > I still think that in practice it would pay to keep the heap size down
> > to k (the number of elements to be extracted). You'd still have to
> > *inspect* all the input, but the number of "heap operations" (heap
> > insertions and original (non-recursive) calls to heapify()) would be
> > much smaller, and operate on a smaller heap.
> >
> > Anno
>
> Unfortunately, no. I wrote some benchmarks just to see what happens in
> practice. The subroutine heap_each() is commented out since it takes so
> long to complete.
Then there must be something wrong with the implementation. My
benchmark (see below) shows the "small-heap" solution I suggested
about 8 times faster than Abigail's "big-heap" solution.
Anno
The benchmark compares Abigail's top-ten extraction with a bottom-ten
extraction using a small heap. Otherwise, implementations of both
a maximum-heap and a minimum heap would have been needed. To make the
results comparable, I'm feeding Abigail's solution with the negatives
of the same numbers I'm using for mine.
#!/usr/local/bin/perl
use strict; use warnings; $| = 1;
use Vi::QuickFix;
use Benchmark;
use constant N => 100_000;
use constant SIZE => 10;
sub _heapify;
my @heap;
my $count;
our @raw = map int rand 1_000_000, 1 .. N;
bench: {
@heap = map -$_, @raw;
timethis 1, \ &abigail;
print "Heap operations: $count\n";
timethis 1, \ &anno;
print "Heap operations: $count\n";
}
exit;
sub anno {
@heap = ();
$count = 0;
for ( @raw ) {
if ( @heap < SIZE or $_ < $heap[ 0] ) {
insert( $_);
extract_max() if @heap > SIZE;
}
}
print extract_max(), "\n" while @heap;
}
sub abigail {
$count = 0;
for (my $i = int (@heap / 2); $i >= 0; $i --) {_heapify $i; $count ++}
print extract_max(), "\n" for 1 .. 10;
}
###############################################################
sub count { print "count: $count\n" }
sub extract_max {
return unless @heap;
my $max = shift @heap;
if ( @heap > 1 ) {
unshift @heap, pop @heap;
$count ++;
_heapify( 0);
}
$max;
}
sub insert {
my $x = shift;
my $i = @heap;
$count ++;
while ( $i > 0 ) {
my $parent = int( ($i - 1)/2);
last if $heap[ $parent] >= $x;
$heap[ $i] = $heap[ $parent];
$i = $parent;
}
$heap[ $i] = $x;
}
sub _heapify {
my $i = shift;
my ( $l, $r) = ( 2*$i + 1, 2*$i + 2);
my $max = $i;
$max = $l if $l < @heap and $heap[ $l] > $heap[ $max];
$max = $r if $r < @heap and $heap[ $r] > $heap[ $max];
if ( $max != $i ) {
@heap[ $i, $max] = @heap[ $max, $i];
_heapify( $max);
}
}
------------------------------
Date: Tue, 12 Oct 2004 02:43:28 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Using a string as a variable name.
Message-Id: <x73c0kmzd2.fsf@mail.sysarch.com>
>>>>> "EJR" == Eric J Roode <sdn.girths00869@zoemail.net> writes:
EJR> Dan Jones <usenet@riddlemaster.org> wrote in
EJR> news:JLydndLDt-SG__XcRVn-sA@speakeasy.net:
>> Uri Guttman wrote:
>>
>>>>>>>> "EJR" == Eric J Roode <sdn.girths00869@zoemail.net> writes:
>>>
>>> >> Is it possible?
>>>
EJR> Strange that you could figure out how to print the indirect
>>> value EJR> out, but you couldn't figure out how to assign
>>> indirectly. :-)
>>>
EJR> ${$v1} = "it worked!";
>>>
>>>
>>> strange that you should know better than to give a symref answer
>>> without all the usual caveats on how dangerous and wrong it is.
>>>
>>> $hash{$v1} = 'better than just working!' ;
EJR> Okay, I take it back, Uri.
EJR> Dan:
EJR> It is a FAQ; pointers to the FAQ are posted here regularly, and can
EJR> be found by a quick google search, or (iirc) at rtfm.mit.edu.
EJR> In short: using a hash instead of variable-names-as-a-variable is far
EJR> superior for several reasons. The hash is neater (it's one data
EJR> structure instead of multiple); it encapsulates the data in one neat
EJR> package, and allows it to be hidden better within a subroutine or an
EJR> object (insofar as Perl allows data to be hidden) (Encapsulation and Data
EJR> Hiding are two important concepts in modern computer science); the
EJR> variable-name approach can often lead to hard-to-find bugs due to typos
EJR> and bad logic.
EJR> No experienced Perl programmer uses variables as variable names
EJR> except in those rare situations when no other approach will work.
EJR> (Better, Uri? ;-) )
better but not perfect!
you should have hunted down all copies of your erroneous post and
deleted them and burned all the disks that even carried it.
:-)
and the rule for symrefs is simple. ONLY use symrefs when you NEED to
mung the symbol table. they have no other purpose and regular hashes
are better in every way for munging data.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Tue, 12 Oct 2004 02:45:06 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Using a string as a variable name.
Message-Id: <x7zn2slkpv.fsf@mail.sysarch.com>
>>>>> "EJR" == Eric J Roode <sdn.girths00869@zoemail.net> writes:
EJR> Uri Guttman <uri@stemsystems.com> wrote in
EJR> news:x78yafpnbc.fsf@mail.sysarch.com:
>>>>>>> "EJR" == Eric J Roode <sdn.girths00869@zoemail.net> writes:
>>
>> >> Is it possible?
>>
EJR> Strange that you could figure out how to print the indirect value
EJR> out, but you couldn't figure out how to assign indirectly. :-)
>>
EJR> ${$v1} = "it worked!";
>>
>>
>> strange that you should know better than to give a symref answer without
>> all the usual caveats on how dangerous and wrong it is.
>>
>> $hash{$v1} = 'better than just working!' ;
EJR> Aw, Uri, you're not letting me have any fun! ;-)
EJR> Actually, I didn't feel it necessary, since others had already
EJR> given good reasons not to do so (and to read the FAQ).
but he may have read your post first. or someone may find it in
google. if strict were on by default (other than for one liners) we
wouldn't have this newbie use of symref syndrome.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 7235
***************************************
