[23428] in Perl-Users-Digest
Perl-Users Digest, Issue: 5645 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 10 18:10:42 2003
Date: Fri, 10 Oct 2003 15:10:14 -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 Fri, 10 Oct 2003 Volume: 10 Number: 5645
Today's topics:
string splitting question <sf_94133@yahoo.com>
Re: string splitting question <cenxnfu@rpr.nevmban.rqh>
Re: string splitting question (NO_SPAM)
Re: string splitting question <usenet@expires12.2003.tinita.de>
Re: string splitting question <usenet@dwall.fastmail.fm>
Re: string splitting question <tore@aursand.no>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: Teach me how to fish, regexp <henryn@zzzspacebbs.com>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 10 Oct 2003 12:40:23 -0500
From: "Emily Beylor" <sf_94133@yahoo.com>
Subject: string splitting question
Message-Id: <bm6qse$1bo2@george.sabre.com>
I have a path string (/usr/local/bin/file.10102003) that I want to split
into a $path and $file section as well as a $date section.
I'm able to get the $path and $file information (perhaps not very elegantly,
but still) as follows:
while(/\//g) {
$position = pos();
}
$getFile = substr($_, $position, length($_));
$getPath = substr($_, 0, $position);
I'm not sure how to get the $date information from the $file name. I've
tried with the following code, but it doesn't work:
$_=$getFile;
@a = m/([\d]+)/g;
print "@a\n";
How do I get the date information out of vi.10102003 to a representation of
$date = 10/10/2003 ?
Thanks
EB.
------------------------------
Date: Fri, 10 Oct 2003 12:09:13 -0700
From: Jayaprakash Rudraraju <cenxnfu@rpr.nevmban.rqh>
Subject: Re: string splitting question
Message-Id: <Pine.GSO.4.50.0310101207300.25659-100000@shellfish.ece.arizona.edu>
#!perl
while(<DATA>) {
/([^\/]*)$/;
($path, $file, $date) = ($`, split(/\./, $1));
print "$path $file ", join ('/', $date =~ /^(\d\d)(\d\d)(\d+)$/);
}
__DATA__
/usr/local/bin/file.10102003
12:40pm, IP packets from Emily Beylor delivered:
> I have a path string (/usr/local/bin/file.10102003) that I want to split
> into a $path and $file section as well as a $date section.
>
> I'm able to get the $path and $file information (perhaps not very elegantly,
> but still) as follows:
>
> while(/\//g) {
> $position = pos();
> }
>
> $getFile = substr($_, $position, length($_));
> $getPath = substr($_, 0, $position);
>
> I'm not sure how to get the $date information from the $file name. I've
> tried with the following code, but it doesn't work:
>
> $_=$getFile;
> @a = m/([\d]+)/g;
> print "@a\n";
>
>
> How do I get the date information out of vi.10102003 to a representation of
> $date = 10/10/2003 ?
>
> Thanks
>
> EB.
>
>
>
--
echo cenxnfu@rpr.nevmban.rqh | perl -pe 'y/A-Za-z/N-ZA-Mn-za-m/'
T h i s t a g l i n e h a s b e e n u n z i p p e d .
------------------------------
Date: Fri, 10 Oct 2003 15:16:09 -0400
From: "Kris Wempa" <calmincents(NO_SPAM)@yahoo.com>
Subject: Re: string splitting question
Message-Id: <bm7093$r086@kcweb01.netnews.att.com>
"Emily Beylor" <sf_94133@yahoo.com> wrote in message
news:bm6qse$1bo2@george.sabre.com...
> I have a path string (/usr/local/bin/file.10102003) that I want to split
> into a $path and $file section as well as a $date section.
>
> I'm able to get the $path and $file information (perhaps not very
elegantly,
> but still) as follows:
>
> while(/\//g) {
> $position = pos();
> }
>
> $getFile = substr($_, $position, length($_));
> $getPath = substr($_, 0, $position);
>
This is a lot of unnecessary work. Assuming your full path filename is in
$str , you can use this:
if ($str =~ /\/([^\/]+)$/) {
$filename = $1; # file is everything BETWEEN the first set of
parentheses
$dirname = $`; # dir is everything BEFORE the matched pattern
}
> I'm not sure how to get the $date information from the $file name. I've
> tried with the following code, but it doesn't work:
>
> $_=$getFile;
> @a = m/([\d]+)/g;
> print "@a\n";
>
>
> How do I get the date information out of vi.10102003 to a representation
of
> $date = 10/10/2003 ?
Using the results stored in $filename, just do something like this:
if ($filename =~ /(\d\d)(\d\d)(\d\d\d\d)/) {
$date = "$1/$2/$3";
}
I'm sure there's simpler ways, but this comes to mind quickly.
------------------------------
Date: 10 Oct 2003 19:42:51 GMT
From: Tina Mueller <usenet@expires12.2003.tinita.de>
Subject: Re: string splitting question
Message-Id: <bm723r$imhnm$1@ID-24002.news.uni-berlin.de>
Emily Beylor wrote:
> I have a path string (/usr/local/bin/file.10102003) that I want to split
> into a $path and $file section as well as a $date section.
as another suggestion: to make this portable, you might want to
have a look at File::Spec and splitpath()
hth, tina
--
http://www.tinita.de/ \ enter__| |__the___ _ _ ___
http://Movies.tinita.de/ \ / _` / _ \/ _ \ '_(_-< of
http://www.perlquotes.de/ \ \ _,_\ __/\ __/_| /__/ perception
-my address is currently unreachable due to the Swen.A virus-
------------------------------
Date: Fri, 10 Oct 2003 19:50:27 -0000
From: "David K. Wall" <usenet@dwall.fastmail.fm>
Subject: Re: string splitting question
Message-Id: <Xns9410A124A973Cdkwwashere@216.168.3.30>
Tina Mueller <usenet@expires12.2003.tinita.de> wrote:
> Emily Beylor wrote:
>> I have a path string (/usr/local/bin/file.10102003) that I want
>> to split into a $path and $file section as well as a $date
>> section.
>
> as another suggestion: to make this portable, you might want to
> have a look at File::Spec and splitpath()
Or File::Basename
------------------------------
Date: Fri, 10 Oct 2003 22:51:57 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: string splitting question
Message-Id: <pan.2003.10.10.19.43.24.547429@aursand.no>
On Fri, 10 Oct 2003 12:09:13 -0700, Jayaprakash Rudraraju wrote:
> while(<DATA>) {
> /([^\/]*)$/;
> ($path, $file, $date) = ($`, split(/\./, $1));
> print "$path $file ", join ('/', $date =~ /^(\d\d)(\d\d)(\d+)$/);
> }
Excellent, indeed. I would have, however chosen a _slightly_ different
approach.
Wouldn't it be more "foolproof" to use File::Basename's fileparse() method
to get the a) path, b) filename, and c) the suffix (ie. the date)?
In that case;
#!/usr/bin/perl
#
use strict;
use warnings;
use File::Basename qw( fileparse );
while ( <DATA> ) {
my ($path, $filename, $suffix) = fileparse( $_ );
my $date = join('/', $suffix =~ /^(\d{2})(\d{2})(\d+)$/ );
}
Just my thought of using already existing modules, and in this case be
sure that your code works even when being run on an obscure OS. :-)
--
Tore Aursand <tore@aursand.no>
------------------------------
Date: Fri, 10 Oct 2003 19:41:09 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBAC5969.15A27%henryn@zzzspacebbs.com>
Bryan Castillo:
Thanks for your post on this thread:
in article 1bff1830.0310071915.68b1952f@posting.google.com, Bryan Castillo
at rook_5150@yahoo.com wrote on 10/7/03 8:15 PM:
(Sorry for the delay in responding. Ate some bad food, was "down" for a
couple of days.)
> Henry <henryn@zzzspacebbs.com> wrote in message
>
> <snip>
>
>> I've got a bunch of fixed-format text files (< 100k bytes each) to sniff.
>>
>> Each file is divided into paragraphs. Each para is preceded by at least
>> three blank lines, and is introduced by a section number of 1 to 6 digits
>> followed by a period and two spaces, OR, 1 to 6 digits followed by a period
>> and at least one digit, followed by a period and two spaces, e.g.
>>
<snip>
<snip>
<snip>
>>
>> Seems the best way to deal with this is to slurp, and use "split" with the
>> appropriate regexp. Wrinkle: I need to retain the section numbers in the
>> return strings.
>
> Here is a way to slurp and split with an re, for what you described.
> 3 things you might want to look at:
>
> 1. How the zero-width look ahead assertion (?!) doesn't
> consume the section number
"Doesn't consume"? Now I'm REALLY confused. According to what I find in
(one) perlre man page, this has concept has to do with looking for 'x' not
followed by 'y'. Maybe I have the wrong man page. Is there a place
that
>
> 2. How the (?:) grouping doesn't capture the value
> (you could have used regular capturing grouping
> but there isn't any point to capture in the split)
Right (I think) -- ( ) captures and groups, while (?: ) groups only. Got
it.
>
> 3. How the qr operator is used. It isn't necessary, but
> I thought it made the code more readable.
I think I get this.
>
> You should also see, that this split might leave an empty
> value in first element of the array. You will have to check for it.
Yes, definitely, I've grown accustomed to the empty value in element 0.
>
>
> use strict;
> use warnings;
> use IO::File;
Huh? Is this the o-o face of perl? Do I need this?
>
> sub readfile {
> my $in = IO::File->new($_[0], "r") || die;
> my $text = '';
> $text.=$_ while (<$in>);
> return $text;
> }
>
OK, makes sense, in general; don't assume clean input, right? Fortunately,
I have pretty good assurance my input is all pretty good -- just may not be
consistent.
I like using subroutines, in general. Looks like I'm going to have to learn
how to use them in perl.
> my $text = readfile('file.txt');
>
> # compile re here for readability
> my $re = qr/
> [\r\n]{3,} # match 3 or more new lines
> (?! # zero width look ahead doesn't consume section
> \d{5}\. # match first 5 digits of section
> (?:\d\.)? # match optional digit and dot (non-capturing)
> \s{2} # match 2 spaces
> )
> /x;
>
> my @t = split $re, $text;
>
> for (my $i=0; $i<=$#t; $i++) {
> print "Para [$i]\n", $t[$i], "\n", "-"x60,"\n";
> }
>
> <snip>
>> Could some wizard teach me to fish: Please don't give me a solution, merely
>> tell me where I'm going wrong and put me back on the right path.
> Sorry, but its easier to give a solution and to ask you to
> read it and research it to figure out how it works.
>
That certainly is a reasonable solution, and I appreciate your help and
patience.
Most of the above makes sense to me. (I still have to understand the
oddities of the "print" syntax, but that's for a different thread.)
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
>
<snip>
>>
>> Thanks,
>>
>> Henry
>>
------------------------------
Date: Fri, 10 Oct 2003 19:41:06 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBAC5965.15A27%henryn@zzzspacebbs.com>
Roy Johnson:
Thanks for your response on this thread:
in article 3ee08638.0310080606.5a95dbae@posting.google.com, Roy Johnson at
rjohnson@shell.com wrote on 10/8/03 7:06 AM:
(Sorry for the delay in responding. Ate some bad food, was "down" for a
couple of days.)
> For learning how to fish, I recommend the book "Learning Perl". Randal
> has a gift for introducing topics so that they are understandable and
> stick with you.
Hmmm, that's exactly what I have right here, bought it over a year ago,
didn't get a chance to use it until now. It looked like the right choice
at the time.
Anticipating some other comments: I note now that this book was over 9
years old when I bought it. I might have chosen differently if I had paid
attention to the date on it. On the other hand, maybe "older" perl is
"simpler" perl, and easier to learn.
>
> As a versatile fishing pole you should already have, I direct you to
> perldoc, and have included some baited hooks below. :-)
Thanks for following the metaphor, and my further gratitude for not reading
into it any particular theological meaning to it.
> Having a copy of "Programming Perl" is a good alternative to looking
> everything up in perldoc and man pages.
Right, I think that's the next purchase, assuming I survive this round of
perl work.
>
>
> Henry <henryn@zzzspacebbs.com> wrote in message
> news:<BBA85E37.1558D%henryn@zzzspacebbs.com>...
>> #1 What does using "my" mean? (Give me a clue -- a keyword; I'll look it up.
>> Googling for "my" and "perl" has not been particularly enlightening.)
>
> "my" declares a variable that exists only in the enclosing block.
I kind of figured that, but wanted to be sure. I _did_ look for it.
> It is "lexically scoped". When declaring variables, this is usually what you
> want. Undeclared variables are global, and those declared "local" are
> "dynamically scoped", meaning their values will persist into function calls.
Right. (Jeez, yet another permutation on scoping rules to learn.)
>
> perldoc -f my
> perldoc -f local
Aha! That's what "perldoc" means. And MacOS X has it. Cool. Strange
controls, though. Uses nroff? Oh, well...
Ummm, this may be entirely obvious to you, but how would a newcomer know
about perldoc? Oh, well, it is clearly shown in the base man page, but
not in the two books I bought.
>
>> #2 Is there any difference --except brevity-- between writing
>> \n{3}
>> and
>> \n\n\n
>> -- both mean "exactly 3 newlines in succession" right?
>
> Correct. I like shorter expressions when possible, and prefer not to
> have to count how many times I've put something.
Right.
>
>> I understand the fundamental match expression components, excepting your use
>> of parens and "?:".
>
> (?:...) indicates that the enclosing parentheses will not be returned
> by the match or assigned to $1, etc. They are only there to group the
> pattern so that a quantifier can apply to it.
>
> perldoc perlretut
> perldoc perlre
I've been all over prelre in the man pages. I guess you mean "perlreftut".
Yep, I'll have to read that.
>
>> #3 To get started, is there a difference between uttering
>> my @paras = split(/\n{3}(\d+\.(?:\d+.)?) /, $whole_file);
>> and
>> my @paras = split /\n{3}(\d+\.(?:\d+.)?) /, $whole_file;
>> Both seem to work the same way in my test scaffolding.
>
> Apart from the extra space in the 2nd pattern, they should be the
> same. The parentheses for function calls are generally optional,
> unless it becomes ambiguous which function gets an argument.
Wow, yet another variation on syntax requirements. I would just as soon
have parens for function arguments required, but that probably shows I
haven't used perl long enough.
>
> perldoc -f split
>
>> #4 .... And I _really_ don't see how this expression leads to getting
>> alternating saved section numbers and section contents in the output array.
>
> It's how split works. The pattern you give it is the delimiter, which
> is not ordinarily returned, but if you have parenthesized
> sub-expression(s) in its pattern, they will be returned in order
> amidst the rest of the data. (Except, of course, if you ?: the ()s.)
Oh, yeah, that. I was getting so deep into the re stuff that I forget the
function in which I was operating. True!
>
>>> [...]I recommend \d instead of [0-9]).
>>
>> OK, these are equivalent, though, right? Is this a matter of style,
>> dialect, common usage, modernity, or what?
>
> Convenience, mostly. They are equivalent. I probably shouldn't have
> thrown extras like that at you when you're trying to nail down more
> fundamental stuff.
Indeed. Actually, that minor variation isn't a problem. Some others on
this thread have thrown much other arcane stuff at me.
>
> Read and practice.
Well, eventually, I need to do the job I set out to. The good news is that
I see how all the tools I need to do the job are at my fingertips, in one
environment. I could do this with awk and shell scripting, too, but it
would be messy. The bad news is that perl seems to have infinite
regression of complexity; the further I look, the more complexity I see!
Is there a deep structure to perl that will become clear after study and
practice? Or will I confirm my current impression that it's got extensions
of a good basic idea extending to the horizon in every direction?
Thanks,
Henry
Henryn@zzzspacebbs.com remove 'zzz'
------------------------------
Date: Fri, 10 Oct 2003 21:27:50 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBAC726A.15A54%henryn@zzzspacebbs.com>
Tad McClellan:
Thanks for your post on this thread:
in article slrnbo88m4.lk2.tadmc@magna.augustmail.com, Tad McClellan at
tadmc@augustmail.com wrote on 10/8/03 7:44 AM:
> Roy Johnson <rjohnson@shell.com> wrote:
>
> [snip good advice]
>
>> "Programming Perl" is a good alternative to looking everything up
>> in perldoc and man pages.
>
>
> No it isn't.
>
> The Camel book describes some old version of Perl.
>
> The std docs describe the version of Perl that you
> actually have installed on your system.
>
>
> "Programming Perl" is a good _supplement_ to looking everything
> up in perldoc.
OK, maybe I _won't_ make this my next purchase. Just what I need to add to
my confusion, a serious case of versionitis.
I'm really struggling to find the right combination of references, both
print and electronic, to support my efforts to learn perl and do a practical
project at the same time.
It appears that between man and perldocs, I _can_ get all the content I
need, and some very good examples.
However, sorry, I don't find these the friendliest documentation
environments. Man pages are great, as far as they go...
Also, I don't find them very well calibrated with respect to
level-of-expertise or detail. Just in the course of this thread, I've found
myself pulled deeper and deeper into what I consider highly-technical
aspects of perl. It is reassuring to know there's plenty of flexibility to
perl, but I sure wish there were "depth" notices (as on the edges of most
swimming pools) on the various materials. I'm founding myself drowned in
detail when all I want to do is get to the other side of the pool.
Is it possible to classify perl material into, say, "beginning",
"intermediate" and "advanced"? Is this done in practice?
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
>
>
> [snip more good advice]
>
------------------------------
Date: Fri, 10 Oct 2003 21:35:22 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBAC742E.15A56%henryn@zzzspacebbs.com>
Sam Holden:
Thanks for your post on this thread:
in article slrnbo96jk.ep2.sholden@flexal.cs.usyd.edu.au, Sam Holden at
sholden@flexal.cs.usyd.edu.au wrote on 10/8/03 4:15 PM:
> On Wed, 08 Oct 2003 19:21:02 GMT, Henry <henryn@zzzspacebbs.com> wrote:
>>
>> That said, I have to say I find the man pages the last place I want to look
>> in terms of convenience. I'll have to find a web based... Done!
>
> The risk with that is that the man pages on your system will document
> the perl installed on your system. The web versions will document
> some version of perl which might not be the one you are using.
The basics should be the same, right?
>
> Plus the man pages also document the modules you have installed, rather than
> a random selection of them...
>
Of course. But, as I've said in another post on this thread just now, I
don't find the man pages a very friendly environment, especially for
material of this complexity.
>>
>> Ah, much easier. Here's a relevant extract.
>>
>> ...Setting to "" will treat two or more consecutive empty lines as a single
>> empty line. Setting to "\n\n" will blindly assume that the next input
>> character belongs to the next paragraph, even if it's a newline. (Mnemonic:
>> / delimits line boundaries when quoting poetry.)
>>
>> Quoting _poetry_?
>
> Why not. It's true after all, and hence a reasonable mnemonic.
I guess you are talking about a typographic convention, as in "Candy is
dandy/But liquor is quicker" (Credit: Ogden Nash). I guess I don't see the
parallel, sorry.
>
>>
>> The choice of "" as a special is clearly a choice of convenience on the part
>> the people doing the internals-- and has no particular mnemonic or symbolic
>> values. I'm glad that's clear.
>
> "" and undef are the only two values that could be used as something special,
> since everything else is a possible literal end of line marker.
I guess so. That issue hasn't stopped the use of escape sequences in other
contexts, right?
>
> undef as "slurp" mode makes sense, since that's more common than paragraph
> mode (in my experience anyway) and being undef means a simple 'local $/;'
> is enough to enable it.
Some of my colleagues are horrified that I would use slurp mode, so I guess
experiences vary widely.
>
> That leaves "" for something else, and paragraph mode is a good choice in
> my opinion, since it's a reasonably commonly wanted operation.
I trying to grasp this, but failing. Maybe after I learn more about perl it
will become clear.
>
> Of course when references arrived a new possibility became available and
> (since it's perl) was used...
References? Sorry. I keep getting deeper and deeper. Do I need to
understand 'references'?
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
------------------------------
Date: Fri, 10 Oct 2003 21:43:10 GMT
From: Henry <henryn@zzzspacebbs.com>
Subject: Re: Teach me how to fish, regexp
Message-Id: <BBAC7603.15A58%henryn@zzzspacebbs.com>
HelgiBriem:
Thanks for your post on this thread:
in article v9faovgncsra10do4urv7g81af0diji8v5@4ax.com, Helgi Briem at
HelgiBriem_1@hotmail.com wrote on 10/9/03 3:53 AM:
> On Wed, 08 Oct 2003 19:21:02 GMT, Henry <henryn@zzzspacebbs.com>
> wrote:
>
>
>> That's a lot of stuff, and in a reference format. Fortunately, the examples
>> are generally quite good, but this isn't exactly the most friendly
>> environment.
>
> What do you mean? Plain text, a pageful at a time, readily
> searchable, isn't friendly enough for you? How much more
> friendly can you get. If you prefer, the Activestate distribution
> of Perl for Windows, Linux and Solaris, comes with all the
> documentation in html format. I use that a little, but usually
> prefer perldoc.
I would not want to argue personal preferences, not at all. My preference
would be for html. As I'm working on MacOS X, apparently I'm out of luck.
>
>>> Furthermore: Don't worry too much that some of this stuff looks
>>> magical. It is. Perl is full of things that you just have to learn
>>> about by immersion, and by repeated visits to the same documentation.
>>> it can take a while before some of this stuff becomes automatic.
>>
>> Perl doesn't seem to be anything one can pick up quickly, that's for sure.
>
> I disagree. Programming logic in itself takes a while, but
> if you are a programmer, you can pick up enough Perl to do
> useful things in a couple of weeks, *if* you learn how to use
> perldoc. It is the very core of learning Perl, more important than
> anything else.
I am a programmer by profession, and I've accomplished some useful work in
perl already. Perhaps this is again a matter of personal preference as
well: I find perl chaotic and not well-bounded. Perhaps that simply means
I'm a different kind of programmer (I am; I work in embedded systems mostly)
or an old-fashioned programmer (possibly).
Would you mind sharing a few bullet points about the keys to getting the
most out of perldoc? From my few first tries, it seems very awkward.
Maybe I'm doing something completely wrong, but I seem to need to do a
vi-style ":q" just to get back to the shell at the end of a doc.
Thanks,
Henry
henryn@zzzspacebbs.com remove 'zzz'
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 5645
***************************************
