[31484] in Perl-Users-Digest
Perl-Users Digest, Issue: 2743 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Dec 30 11:09:41 2009
Date: Wed, 30 Dec 2009 08:09: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 Wed, 30 Dec 2009 Volume: 11 Number: 2743
Today's topics:
Re: FAQ 5.41 How do I delete a directory tree? <brian.d.foy@gmail.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <spamtotrash@toomuchfiction.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <sysadmin@example.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <ben@morrow.me.uk>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <spamtrap@shermpendley.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <dirk.heinrichs@online.de>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <dirk.heinrichs@online.de>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <nospam-abuse@ilyaz.org>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <ben@morrow.me.uk>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <sysadmin@example.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <dirk.heinrichs@online.de>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <dirk.heinrichs@online.de>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin (Randal L. Schwartz)
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <tadmc@seesig.invalid>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <tadmc@seesig.invalid>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <ben@morrow.me.uk>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <RedGrittyBrick@spamweary.invalid>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <rvtol+usenet@xs4all.nl>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <someone@example.com>
Re: How to put '#!/usr/bin/env perl -w' at the beginnin <hjp-usenet2@hjp.at>
Thanks (was: FAQ 5.41 How do I delete a directory tree? <marc.girod@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 30 Dec 2009 11:14:24 +0100
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 5.41 How do I delete a directory tree?
Message-Id: <301220091114245590%brian.d.foy@gmail.com>
In article
<e58552bc-8266-4e32-881b-c9c5305f3741@k17g2000yqh.googlegroups.com>,
Marc Girod <marc.girod@gmail.com> wrote:
> On Dec 29, 11:00 am, PerlFAQ Server <br...@theperlreview.com> wrote:
>
> > The first argument to "rmtree" is either a string representing a
> This is the 'legacy interface promoted before v2.00'...
> I recently found that different versions expect different syntaxes...
Right. I'll look into this and update the answer.
Thanks,
------------------------------
Date: Tue, 29 Dec 2009 23:55:36 +0000 (UTC)
From: Kevin Collins <spamtotrash@toomuchfiction.com>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <slrnhjl5no.pee.spamtotrash@vai.unix-guy.com>
On 2009-12-29, l v <veatchla@yahoo.com> wrote:
> On 12/29/2009 4:25 PM, Peng Yu wrote:
>> On Dec 29, 4:17 pm, mer...@stonehenge.com (Randal L. Schwartz) wrote:
>>>>>>>> "Peng" == Peng Yu<pengyu...@gmail.com> writes:
>>>
>>> Peng> Since my perl is installed in a nonstandard location, I have to use '/
>>> Peng> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
>>> Peng> to do it.
>>>
>>> Don't use "-w". Add "use warnings;" early in your script.
>>>
>>> Also, /usr/bin/env perl is a hack. You should replace it with your
>>> specific perl path.
>>
>> If I use my specific perl path, it will not be portable, right? After
>> all, if it moves to a different machine, the path has to be fixed.
>
> Create a symbolic link for /usr/bin/perl to your non-standard location
> and you should then be able to use the correct shebang in your Perl scripts.
This assumes you have rights to do that, which is often not the case...
In a similar situation with one of my clients, where I have access only as a
"user" not an "admin" I wrote a ksh wrapper script (perlwrap) that does various
techniques to identify the "correct" perl (based on OS version and
architecture), and then:
exec /path/to/perl "$@"
Then, in my scripts I have:
#!/mypath/perlwrap -w
Of course, that assumes you can store the wrapper script in a fixed path... :)
Kevin
------------------------------
Date: Tue, 29 Dec 2009 16:43:54 -0800
From: Wanna-Be Sys Admin <sysadmin@example.com>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <enx_m.86119$Wd1.43955@newsfe15.iad>
Kevin Collins wrote:
>> Create a symbolic link for /usr/bin/perl to your non-standard
>> location and you should then be able to use the correct shebang in
>> your Perl scripts.
>
> This assumes you have rights to do that, which is often not the
> case...
>
The Op's first post shows they have shell access, and I find that
assumption curious, as I've never seen a system prevent a user from
creating symbolic links (even if it did, it would be unlikely a system
could prevent the user from executing the ln binary they could upload
themselves, even if tehy didn't have access to the compilers). But, I
suppose it's possible. I just think they should call use warnings; at
the top and not have to mess with anything else, though I never, ever
use env in a script myself.
--
Not really a wanna-be, but I don't know everything.
------------------------------
Date: Wed, 30 Dec 2009 01:01:25 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <5clq07-uh22.ln1@osiris.mauzo.dyndns.org>
Quoth Kevin Collins <spamtotrash@toomuchfiction.com>:
>
> In a similar situation with one of my clients, where I have access only as a
> "user" not an "admin" I wrote a ksh wrapper script (perlwrap) that does various
> techniques to identify the "correct" perl (based on OS version and
> architecture), and then:
>
> exec /path/to/perl "$@"
>
> Then, in my scripts I have:
>
> #!/mypath/perlwrap -w
You need to be a little careful here: many Unixes will not allow a
script to appear on the #! line, only a compiled binary (to prevent
recursion), and many (all?) will pass the whole of the rest of the #!
line as a single argument. perl itself does some fancy parsing to make
it seem as though
#!/usr/bin/perl -w -T
works, but this won't work with your perlwrap.
Ben
------------------------------
Date: Tue, 29 Dec 2009 23:48:48 -0500
From: Sherm Pendley <spamtrap@shermpendley.com>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <m2d41xdq33.fsf@shermpendley.com>
Peng Yu <pengyu.ut@gmail.com> writes:
> Since my perl is installed in a nonstandard location, I have to use '/
> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
> to do it.
The "warnings" pragma is preferred over the -w switch now anyway:
use warnings;
That is, unless your question is about switches in general, not -w in
particular.
sherm--
------------------------------
Date: Wed, 30 Dec 2009 09:46:41 +0100
From: Dirk Heinrichs <dirk.heinrichs@online.de>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <hhf41h$iju$2@online.de>
Ilya Zakharevich wrote:
> #!/usr/bin/env perl
> BEGIN { $^W = 1 } # Can't use -w `with env perl'
Yes, you can!
Bye...
Dirk
------------------------------
Date: Wed, 30 Dec 2009 09:52 +0100
From: Dirk Heinrichs <dirk.heinrichs@online.de>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <hhf4bg$iju$4@online.de>
Dirk Heinrichs wrote:
> Ilya Zakharevich wrote:
>
>> #!/usr/bin/env perl
>> BEGIN { $^W = 1 } # Can't use -w `with env perl'
>
> Yes, you can!
Damn, I was so sure that I already did this in the past. You're right, it
doesn't work.
Bye...
Dirk
------------------------------
Date: Wed, 30 Dec 2009 09:21:04 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <slrnhjm6s0.rtb.nospam-abuse@powdermilk.math.berkeley.edu>
On 2009-12-30, Sherm Pendley <spamtrap@shermpendley.com> wrote:
> Peng Yu <pengyu.ut@gmail.com> writes:
>
>> Since my perl is installed in a nonstandard location, I have to use '/
>> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
>> to do it.
>
> The "warnings" pragma is preferred over the -w switch now anyway:
>
> use warnings;
Wrong. `use warning' is useful in a module. It is mostly useless in
a script. One should always use -w in scripts.
Yours,
Ilya
------------------------------
Date: Wed, 30 Dec 2009 00:58:21 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <d6lq07-uh22.ln1@osiris.mauzo.dyndns.org>
Quoth Peng Yu <pengyu.ut@gmail.com>:
> On Dec 29, 4:17 pm, mer...@stonehenge.com (Randal L. Schwartz) wrote:
> > >>>>> "Peng" == Peng Yu <pengyu...@gmail.com> writes:
> >
> > Peng> Since my perl is installed in a nonstandard location, I have to use '/
> > Peng> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
> > Peng> to do it.
> >
> > Don't use "-w". Add "use warnings;" early in your script.
> >
> > Also, /usr/bin/env perl is a hack. You should replace it with your
> > specific perl path.
>
> If I use my specific perl path, it will not be portable, right? After
> all, if it moves to a different machine, the path has to be fixed.
Put the script in a proper CPAN-style distribution, and MakeMaker will
fix up the #! line for you when you install it (to refer to the perl you
ran 'Makefile.PL' with). You also get nice things like automatic
installation of required modules. A useful tool for installing
CPAN-style distributions that aren't on CPAN is pip (which is on CPAN).
It's probably possible to call ExtUtils::MM_Unix->fixin directly, but I
wouldn't recommend it.
Ben
------------------------------
Date: Tue, 29 Dec 2009 16:40:54 -0800
From: Wanna-Be Sys Admin <sysadmin@example.com>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <qkx_m.86118$Wd1.66540@newsfe15.iad>
Peng Yu wrote:
> Since my perl is installed in a nonstandard location, I have to use '/
> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
> to do it.
>
> Currently, I have the following error.
>
> $ head -n 1 ./main.pl
> #!/usr/bin/env perl -w
> $ ./main.pl
> /usr/bin/env: perl -w: No such file or directory
just use "use warnings;" which offers some advantages. Keep the env the
same. Problem solved.
--
Not really a wanna-be, but I don't know everything.
------------------------------
Date: Wed, 30 Dec 2009 09:44:41 +0100
From: Dirk Heinrichs <dirk.heinrichs@online.de>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <hhf3tp$iju$1@online.de>
Ben Morrow wrote:
>
> Quoth Tad McClellan <tadmc@seesig.invalid>:
>> Wanna-Be Sys Admin <sysadmin@example.com> wrote:
>> > Peng Yu wrote:
>> >
>> >> Since my perl is installed in a nonstandard location, I have to use '/
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Please re-read the solution offered...
The offered solution was simply wrong, so what Tad wrote is perfectly valid.
The right solution is to add the "nonstandard" location to $PATH, so that
env can find perl there.
The problem has nothing to do with "-w" at all!!!
Bye...
Dirk
------------------------------
Date: Wed, 30 Dec 2009 09:51:10 +0100
From: Dirk Heinrichs <dirk.heinrichs@online.de>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <hhf49u$iju$3@online.de>
Dirk Heinrichs wrote:
> The offered solution was simply wrong, so what Tad wrote is perfectly
> valid. The right solution is to add the "nonstandard" location to $PATH,
> so that env can find perl there.
>
> The problem has nothing to do with "-w" at all!!!
Damn, forgot to switch on brain. No, one can not use '#!/usr/bin/env perl -
w'.
Sorry for the noise.
Bye...
Dirk
------------------------------
Date: Wed, 30 Dec 2009 07:26:52 -0800
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <86ljgka3er.fsf@blue.stonehenge.com>
>>>>> "Ruud" == Ruud <rvtol+usenet@xs4all.nl> writes:
Ruud> I prefer -w in scripts too, because it enforces warnings on the included
Ruud> code.
So you want to spend time debugging someone else's code? :)
I put "use warnings" on the code I write while I'm writing it. I'm presuming
the authors of other modules put use warnings on their code while they're
writing it.
Keep in mind that "use warnings" has value *only* while coding. It has no
practical value in production, so if you're using CPAN modules, you really
*don't* want warnings enabled on them, because you're not the author of that
code.
print "Just another Perl hacker,";
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 29 Dec 2009 20:27:08 -0600
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <slrnhjledh.291.tadmc@tadbox.sbcglobal.net>
Wanna-Be Sys Admin <sysadmin@example.com> wrote:
> Kevin Collins wrote:
>
>>> Create a symbolic link for /usr/bin/perl to your non-standard
>>> location and you should then be able to use the correct shebang in
>>> your Perl scripts.
>>
>> This assumes you have rights to do that, which is often not the
>> case...
>>
>
> The Op's first post shows they have shell access, and I find that
> assumption curious, as I've never seen a system prevent a user from
> creating symbolic links
Every system you've seen gives write permission
on /usr/bin to ordinary users?
I have never seen a system that gives write permission
on /usr/bin to ordinary users...
> (even if it did, it would be unlikely a system
> could prevent the user from executing the ln binary they could upload
> themselves,
errr, like a perl binary perhaps?
perldoc -f symlink
> even if tehy didn't have access to the compilers). But, I
> suppose it's possible. I just think they should call use warnings; at
> the top
We all think that (except the OP, who has hopefully been converted by now)
> and not have to mess with anything else, though I never, ever
> use env in a script myself.
You have not addressed the OP's primary problem.
His binary is not at /usr/bin/perl and may in fact be in yet a
third place when moved to another system.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
------------------------------
Date: Tue, 29 Dec 2009 20:29:28 -0600
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <slrnhjleht.291.tadmc@tadbox.sbcglobal.net>
Wanna-Be Sys Admin <sysadmin@example.com> wrote:
> Peng Yu wrote:
>
>> Since my perl is installed in a nonstandard location, I have to use '/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
>> to do it.
>>
>> Currently, I have the following error.
>>
>> $ head -n 1 ./main.pl
>> #!/usr/bin/env perl -w
>> $ ./main.pl
>> /usr/bin/env: perl -w: No such file or directory
>
> just use "use warnings;" which offers some advantages. Keep the env the
> same. Problem solved.
Please re-read the problem statement...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
------------------------------
Date: Wed, 30 Dec 2009 04:30:09 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <hj1r07-kqc2.ln1@osiris.mauzo.dyndns.org>
Quoth Tad McClellan <tadmc@seesig.invalid>:
> Wanna-Be Sys Admin <sysadmin@example.com> wrote:
> > Peng Yu wrote:
> >
> >> Since my perl is installed in a nonstandard location, I have to use '/
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
> >> to do it.
> >>
> >> Currently, I have the following error.
> >>
> >> $ head -n 1 ./main.pl
> >> #!/usr/bin/env perl -w
> >> $ ./main.pl
> >> /usr/bin/env: perl -w: No such file or directory
> >
> > just use "use warnings;" which offers some advantages. Keep the env the
^^^^^^^^^^^^^^^^
> > same. Problem solved.
^^^^^
...that is, use
#!/usr/bin/env perl
use warnings;
so that the kernel can pass 'perl' as a single argument to env(1) and it
will work as expected.
> Please re-read the problem statement...
Please re-read the solution offered...
:)
(Not that I think this is a good solution. env(1) on the #! line is a
security risk, since you don't know what's in the PATH; I've always
found it a little disconcerting that python recommends
#!/usr/bin/env python
in the standard docs.)
Ben
------------------------------
Date: Wed, 30 Dec 2009 10:22:22 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <4b3b29e0$0$2475$db0fefd9@news.zen.co.uk>
Ilya Zakharevich wrote:
> On 2009-12-30, Sherm Pendley <spamtrap@shermpendley.com> wrote:
>> Peng Yu <pengyu.ut@gmail.com> writes:
>>
>>> Since my perl is installed in a nonstandard location, I have to use '/
>>> usr/bin/env perl'. I also what to use it with '-w'. I'm wondering how
>>> to do it.
>> The "warnings" pragma is preferred over the -w switch now anyway:
>>
>> use warnings;
>
> Wrong. `use warning' is useful in a module. It is mostly useless in
> a script. One should always use -w in scripts.
>
Can anyone provide a reference to where Ilya (or anyone else) provides
an explanation of this assertion?
It doesn't seem to be in accord with `perldoc perllexwarn`. Am I right
to assume there is some disagreement on this point?
--
RGB
------------------------------
Date: Wed, 30 Dec 2009 12:13:08 +0100
From: "Dr.Ruud" <rvtol+usenet@xs4all.nl>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <4b3b35c4$0$22933$e4fe514c@news.xs4all.nl>
RedGrittyBrick wrote:
> Ilya Zakharevich wrote:
>> `use warning' is useful in a module. It is mostly useless in
>> a script. One should always use -w in scripts.
>
> Can anyone provide a reference to where Ilya (or anyone else) provides
> an explanation of this assertion?
>
> It doesn't seem to be in accord with `perldoc perllexwarn`. Am I right
> to assume there is some disagreement on this point?
I prefer -w in scripts too, because it enforces warnings on the included
code.
The 'use warnings' is only lexical, that's all there is to it.
--
Ruud
------------------------------
Date: Wed, 30 Dec 2009 07:29:04 -0800
From: "John W. Krahn" <someone@example.com>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <llK_m.99193$Zu5.62570@newsfe24.iad>
Dr.Ruud wrote:
> RedGrittyBrick wrote:
>> Ilya Zakharevich wrote:
>
>>> `use warning' is useful in a module. It is mostly useless in
>>> a script. One should always use -w in scripts.
>>
>> Can anyone provide a reference to where Ilya (or anyone else) provides
>> an explanation of this assertion?
>>
>> It doesn't seem to be in accord with `perldoc perllexwarn`. Am I right
>> to assume there is some disagreement on this point?
>
> I prefer -w in scripts too, because it enforces warnings on the included
> code.
Then you probably want to use -W instead of -w.
John
--
The programmer is fighting against the two most
destructive forces in the universe: entropy and
human stupidity. -- Damian Conway
------------------------------
Date: Wed, 30 Dec 2009 16:57:56 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: How to put '#!/usr/bin/env perl -w' at the beginning of a perl script?
Message-Id: <slrnhjmu45.4kq.hjp-usenet2@hrunkner.hjp.at>
On 2009-12-30 11:13, Dr.Ruud <rvtol+usenet@xs4all.nl> wrote:
> RedGrittyBrick wrote:
>> Ilya Zakharevich wrote:
>>> `use warning' is useful in a module. It is mostly useless in
>>> a script. One should always use -w in scripts.
>>
>> Can anyone provide a reference to where Ilya (or anyone else) provides
>> an explanation of this assertion?
>>
>> It doesn't seem to be in accord with `perldoc perllexwarn`. Am I right
>> to assume there is some disagreement on this point?
>
> I prefer -w in scripts too, because it enforces warnings on the included
> code.
Which is why I disagree with Ilya and you. -w is mostly useless in a
script and should never be used except maybe as a quick hack during
debugging.
> The 'use warnings' is only lexical, that's all there is to it.
And I think this is a good thing. Getting lots of warnings in code I
haven't written and cannot change[1][2] is not very helpful. And most
modules use "use warnings" anyway, so it's usually redundant (and you
probably should be wary of those that don't use it).
I do think it was a good thing that -w was invented before "use
warnings": It forced module maintainers to clean up their code.
hp
[1] Well, *I* can change it because I'm sysadmin on most of the systems
where my code runs. But that's far from universal.
[2] I remember the bad old days of C programming where you could choose
between getting lots of warnings from system header files and turning
off many useful warnings.
------------------------------
Date: Wed, 30 Dec 2009 05:54:04 -0800 (PST)
From: Marc Girod <marc.girod@gmail.com>
Subject: Thanks (was: FAQ 5.41 How do I delete a directory tree?)
Message-Id: <f07495a5-5c8d-4151-a729-11f6bdc87c3c@r5g2000yqb.googlegroups.com>
On Dec 30, 10:14=A0am, brian d foy <brian.d....@gmail.com> wrote:
> Thanks,
Thanks to you Brian.
I find this random reading of the FAQs very
useful. I am seldom smart enough to make
those questions, the answers to which are
so interesting.
I usually try to keep silent when I have
nothing to say. Please know to take it as
an expression of gratitude.
Marc
------------------------------
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 2743
***************************************
