[23856] in Perl-Users-Digest
Perl-Users Digest, Issue: 6059 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jan 31 18:10:34 2004
Date: Sat, 31 Jan 2004 15:10:07 -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 Sat, 31 Jan 2004 Volume: 10 Number: 6059
Today's topics:
Re: Perl For Amateur Computer Programmers <1usa@llenroc.ude>
Re: Perl For Amateur Computer Programmers <usenet@morrow.me.uk>
Re: Perl For Amateur Computer Programmers <nobull@mail.com>
Re: Perl For Amateur Computer Programmers <edgrsprj@ix.netcom.com>
Re: Perl For Amateur Computer Programmers <usenet@morrow.me.uk>
Re: Perl For Amateur Computer Programmers <uri@stemsystems.com>
Re: Perl For Amateur Computer Programmers <matthew.garrish@sympatico.ca>
Re: Perl For Amateur Computer Programmers (Walter Roberson)
Re: Perl For Amateur Computer Programmers <matthew.garrish@sympatico.ca>
Re: Perl For Amateur Computer Programmers <dwall@fastmail.fm>
Re: Perl For Amateur Computer Programmers <flavell@ph.gla.ac.uk>
Re: Perl For Amateur Computer Programmers <tim@vegeta.ath.cx>
Re: Perl For Amateur Computer Programmers <tadmc@augustmail.com>
Re: Perl For Amateur Computer Programmers <bobx@linuxmail.org>
Re: printing sub results in heredocs <bmb@ginger.libs.uga.edu>
Re: Template Toolkit ... is there a bug in the ANYCASE <dave@dave.org.uk>
Re: unused lexicals <bill_knight2@yahoo.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 31 Jan 2004 14:25:13 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <Xns94815FD564A07asu1cornelledu@132.236.56.8>
"edgrsprj" <edgrsprj@ix.netcom.com> wrote in
news:qkOSb.4022$jH6.3447@newsread1.news.atl.earthlink.net:
> As I stated in some recent posts, I have been looking for a
> programming language which scientists and other people around the
> world who are not professional computer programmers could use with the
> same ease as Basic.
When I new absolutely nothing baout Perl, I found
http://www.ebb.org/PickingUpPerl/ very useful. You could benefit from
taking a look at that as well. The mistake people make in general is that
to be able to teach material at the beginner level, you have to have years
and years of experience and accumulated knowledge.
Calling something 'beginner level' or 'for amateurs' is not a good way to
cover its shortcomings.
I have neither the time nor the inclanation to go through your tutorial
line by line.
However, let's look at but one paragraph:
<blockquote>
print localtime Generates a lengthy number representing the local time.
Digits 1 & 2 are seconds, 3 & 4 are minutes past the hour, 5 & 6 are hour
in the day, 7 & 8 are day in the month, 9 & 10 are month in the year, and
11 & 12 are the last two digits of the present year. There are several
more numbers which correspond to things such as the day of the week etc.
</blockquote>
Read perldoc -f localtime and perldoc -f print to understand how wildly
wrong this statement is.
And if you do not understand what's wrong then you should not be in the
business of writing tutorials.
Sinan.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
Date: Sat, 31 Jan 2004 15:38:46 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <bvgi66$miu$1@wisteria.csv.warwick.ac.uk>
"edgrsprj" <edgrsprj@ix.netcom.com> wrote:
> I suspect that Perl might not be sufficiently reliable that people who are
> developing computer programs for air traffic controllers would make it their
> first choice. But for use within the international scientific community it
> looks almost ideal because of its versatility, ease of use, and
> availability. Unfortunately I have been encountering one major problem with
> it. And that is with its documentation.
<snip>
> The URL for that Web page is:
>
> Perl For Amateur Computer Programmers
> http://www.freewebz.com/eq-forecasting/Perl.html
I do not wish to sound scathing, as I think that what you are trying
to do is laudable; but that page is *very* *very* bad. Please take it
down: there are more than enough sources of wrong information about
Perl as it is.
If you yourself are reasonably indicative of the level of competence
among the people you are hoping to introduce Perl to, and you think
you have the beginnings of a good grasp of it, then I wonder if it is
too complex for what you want. Certainly the level you have pitched
that page at is too low for anyone to get any sort of idea of how to
program: there are some basic programming concepts, such as an
understanding of how logic operators work, that need a decent
expposition rather than the reference-book style you have chosen. To
explain a little more clearly, perhaps, consider your sentence
| && (or) and for statements where several conditions must be met in
| order for them to be true or correct
. If your reader has met the concept of 'logical AND operator' in some
other language, and understands it, there is no need to say any more
than '&& is the logical AND operator'. OTOH, if he has not, this
explanation omits many ideas that are essential to using the operator
correctly, such as the idea of an expression being true or false.
Some more specific comments:
| any text editing program such as DOS Edit, Windows Notepad, Wordpad,
| and Word, or WordPerfect can be used to create and edit them.
It would be wise to mention that Perl programs are plain text. Trying
to execute a Word document as a Perl program is unlikely to be
terribly successful.
| lines which begin with the pound sign #.
If this is for international users, then '#' is *not* a pound sign. It
is a hash, or a sharp, or a number sign. A pound sign is the British
currency symbol.
Throughout the document you show a complete misunderstanding of what
"\n" means. It represents a newline character. That is all. If you
execute
print "hello\nworld\n";
you will get 'hello' and 'world' on separate lines, because of the
newline between them. The fact that often your output does not appear
until you print a newline is quite separate, and is to do with how the
system buffers output. See $| in perlvar for more information.
| However I suspect that it is probably better not to use "/" with
| filenames and directories.
This is quite wrong: in fact, it is much better to use /, even under
Win32, as then at least relative paths are more likely to be portable
to other OSen.
'<>' is not a Perl operator. The numeric not-equal operator is
'!='. You completely fail to mention the string comparison operators
(eq, ne, lt, gt, cmp), even though the difference is very
important. What is unclear about the descriptions in perlop, that you
couldn't simply refer people there?
Don't even mention goto. It is very rarely useful in Perl, and
fledgling programmers should be encouraged to use proper control
structures where possible.
Any new tutorial ought to use lexical rather than bareword
filehandles, as they are a lot less confusing. That is, you should use
my $FILE;
open $FILE, '< file';
rather than
open FILE, '< file';
.
I would not recommend using a raw select command for high-res
sleeping: apart from anything else, the presence of those three
unexplained 'undef's will confuse people. Use Time::HiRes.
The debugger (perl -d) is not an interactive version of perl. It is a
debugger.
--
Musica Dei donum optimi, trahit homines, trahit deos. |
Musica truces mollit animos, tristesque mentes erigit. | ben@morrow.me.uk
Musica vel ipsas arbores et horridas movet feras. |
------------------------------
Date: 31 Jan 2004 16:17:24 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <u9k738f5yj.fsf@wcl-l.bham.ac.uk>
Ben Morrow <usenet@morrow.me.uk> writes:
> Any new tutorial ought to use lexical rather than bareword
> filehandles, as they are a lot less confusing. That is, you should use
>
> my $FILE;
> open $FILE, '< file';
Surely you mean:
open my $FILE, '<', 'file' or die "Cannot read file: $!";
In early versions of Perl the mode and filename arguments were
(unwisely IMNSHO) forcably combined into a single argument[1]. By
the same argument as Ben used above, a new tutorial should not
introduce this confusing legacy syntax first. You certainly shouldn't
intoduce people to the idea of not checking if open() succedes.
[1] Yes I'm aware that in theory it can be good to have a program that
can take a filename or a command with a trailing '|' as an argument.
I've never encountered a situation where this is good in practice. I
have encountered many situations where this is very bad!
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Sat, 31 Jan 2004 16:49:25 GMT
From: "edgrsprj" <edgrsprj@ix.netcom.com>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <p0RSb.4697$GO6.4089@newsread3.news.atl.earthlink.net>
"Ben Morrow" <usenet@morrow.me.uk> wrote in message
news:bvgi66$miu$1@wisteria.csv.warwick.ac.uk...
> I do not wish to sound scathing, as I think that what you are trying
> to do is laudable; but that page is *very* *very* bad. Please take it
This is the purpose of that Web page:
Perhaps 99% of the people around the world who might have a use for a Perl
program cannot use it because something in the code they generate will
produce an error which stops the program from running. They cannot
determine what is wrong, get frustrated, and switch to some other language.
My Web page is not meant to teach people how to use Perl. It simply states
that if you want to write a simple program which will do something like
multiply two numbers together and store the result in a text file then here
is how to do it. It is like a "cookbook" for creating simple Perl programs.
Once you have the system installed and running on your computer you can copy
all of those routines from my Web page and immediately begin using them to
create a simple program which will do what you want. You do not need to
read instruction manuals for an entire month in order to learn how the
instructions work.
So that is it. If you create a program following my instructions you will
at least be able to perform some basic operation. And then when your
program is operational you can go back and use more sophisticated commands
etc.
Last week I myself could not use it to do anything. And I was not certain
if I would ever be able to use it. But now I can write fairly useful and
powerful programs just using the codes on that page. And it is easy to
check the original reference documents for more exact or versatile
instructions.
Finally, remember that my Web page is just a first version. Information is
being stored there as I learn it. And I would expect things to improve.
------------------------------
Date: Sat, 31 Jan 2004 17:28:02 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <bvgoj2$rjc$1@wisteria.csv.warwick.ac.uk>
"edgrsprj" <edgrsprj@ix.netcom.com> wrote:
> My Web page is not meant to teach people how to use Perl. It simply states
> that if you want to write a simple program which will do something like
> multiply two numbers together and store the result in a text file then here
> is how to do it. It is like a "cookbook" for creating simple Perl
> programs.
>
> Once you have the system installed and running on your computer you can copy
> all of those routines from my Web page and immediately begin using them to
> create a simple program which will do what you want. You do not need to
> read instruction manuals for an entire month in order to learn how the
> instructions work.
But you do. Perl is what I would call a 'real' programming language:
it requires a basic understanding of the fundamentals of programming
before anything useful can be written in it, but once you have a grasp
of the language there is essentially no limit to the complexity of
what it is possible to write. This is why I suspect it may not be what
you want, and some noddy language like VBScript may be better suited
to your task.
Your page will not teach anyone how to write a useful Perl program,
and it will not give them any idea of where to go to learn
this. Multiplying two numbers together and storing the result in a
text file is not useful: I can do it quicker with a calculator and
Notepad than I can with Perl.
> Last week I myself could not use it to do anything. And I was not certain
> if I would ever be able to use it. But now I can write fairly useful and
> powerful programs just using the codes on that page.
I doubt it. I would be pretty sure you are also using other knowledge,
gleaned from reading the perl docs and from here, which you haven't
put into that page. For instance, you do not explain loops in any way
that would lead to someone being able to use them, and Perl's loops
are rather different from, say, BASIC's loops. You do not explain
subs, even at a really basic level. And while you use some modules,
you do not explain what they are, or how they are used; or that there
is a module to do almost anything, which is the real power of Perl.
You need to learn Perl yourself before you start trying to teach
others.
Ben
--
EAT
KIDS (...er, whoops...)
FOR ben@morrow.me.uk
99p
------------------------------
Date: Sat, 31 Jan 2004 18:50:36 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <x7ad44osuc.fsf@mail.sysarch.com>
The Importance Of Distinguishing Between Using Single Versus
Double Quotation Marks Something which it is important to
remember is the fact that Perl usually processes information
contained within single quotation marks (for example ¡Ætext
message¡Ç) differently than information contained within double
quotation marks (for example ¡Ètext message"). I myself do not
know what all of the rules are regarding the significance of
single and double quotation marks. Perhaps the best thing to do
is to either read the Perl documentation regarding them or to at
least be careful about which type of quotation mark is used.
GAHHHH!!!!!
if you don't know the difference, then HOW can you write that crap? how
can you be CAREFUL about choosing if you don't TEACH the difference?
that text is almost criminal.
"don't go to the store unless you know how to either steal or buy
stuff. i don't know the difference but you can read some laws and find
out"
this has to be one of the worst intros to perl i have ever seen. we
should make a copy (i just did) before he takes it down (but he sounds
like he won't) so we can use it in a yapc talk. i got dibs on the
lightning talk for this baby.
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: Sat, 31 Jan 2004 13:59:17 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <4WSSb.7723$qU3.718185@news20.bellglobal.com>
"Ben Morrow" <usenet@morrow.me.uk> wrote in message
news:bvgi66$miu$1@wisteria.csv.warwick.ac.uk...
>
> "edgrsprj" <edgrsprj@ix.netcom.com> wrote:
>
> | lines which begin with the pound sign #.
>
> If this is for international users, then '#' is *not* a pound sign. It
> is a hash, or a sharp, or a number sign. A pound sign is the British
> currency symbol.
>
Actually, pound sign is just as valid a name for it as any of the ones you
quoted (and don't forget good old octothorpe). There is the pound sign you
are thinking of (which is for currency) and the pound sign he is referring
to (which I believe was originally used to distinguish a pound as a unit of
weight). Had he not specified which character he was referring to, you would
have a better case. Otherwise, I agree with your assessment completely...
: )
Matt
------------------------------
Date: 31 Jan 2004 19:27:34 GMT
From: roberson@ibd.nrc-cnrc.gc.ca (Walter Roberson)
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <bvgvj6$ov2$1@canopus.cc.umanitoba.ca>
In article <4WSSb.7723$qU3.718185@news20.bellglobal.com>,
Matt Garrish <matthew.garrish@sympatico.ca> wrote:
:Actually, pound sign is just as valid a name for it as any of the ones you
:quoted (and don't forget good old octothorpe). There is the pound sign you
:are thinking of (which is for currency) and the pound sign he is referring
:to (which I believe was originally used to distinguish a pound as a unit of
:weight).
# as meaning pound weight (of anything other than silver or gold?)
was still seen in the UK when I was last there about 2 years ago.
I have also (rarely) seen it used in Canada -- I think I saw it
less than a week ago on one sign for one product in the corner deli.
[Last time I posted mentioning that I'd seen it used in the UK, someone
replied to the effect of "No, it isn't used here!". Gee, I guess my
eyes must have been playing tricks on me...]
--
Caution: A subset of the statements in this message may be
tautologically true.
------------------------------
Date: Sat, 31 Jan 2004 14:15:56 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <H9TSb.7735$qU3.719215@news20.bellglobal.com>
To quote from the site:
> A version of Perl called ActivePerl can be downloaded from the following
Web site
> for free and then installed. The Windows 5.8.2 AS package which I myself
> downloaded was about 12 million bytes in size (12 Meg).
> http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl
I assume you have your reasons for installing the AS package, but why
wouldn't you at least advise against it? Even ActiveState doesn't recommend
it unless you absolutely can't install the MSI (or did you just pick it
because it was first in the list?). You do realize that there is no
uninstall option with the AS? So, when all your technically unsavvy people
realize your tutorial is garbage, they're going to be pretty mad to find out
they have to clean out their registry manually.
Matt
btw: Mb is the proper abbreviation, not Meg...
------------------------------
Date: Sat, 31 Jan 2004 19:53:49 -0000
From: "David K. Wall" <dwall@fastmail.fm>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <Xns9481978B1775Bdkwwashere@216.168.3.30>
"edgrsprj" <edgrsprj@ix.netcom.com> wrote:
> People who would like to see Perl used by more people around the world
> might want to examine that Web page and post comments about it here or
> send them to me by e-mail. I believe that all of the commands on that
> page will work as is. But they should probably be checked for errors by
> someone other than me.
>
> Unless there is some good reason not to do this then early next week I
> will probably begin letting people around the world know about that Web
> page.
One very good reason not to do this is because http://learn.perl.org/
already exists. If you really want to help people, send them there.
I don't consider myself an expert at programming or Perl, but even so I can
see numerous incorrect, incomplete, and misleading statements on that page.
As Ben Morrow said, what you want to do is laudable, but you'll be doing
people a disservice by sending them to your page.
I also tried to write a Perl tutorial at one time. After writing several
pages I realized I didn't know enough to write a tutorial and stopped.
Luckily for the world, my incomplete tutorial no longer exists and no-one
but me saw it.
--
David Wall
------------------------------
Date: Sat, 31 Jan 2004 19:56:31 +0000
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <Pine.LNX.4.53.0401311940400.7469@ppepc56.ph.gla.ac.uk>
On Sat, 31 Jan 2004, Walter Roberson wrote:
> [Last time I posted mentioning that I'd seen it used in the UK, someone
> replied to the effect of "No, it isn't used here!". Gee, I guess my
> eyes must have been playing tricks on me...]
Sorry, but I think you've been seeing a cursively-handwritten "lb".
They do look very similar.
However, when trying to name characters in an international context,
I'd suggest it's best to stick to the Unicode names, or at least
something close enough to be recognised as such - we don't all care
for names like "LATIN CAPITAL LETTER O WITH CIRCUMFLEX" in all their
Unicode uppercase glory, but at least we can use a term which
distinguishes clearly enough between "POUND SIGN" (U+00A3, the pound
sterling currency character) and "NUMBER SIGN" (U+0023).
------------------------------
Date: 31 Jan 2004 20:48:44 GMT
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <slrnc1o5ep.73q.tim@kimari.saiyix>
Matt Garrish <matthew.garrish@sympatico.ca> wrote:
[...]
> > downloaded was about 12 million bytes in size (12 Meg).
>
[...]
> btw: Mb is the proper abbreviation, not Meg...
%abbrev = (
MB => 'megabytes',
Mb => 'megabits',
);
Tim Hammerquist
------------------------------
Date: Sat, 31 Jan 2004 15:25:01 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <slrnc1o79d.ssa.tadmc@magna.augustmail.com>
edgrsprj <edgrsprj@ix.netcom.com> wrote:
> Unfortunately I have been encountering one major problem with
> it. And that is with its documentation.
> Perl's structure which I myself do not yet fully understand. So what I have
> been doing while I have been learning how to use it
You do not fully understand it and are just learning it, yet _you_
are qualified to instruct others in how to use it?
That is ludicrous.
> Unless there is some good reason not to do this then early next week I will
> probably begin letting people around the world know about that Web page.
You should not be so mean to people around the world.
You would be doing them a great DISservice.
Perhaps your intentions are honorable, but carrying them out as
you suggest would be dishonorable. Please don't.
> However, my Web page is intended to provide people with
> a certain type of information.
Wrong information written by someone who doesn't understand
what it is that they are writing about?
It that the type of information you meant?
People don't need that type of information. It hurts them more
that it helps them.
> And it will probably remain active even if I
> learn that there are already some excellent reference manuals available.
I, for one, will do my best to steer people *away* from it.
No information is better than wrong information.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 31 Jan 2004 16:55:34 -0500
From: Robert <bobx@linuxmail.org>
Subject: Re: Perl For Amateur Computer Programmers
Message-Id: <C7GdnX7iicvLuYHdRVn-hA@adelphia.com>
It is insane not to use the ActiveState MSI installer.
Get the book:
Elements of Programming with Perl
Andrew L. Johnson
October 1999
This is a great book that you can get fairly cheaply off of Amazon. I am
about half way through it and it is wonderful. You can even talk to the
autor off of the Manning site if you have questions.
------------------------------
Date: Sat, 31 Jan 2004 11:17:56 -0500
From: Brad Baxter <bmb@ginger.libs.uga.edu>
Subject: Re: printing sub results in heredocs
Message-Id: <Pine.A41.4.58.0401311110580.10494@ginger.libs.uga.edu>
On Sat, 31 Jan 2004, Gunnar Hjalmarsson wrote:
> Brad Baxter wrote:
> > On Fri, 30 Jan 2004, Brian McCauley wrote:
> >> Actually the context you get after a \ operator is not an
> >> ordinary list context. It is a context unlike any other you'll
> >> ever see in Perl.
> >
> > sub x { 1,2,3 }
> >
> > print \x;
> > print scalar \x;
> >
> > SCALAR(0xf896c)SCALAR(0xf8a50)SCALAR(0xf887c)
> > SCALAR(0xf887c)
>
> You get the same result with this sub:
>
> sub x { wantarray ? (1,2,3) : 'abc' }
>
> So maybe you'd better give Brian right, after all. ;-)
Oh, I'm not disputing anyone, if that's what you mean. I'm now firmly
convinced that avoiding "${\...}" in favor of "@{[...]}" is wise. Until
Brian's comments I was still waffling. :-)
Regards,
Brad
------------------------------
Date: Sat, 31 Jan 2004 16:27:11 +0000
From: Dave Cross <dave@dave.org.uk>
Subject: Re: Template Toolkit ... is there a bug in the ANYCASE setting??
Message-Id: <pan.2004.01.31.16.27.07.730777@dave.org.uk>
On Fri, 23 Jan 2004 01:46:38 -0800, valued customer wrote:
> The code snippet below produces an error "unexpected token (LAST)".
> Changing the ANYCASE property to false (zero) removes the error and
> the code behaves as expected.
>
> The question is, is this a bug? According to the TT2 documentation,
> the ANYCASE property has a side effect of precluding reserved words as
> variable names, does this also preclude using the 'loop.last'
> directive? Any TT2 experts out there? Tips? Suggestions? Thanks in
> advance.
>
> ### INIT library
> use strict;
> use warnings;
> use Template;
>
> ### INIT variables
> my $tt =
> Template->new( { ANYCASE => 1,}) || die "$Template::ERROR\n";
>
> ### INIT Source Data
> my $data = { list => [ qw(one two three four five) ]};
>
> ### PROCESS TEMPLATE
> my $strOut;
> $tt->process(\*DATA, $data, \$strOut) || die $tt->error(), "\n";
> print $strOut;
>
> __DATA__
> [%-FOREACH item = list;
> "<BEGIN>\n" IF loop.first;%]
> [%- item %]
> [%"<END>" IF loop.last;
> END;%]
LAST is also a template directive (for exiting loops) so it seems that the
parser is getting slightly confused in this situation. Probably worth
letting the TT mailing list know (as that's where the real TT experts hang
out).
Dave...
------------------------------
Date: Sat, 31 Jan 2004 16:00:39 +0000 (UTC)
From: bill <bill_knight2@yahoo.com>
Subject: Re: unused lexicals
Message-Id: <bvgjf7$162$1@reader2.panix.com>
Cool! Thanks, Matt.
bill
------------------------------
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 6059
***************************************
