[22626] in Perl-Users-Digest
Perl-Users Digest, Issue: 4847 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 15 06:15:37 2003
Date: Tue, 15 Apr 2003 03:10:10 -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, 15 Apr 2003 Volume: 10 Number: 4847
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Shortcut <tassilo.parseval@rwth-aachen.de>
Re: Specific Regex Question <dha@panix.com>
Re: Specific Regex Question <Jeff@aetherweb.co.uk>
Re: Specific Regex Question <john-s@moving-picture.com>
Re: Specific Regex Question <Jeff@aetherweb.co.uk>
Re: Stack used by regexen <nospam-abuse@ilyaz.org>
Re: Stack used by regexen <tassilo.parseval@rwth-aachen.de>
Temporary Folder <marko@lvivmedia.lviv.net>
Re: Temporary Folder <kasp@epatra.com>
Re: Temporary Folder <News@LearnQuick.Com>
Validating user input to match certain characters (Mark Smith)
Re: Validating user input to match certain characters <kasp@epatra.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 15 Apr 2003 01:22:31 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <9A2dne8N_sG6OAajXTWcrg@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"Jeopardy" (because the answer comes before the question), or
"TOFU".
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: 15 Apr 2003 06:38:05 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Shortcut
Message-Id: <b7g9cd$cng$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Jürgen Exner:
> Benjamin Goldberg wrote:
>> [OT] Slightly untrue. You can swap two variables in C without a third
>> variable:
>>
>> a ^= b;
>> b ^= a;
>> a ^= b;
>
> Well, ok, you are right.
> But that hack is direct result of C's inability to deal with data that is
> larger than on word/double word.
Or rather its ability to treat almost any data as word/double word. They
have to be pointers of course. In this case the swapping trick only
works with a cast (and provided, an 'int' is large enough to hold a
pointer on the respective platform):
(int)a ^= (int)b;
(int)b ^= (int)a;
(int)a ^= (int)b;
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Tue, 15 Apr 2003 04:14:33 +0000 (UTC)
From: "David H. Adler" <dha@panix.com>
Subject: Re: Specific Regex Question
Message-Id: <slrnb9n1p9.rqd.dha@panix2.panix.com>
In article <e4dad21a.0304141937.583e8897@posting.google.com>, Cameron wrote:
> Hi All --
>
> I have a comma delimited text file with records in the following format:
>
> B4527D,91,3,PONT,BONN,"5,675.00",600,"2,470.27",,,,32103,HM,WO
> ^^^ ^^^
> Can someone show me how to strip the only the commas that fall within quotes?
Perhaps the Text::CSV or Text::CSV_XS modules would be of help?
dha
--
David H. Adler - <dha@panix.com> - http://www.panix.com/~dha/
"What is this Japanese preoccupation with the name Ken???" - Tom Servo
------------------------------
Date: Tue, 15 Apr 2003 07:49:06 +0100
From: "Jeff Snoxell" <Jeff@aetherweb.co.uk>
Subject: Re: Specific Regex Question
Message-Id: <b7g9vq$7hp$1@newsg1.svr.pol.co.uk>
> I have a comma delimited text file with records in the following format:
>
> B4527D,91,3,PONT,BONN,"5,675.00",600,"2,470.27",,,,32103,HM,WO
> ^^^ ^^^
> Can someone show me how to strip the only the commas that fall within
quotes?
Try this:
my $text = 'B4527D,91,3,PONT,BONN,"5,675.00",600,"2,470.27",,,,32103,HM,WO';
$text =~ s/,\"([^\"]*),([^\"]*)\",/,$1\%COMMA\%$2,/g;
my @items = split(",", $text);
@items = map { s/\%COMMA\%/,/g; $_; } @items;
print join("<BR>\n", @items);
Not super efficient I guess but it does the trick.
HTH
Jeff Snoxell
Aetherweb Ltd - http://www.bespoke-web-design-uk.co.uk
------------------------------
Date: Tue, 15 Apr 2003 09:13:18 +0100
From: John Strauss <john-s@moving-picture.com>
Subject: Re: Specific Regex Question
Message-Id: <20030415091318.58db57b0.john-s@moving-picture.com>
On 14 Apr 2003 20:37:30 -0700
cam@ntwk.net (Cameron) wrote:
>
> Hi All --
>
> I have a comma delimited text file with records in the following format:
>
> B4527D,91,3,PONT,BONN,"5,675.00",600,"2,470.27",,,,32103,HM,WO
> ^^^ ^^^
> Can someone show me how to strip the only the commas that fall within quotes?
>
> Thanks,
>
> Cameron
this seems to work for your sample record.
$record =~ s/\"([^\"|,]),/\"$1/g;
------------------------------
Date: Tue, 15 Apr 2003 10:48:19 +0100
From: "Jeff Snoxell" <Jeff@aetherweb.co.uk>
Subject: Re: Specific Regex Question
Message-Id: <b7gkfq$v3s$1@news8.svr.pol.co.uk>
> > I have a comma delimited text file with records in the following format:
> >
> > B4527D,91,3,PONT,BONN,"5,675.00",600,"2,470.27",,,,32103,HM,WO
> > ^^^ ^^^
> > Can someone show me how to strip the only the commas that fall within
quotes?
>
> this seems to work for your sample record.
> $record =~ s/\"([^\"|,]),/\"$1/g;
This strips the commas within quotes very effectively... but perhaps in some
data the commas are needed.
Jeff Snoxell
Aetherweb Ltd - http://www.bespoke-web-design-uk.co.uk
------------------------------
Date: Tue, 15 Apr 2003 05:35:06 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Stack used by regexen
Message-Id: <b7g5ma$u3s$1@agate.berkeley.edu>
[A complimentary Cc of this posting was NOT [per weedlist] sent to
Benjamin Goldberg
<goldbb2@earthlink.net>], who wrote in article <3E98B3E5.D2F8B0BA@earthlink.net>:
> Ilya Zakharevich wrote:
> [snip]
> > [A couple of years ago I build the infrastructure for stackless REx
> > engine,
>
> How can you do backtracking without a stack?
You use your own stack (my patch used one of 6 existing Perl stacks),
not the C stack.
> Or do you merely mean, you use an explicitly allocated stack, instead of
> recursion, and so you avoid using the C stack (which saves rather more
> stuff than you actually need saved)?
> Obviously, if all parts of a regex are non-greedy, or if you're using a
> DFA, then no backtracking is needed
Depends on the implementation. What is important is *recursion*, not
backtracking. Recursion uses stack, and one needs to allocate stack
*in advance*. And since nobody can predict what a particular copy of
interpreter will do, one is forced to allocate enormous stack.
On my builds I use 32M stack (just to avoid debugging "common"
stack-based problems - most people run with 8M stack, so will hit the
problems ahead of me ;-); hopefully, some of them will debug it.
> In perl6/parrot, the regex stack is explicitly allocated,
Broken architecture.
> > and instrumented one (of circa 10) stack-bound brnach to use
> > this infrastructure. If anybody cared enough to *copy* my patch into
> > other 9 branches, Perl does not need lots of stack any more - AFAIR,
> > only the REx engine was using stack.]
>
> Could you explain what you are talking about, for us unenlightened
> folks?
I made it possible (implemented an API with convenient macros) to
allocate the backtracking info on the Perl's save-stack. There are
approximately 10 cases where the REx engine uses recursion; I
converted one of these cases to the new API (and did the fix debug
cycle). Given sufficient interest, people would copy the patch to
other 9 cases.
Hope this helps,
Ilya
------------------------------
Date: 15 Apr 2003 06:47:23 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Stack used by regexen
Message-Id: <b7g9tr$d53$1@nets3.rz.RWTH-Aachen.DE>
[ posted and CCed ]
Also sprach Ilya Zakharevich:
> [A complimentary Cc of this posting was NOT [per weedlist] sent to
> Benjamin Goldberg
>> > and instrumented one (of circa 10) stack-bound brnach to use
>> > this infrastructure. If anybody cared enough to *copy* my patch into
>> > other 9 branches, Perl does not need lots of stack any more - AFAIR,
>> > only the REx engine was using stack.]
>>
>> Could you explain what you are talking about, for us unenlightened
>> folks?
>
> I made it possible (implemented an API with convenient macros) to
> allocate the backtracking info on the Perl's save-stack. There are
> approximately 10 cases where the REx engine uses recursion; I
> converted one of these cases to the new API (and did the fix debug
> cycle). Given sufficient interest, people would copy the patch to
> other 9 cases.
I've been following the porters-list for a few months now and haven't
seen this topic discussed. Ilya, since you say that the code already
exists in some other places, couldn't you just bring it up again? I am
quite sure that somebody will pick it up and apply the necessary
patches to the source-tree. It's not that the porters ignore patches out
of malignity...probably they just aren't aware of them. Thus everybody
could benefit from your efforts.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Tue, 15 Apr 2003 09:54:06 +0300
From: "Marko" <marko@lvivmedia.lviv.net>
Subject: Temporary Folder
Message-Id: <b7gaa7$2eqp$1@news.uar.net>
Hi,
What I can get Temporary Folder???
For example: C:\WINNT\Temp
Thanks!!
------------------------------
Date: Tue, 15 Apr 2003 12:53:28 +0530
From: "Kasp" <kasp@epatra.com>
Subject: Re: Temporary Folder
Message-Id: <b7gcb3$vg9$1@newsreader.mailgate.org>
How is your question is related to Perl?
%SystemRoot%\TEMP is what gives you the path to the TEMP folder in Windows.
Also you might want to try "echo %TEMP% %TMP%"
--
"Accept that some days you are the pigeon and some days the statue."
"A pat on the back is only a few inches from a kick in the butt." - Dilbert.
------------------------------
Date: Tue, 15 Apr 2003 07:27:45 GMT
From: "Herb Martin" <News@LearnQuick.Com>
Subject: Re: Temporary Folder
Message-Id: <RvOma.78995$rd4.2981562@twister.austin.rr.com>
If you only want it for "Windows" it is an environment
variable. Read it from the %ENV hash...
print "$ENV{'temp'}\n";
Might work for other operating systems...your milage
may vary.
Herb Martin
Try ADDS for great Weather too:
http://adds.aviationweather.noaa.gov/projects/adds
------------------------------
Date: 15 Apr 2003 02:34:09 -0700
From: Mark.Smith@sonyericsson.com (Mark Smith)
Subject: Validating user input to match certain characters
Message-Id: <cf24885e.0304150134.6e49665d@posting.google.com>
I have some Web forms that take user input. I process these in Perl.
What I want to do is limit what characters are valid for certain
fields. For example if the user creates a new account I would like to
restrict the account name to just A-Z, a-z, 0-9, _ and -.
I have tried using the following:
if ($accountname !~ m/([A-Za-z0-9_-])/)
{
print "<B>ERROR: invalid chars, please re-enter</B>";
}
However aslong as it finds at least one valid character the match
fails to output the error.
So "%abAB" should be invalid as it contains % but will not fail as
contains valid characters. Only strings that contain none of the
valid characters I've specified will result in the error message being
output.
I'm sure this is a fairly standard problem and I know I have done this
properly in the past but I don't have access to my notes and other
code at the moment. Can anyone please help.
Regards,
Mark.
------------------------------
Date: Tue, 15 Apr 2003 15:16:49 +0530
From: "Kasp" <kasp@epatra.com>
Subject: Re: Validating user input to match certain characters
Message-Id: <b7gkee$e8t$1@newsreader.mailgate.org>
Try this:
if ($accountname =~ m/[^A-Za-z0-9_-]/)
--
"Accept that some days you are the pigeon and some days the statue."
"A pat on the back is only a few inches from a kick in the butt." - Dilbert.
------------------------------
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 4847
***************************************
