[31577] in Perl-Users-Digest
Perl-Users Digest, Issue: 2836 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 26 06:09:19 2010
Date: Fri, 26 Feb 2010 03:09:05 -0800 (PST)
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, 26 Feb 2010 Volume: 11 Number: 2836
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
UDP receive <aku@bluewin.ch>
Re: UDP receive <uri@StemSystems.com>
Re: Would like some words of wisdom - convert text file <uri@StemSystems.com>
Re: Would like some words of wisdom - convert text file <glenmillard@gmail.com>
Re: Would like some words of wisdom - convert text file <uri@StemSystems.com>
Re: Would like some words of wisdom - convert text file <jimsgibson@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 26 Feb 2010 02:13:47 -0600
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <0O6dnTSLhbYmHxrWnZ2dnUVZ_q6dnZ2d@giganews.com>
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.9 $)
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.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
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://www.rehabitation.com/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 that they do
know and are being the "bad kind" of Lazy.
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_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
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
------------------------------
Date: Thu, 25 Feb 2010 21:17:14 -0800 (PST)
From: aku <aku@bluewin.ch>
Subject: UDP receive
Message-Id: <73bcfaba-d260-4028-b432-6da6e80c7d12@g19g2000yqe.googlegroups.com>
Hi, got a UDP msg with format STXdataETX (without a LF)
I use this:
use IO::Socket;
my $PORT='4444';
$sock = IO::Socket::INET -> new(LocalPort => $PORT, Proto => 'udp') or
die "socket: $@";
print "Server Mode\n";
while ($sock->recv($nachricht,1024))
{
print "$nachricht";
};
with my incoming format STXdataETX (without a LF) it do not work; if I
add a LF it works
is there a chance to change the delimiter in the recv function from LF
to ETX or are there other solutions for my program?
Thanks a lot
aku
------------------------------
Date: Fri, 26 Feb 2010 01:07:51 -0500
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: UDP receive
Message-Id: <87pr3sttqg.fsf@quad.sysarch.com>
>>>>> "a" == aku <aku@bluewin.ch> writes:
a> Hi, got a UDP msg with format STXdataETX (without a LF)
a> I use this:
a> use IO::Socket;
a> my $PORT='4444';
a> $sock = IO::Socket::INET -> new(LocalPort => $PORT, Proto => 'udp') or
a> die "socket: $@";
a> print "Server Mode\n";
a> while ($sock->recv($nachricht,1024))
a> {
a> print "$nachricht";
a> };
a> with my incoming format STXdataETX (without a LF) it do not work; if I
a> add a LF it works
a> is there a chance to change the delimiter in the recv function from LF
a> to ETX or are there other solutions for my program?
udp does not have a delimiter and you don't need one if your message is
always under a packet size. i would bet the issue is on the client side
as needing a lf implies it is line buffered and isn't being flushed
until a lf (newline) is sent. are you using print to send the packet?
try using send() on a udp client socket and it should work.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Thu, 25 Feb 2010 18:09:49 -0500
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Would like some words of wisdom - convert text files to CSV
Message-Id: <87pr3sx682.fsf@quad.sysarch.com>
>>>>> "G" == GlenM <glenmillard@gmail.com> writes:
>> you need to be much clearer. is each mail file to be written out as a
>> single csv file? will the file names stay the same?
G> well, it doesn't really matter, but if it was one big CSV file, it
G> would probably be too big. So, I can break them up into groups
G> manually. So, for now, one big CSV file for all emails.
do you realize how wide this file will be? with some mails, it could be
10's of k wide. that is insane.
G> Second:
G> also that prints to stdout. if you want to do this per file and keep
G> the
>> results you need to open an output file. and you will need an outer loop
>> to scan all the files. will they all be in a directory? passed in on the
>> command line into @ARGV? you need to ask and answer these questions.
G> I can redirect the output to a file - yes, I see that it goes to
G> STDOUT. Not really looking for bells and whistles.
G> I will scan in every file in the directory - like I said previously,
G> it is a sheet-load of data so, I will split up the files.
redirecting to stdout is fine but if you do want to split this up, it is
better to manage your output directly in perl.
G> Third:
G> well, think about your current output. why does it put each field
G> (line)
>> on its own line? i will let you answer that first and then you can
>> easily fix it.
G> I would like to have each field in a different 'column' or be
G> separated by a "|" or a "," (hence CSV). So, that is the next hurdle.
you didn't answer the question. WHY does your current code put each line
on its own line instead of all the mail lines in one long csv line?
until you fix that (and others already told you how), you can't get what
you want.
G> Fourth
G> that is a very strange format and will make for extremely long csv
G> lines
>> (not a problem but just odd). also you are putting the line number in
>> front of each line. why? you can count the fields (lines). what happens
>> if a text line in an email starts with a number? then it will be next to
>> your line number making it hard to parse out the line number. also your
>> format starts with | so it means there is a leading empty field in the
>> csv. not a big problem but something to be aware of.
G> Well, I just want to get all of the emails into a spreadsheet format,
G> then they are easier to work with. I can massage the data manually
G> afterward. Just want to get it into a CSV - maybe I can get fancy once
G> I get the fundamentals down.
easier to work with?? how? mail is easy to work with already. there are
many modules that will parse out mail including all the headers (which
aren't trivial to parse and a spreadsheet won't help).
and learn to bottom post. these netiquette rules are all covered in this
group's guidelines which are posted regularly. find a copy and read it.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Thu, 25 Feb 2010 15:40:54 -0800 (PST)
From: GlenM <glenmillard@gmail.com>
Subject: Re: Would like some words of wisdom - convert text files to CSV
Message-Id: <4e6e2414-3841-4700-8b05-82a748bcb553@33g2000yqj.googlegroups.com>
On Feb 25, 6:09=A0pm, "Uri Guttman" <u...@StemSystems.com> wrote:
> >>>>> "G" =3D=3D GlenM =A0<glenmill...@gmail.com> writes:
>
> =A0 >> you need to be much clearer. is each mail file to be written out a=
s a
> =A0 >> single csv file? will the file names stay the same?
>
> =A0 G> well, it doesn't really matter, but if it was one big CSV file, it
> =A0 G> would probably be too big. So, I can break them up into groups
> =A0 G> manually. So, for now, one big CSV file for all emails.
>
> do you realize how wide this file will be? with some mails, it could be
> 10's of k wide. that is insane.
>
> =A0 G> Second:
>
> =A0 G> =A0also that prints to stdout. if you want to do this per file and=
keep
> =A0 G> the
> =A0 >> results you need to open an output file. and you will need an oute=
r loop
> =A0 >> to scan all the files. will they all be in a directory? passed in =
on the
> =A0 >> command line into @ARGV? you need to ask and answer these question=
s.
>
> =A0 G> I can redirect the output to a file - yes, I see that it goes to
> =A0 G> STDOUT. Not really looking for bells and whistles.
> =A0 G> I will scan in every file in the directory - like I said previousl=
y,
> =A0 G> it is a sheet-load of data so, I will split up the files.
>
> redirecting to stdout is fine but if you do want to split this up, it is
> better to manage your output directly in perl.
>
> =A0 G> Third:
>
> =A0 G> well, think about your current output. why does it put each field
> =A0 G> (line)
> =A0 >> on its own line? i will let you answer that first and then you can
> =A0 >> easily fix it.
>
> =A0 G> I would like to have each field in a different 'column' or be
> =A0 G> separated by a "|" or a "," (hence CSV). So, that is the next hurd=
le.
>
> you didn't answer the question. WHY does your current code put each line
> on its own line instead of all the mail lines in one long csv line?
> until you fix that (and others already told you how), you can't get what
> you want.
>
> =A0 G> Fourth
>
> =A0 G> that is a very strange format and will make for extremely long csv
> =A0 G> lines
> =A0 >> (not a problem but just odd). also you are putting the line number=
in
> =A0 >> front of each line. why? you can count the fields (lines). what ha=
ppens
> =A0 >> if a text line in an email starts with a number? then it will be n=
ext to
> =A0 >> your line number making it hard to parse out the line number. also=
your
> =A0 >> format starts with | so it means there is a leading empty field in=
the
> =A0 >> csv. not a big problem but something to be aware of.
>
> =A0 G> Well, I just want to get all of the emails into a spreadsheet form=
at,
> =A0 G> then they are easier to work with. I can massage the data manually
> =A0 G> afterward. Just want to get it into a CSV - maybe I can get fancy =
once
> =A0 G> I get the fundamentals down.
>
> easier to work with?? how? mail is easy to work with already. there are
> many modules that will parse out mail including all the headers (which
> aren't trivial to parse and a spreadsheet won't help).
>
> and learn to bottom post. these netiquette rules are all covered in this
> group's guidelines which are posted regularly. find a copy and read it.
>
> uri
>
> --
> Uri Guttman =A0------ =A0u...@stemsystems.com =A0-------- =A0http://www.s=
ysarch.com--
> ----- =A0Perl Code Review , Architecture, Development, Training, Support =
------
> --------- =A0Gourmet Hot Cocoa Mix =A0---- =A0http://bestfriendscocoa.com=
---------
Okay - sorry about the post SNAFU.
Okay - perhaps I am barking up the wrong tree.
Perhaps you would be able to provide me with some module examples that
will extract email messages. The reason being is that I need to have
these emails in a spread sheet for a presentation that I am providing
to a government official - makes it easier for them to read.
Even a module (with examples) that will extract the email fields into
a database. That is a better idea because then I can search and
extract the data that I need.
Does that make any sense?
Thanks
Glen
------------------------------
Date: Thu, 25 Feb 2010 19:16:55 -0500
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Would like some words of wisdom - convert text files to CSV
Message-Id: <87iq9kx348.fsf@quad.sysarch.com>
>>>>> "G" == GlenM <glenmillard@gmail.com> writes:
G> Okay - sorry about the post SNAFU.
you still haven't gotten it. read the guidelines and google about bottom
posting. you don't quote the entire email but the parts you reply
to. you edit out the rest. you put your reply parts after the parts they
refer to. it is a conversation that reads top to bottom. very logical
but untaught to the intarweb unwashed masses. :/
G> Perhaps you would be able to provide me with some module examples
G> that will extract email messages. The reason being is that I need
G> to have these emails in a spread sheet for a presentation that I am
G> providing to a government official - makes it easier for them to
G> read.
search cpan. there are many modules that parse emails. just look at the
docs for some and see what catches your eye. then try them and see how
you like them. this is easy and very educational. using cpan is part of
the perl culture.
G> Even a module (with examples) that will extract the email fields
G> into a database. That is a better idea because then I can search
G> and extract the data that I need.
you can parse out the fields but putting them into a db is more likely
your code as that can be very custom.
G> Does that make any sense?
sort of. you need to learn to explain the bigger picture. saying you
want emails with one line per csv field is very different than saying
you want to be able to search emails by various headers and such.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Thu, 25 Feb 2010 18:12:07 -0800
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: Would like some words of wisdom - convert text files to CSV
Message-Id: <250220101812072344%jimsgibson@gmail.com>
In article
<f6dbdaaf-05d7-4c73-a890-000096b179ab@k41g2000yqm.googlegroups.com>,
GlenM <glenmillard@gmail.com> wrote:
>
> Well, I just want to get all of the emails into a spreadsheet format,
> then they are easier to work with. I can massage the data manually
> afterward. Just want to get it into a CSV - maybe I can get fancy once
> I get the fundamentals down.
Perl can write Excel documents directly using the
Spreadsheet::WriteExcel module, available from CPAN. You can even add
some formatting like bold, italics, etc,
--
Jim Gibson
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 V11 Issue 2836
***************************************
