[25399] in Perl-Users-Digest
Perl-Users Digest, Issue: 7644 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 14 00:05:33 2005
Date: Thu, 13 Jan 2005 21:05:16 -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 Thu, 13 Jan 2005 Volume: 10 Number: 7644
Today's topics:
Re: [perl-python] 20050112 while statement <abigail@abigail.nl>
Re: [perl-python] 20050112 while statement <cwilbur@mithril.chromatico.net>
Re: Adding a delimiter inbetween number characters and <news@chaos-net.de>
Re: Adding a delimiter inbetween number characters and <1usa@llenroc.ude.invalid>
Re: Adding a delimiter inbetween number characters and <news@chaos-net.de>
Re: Adding a delimiter inbetween number characters and <1usa@llenroc.ude.invalid>
Re: Advice on starting form based application <noreply@gunnar.cc>
Re: convention regarding lexical filehandles <abigail@abigail.nl>
Re: convention regarding lexical filehandles <spamtrap@dot-app.org>
Re: convention regarding lexical filehandles <tadmc@augustmail.com>
Re: Formmail Question <tadmc@augustmail.com>
how could i get perl module in unix? <mic.check@gmail.com>
Re: how could i get perl module in unix? <spamtrap@dot-app.org>
Re: how could i get perl module in unix? <tony_curtis32@yahoo.com>
Re: how could i get perl module in unix? <spamtrap@dot-app.org>
Re: how could i get perl module in unix? <1usa@llenroc.ude.invalid>
how to control stdout buffer?? <sonet.all@msa.hinet.net>
Re: how to control stdout buffer?? <1usa@llenroc.ude.invalid>
Log File parser <georgemj@sympatico.ca>
Re: Log File parser <spamtrap@dot-app.org>
Re: Log File parser <georgemj@sympatico.ca>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 13 Jan 2005 23:35:41 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: [perl-python] 20050112 while statement
Message-Id: <slrncue1ed.ucb.abigail@alexandra.abigail.nl>
Xah Lee (xah@xahlee.org) wrote on MMMMCLIII September MCMXCIII in
<URL:news:1105611506.106440.135670@f14g2000cwb.googlegroups.com>:
.. # here's a while statement in python.
..
.. a,b = 0,1
.. while b < 20:
.. print b
IndentationError: expected an indented block
.. a,b = b,a+b
You have already proven you don't know Perl, but now it turns
out, you don't know Python either.
Go away.
Abigail
--
package Z;use overload'""'=>sub{$b++?Hacker:Another};
sub TIESCALAR{bless\my$y=>Z}sub FETCH{$a++?Perl:Just}
$,=$";my$x=tie+my$y=>Z;print$y,$x,$y,$x,"\n";#Abigail
------------------------------
Date: Thu, 13 Jan 2005 23:59:30 GMT
From: Charlton Wilbur <cwilbur@mithril.chromatico.net>
Subject: Re: [perl-python] 20050112 while statement
Message-Id: <87fz14q45j.fsf@mithril.chromatico.net>
>>>>> "b" == brianr <brianr@liffe.com> writes:
b> (As a matter of interest, is this sequence of posts intended to
b> demonstrate ignorance of both languages, or just one?)
Intentional fallacy -- there's no necessary correlation between what
he *intends* to do and what he actually succeeds at doing. As noted,
Xah *intends* to use his expertise in Perl to teach Python to others.
All he's succeeding in doing is demonstrating his incompetence at
both. As for myself, I suspect it's just a cunning approach to Let's
You And Him Fight.
Charlton
--
cwilbur at chromatico dot net
cwilbur at mac dot com
------------------------------
Date: 14 Jan 2005 00:24:40 GMT
From: Martin Kissner <news@chaos-net.de>
Subject: Re: Adding a delimiter inbetween number characters and letter characters
Message-Id: <slrncue4a8.14l.news@maki.homeunix.net>
Michele Dondi wrote :
> On 12 Jan 2005 19:20:48 GMT, Martin Kissner <news@chaos-net.de> wrote:
>
> There's hardly any need IMHO to include line numbers. To be fair,
> personally I find them to be disturbing...
>
I forgot to "set :nonu" before copying.
Sorry for the inconvenience.
>
>> 5 my $lastline="";
>> 6 my @lastline;
>> 7
>> 8 while (<DATA>)
>> 9 {
>> 10 chomp ($lastline) if (/^\D/);
>> 11 &printline;
>> 12 $lastline = $_;
>
> Do you _really_ need this $lastline algorithmic madness?
>
Good question. What do you think of that solution?
#!/usr/bin/perl
use warnings;
use strict;
local $/;
my $content = <DATA>;
$content =~ s/\n\D//g;
$content =~ s/(^\d+|\n\d)/$1-/g;
print $content;
__DATA__
1sampletextsampletextsamplet22tsampletextsampletextsampletext
2sampletextsampletextsampletextsam56etextsampletextsampletext
3sampletextsampletextsampletextsampletextsampletextsampletext
[...]
>> 13 }
>> 14 &printline;
>
> There's no need to use the &-form of sub call in Perl5: most likely it
> won't do what you mean. See 'perldoc perlsub'.
>
Just to make sure I understood:
Is the foo() form cheaper because it doesn't pass @_ ?
Thank you, for your feedback.
--
Epur Si Muove (Gallileo Gallilei)
------------------------------
Date: 14 Jan 2005 01:35:49 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Adding a delimiter inbetween number characters and letter characters
Message-Id: <Xns95DDD185E8A96asu1cornelledu@132.236.56.8>
Martin Kissner <news@chaos-net.de> wrote in
news:slrncue4a8.14l.news@maki.homeunix.net:
> Michele Dondi wrote :
>> On 12 Jan 2005 19:20:48 GMT, Martin Kissner <news@chaos-net.de> wrote:
>> There's no need to use the &-form of sub call in Perl5: most likely it
>> won't do what you mean. See 'perldoc perlsub'.
>>
> Just to make sure I understood:
> Is the foo() form cheaper because it doesn't pass @_ ?
I am curious, did you actually bother to read 'perldoc perlsub'?
... If a subroutine is called using the "&" form, the argument list
is optional, and if omitted, no @_ array is set up for the subroutine:
the @_ array at the time of the call is visible to subroutine instead.
This is an efficiency mechanism that new users may wish to avoid.
If you use the foo() form, you are not passing any arguments at all. That is
allright if the sub does not take any arguments, but would be a problem if
the sub needed arguments to do its job. Please read (or re-read) perldoc
perlsub in its entirety to understand why the &foo is useful only in very few
specific instances.
Sinan
------------------------------
Date: 14 Jan 2005 04:22:21 GMT
From: Martin Kissner <news@chaos-net.de>
Subject: Re: Adding a delimiter inbetween number characters and letter characters
Message-Id: <slrncuei7t.14l.news@maki.homeunix.net>
A. Sinan Unur wrote :
> Martin Kissner <news@chaos-net.de> wrote in
> news:slrncue4a8.14l.news@maki.homeunix.net:
>
>> Just to make sure I understood:
>> Is the foo() form cheaper because it doesn't pass @_ ?
>
> I am curious, did you actually bother to read 'perldoc perlsub'?
I didn't read all of it; it has more than 1300 lines.
But I tried to find, what Michele wanted to point me at.
English is not my native language.
Therefore reading (and understanding!) the docs is difficult for me and
takes a lot of time.
> ... If a subroutine is called using the "&" form, the argument list
> is optional, and if omitted, no @_ array is set up for the subroutine:
> the @_ array at the time of the call is visible to subroutine instead.
> This is an efficiency mechanism that new users may wish to avoid.
I did read that, but i didn't really understand why it should be
necessary to avoid this.
> [...] . Please read (or re-read) perldoc
> perlsub in its entirety to understand why the &foo is useful only in very few
> specific instances.
Well, I really tried, but things didn't get much clearer.
As far as I understand "new-style calls" enable subroutines which can
behave like built-in functions (which is beyond my scope for now).
Is that what you mean?
I'd appreciate if you could point me to a particular section of perlsub
to help me understand.
Thank you for your help.
Martin
--
Epur Si Muove (Gallileo Gallilei)
------------------------------
Date: 14 Jan 2005 04:54:01 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Adding a delimiter inbetween number characters and letter characters
Message-Id: <Xns95DDF31FCD7E6asu1cornelledu@132.236.56.8>
Martin Kissner <news@chaos-net.de> wrote in
news:slrncuei7t.14l.news@maki.homeunix.net:
> A. Sinan Unur wrote :
>> Martin Kissner <news@chaos-net.de> wrote in
>> news:slrncue4a8.14l.news@maki.homeunix.net:
>>
>>> Just to make sure I understood:
>>> Is the foo() form cheaper because it doesn't pass @_ ?
>>
>> I am curious, did you actually bother to read 'perldoc perlsub'?
> I didn't read all of it; it has more than 1300 lines.
Well, you should read all of it as many times as necessary.
> But I tried to find, what Michele wanted to point me at.
> English is not my native language.
Nor is it mine.
> Therefore reading (and understanding!) the docs is difficult for me
> and takes a lot of time.
You should spend as much time as needed.
>> ... If a subroutine is called using the "&" form, the argument list
>> is optional, and if omitted, no @_ array is set up for the
>> subroutine: the @_ array at the time of the call is visible to
>> subroutine instead. This is an efficiency mechanism that new users
>> may wish to avoid.
>
> I did read that, but i didn't really understand why it should be
> necessary to avoid this.
Just a simple example:
#! perl
use strict;
use warnings;
sub mysub {
join ':', @_;
}
print mysub 'Drive', 'Directory', "\n";
print &mysub 'Drive', 'Directory', "\n";
I am not particularly inclined to spend a lot of time with this at this
point. Unless you _know_ that you need & for a specific reason, you are
better off not using it. Simple rule, really.
>> [...] . Please read (or re-read) perldoc
>> perlsub in its entirety to understand why the &foo is useful only in
>> very few specific instances.
> Well, I really tried, but things didn't get much clearer.
> As far as I understand "new-style calls" enable subroutines which can
> behave like built-in functions (which is beyond my scope for now).
AFAIK, that is made possible with the use of prototypes.
> I'd appreciate if you could point me to a particular section of
> perlsub to help me understand.
But I did. Are you so lazy that you did not bother to read the few lines
below the specific paragraph I quoted.
Sinan.
------------------------------
Date: Fri, 14 Jan 2005 00:17:46 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Advice on starting form based application
Message-Id: <34odt2F4d0aaaU1@individual.net>
dbmeyers23@yahoo.com wrote:
> If I'm printing these results to a file, is there a way to know where
> the values came from?
There are obviously many ways.
> $query = CGI::new();
> print $query->header();
Didn't you say that you wanted to print them to a file?
> So let's say they fill in everything above, excpet "a2"...how could
> easily print this to a flat file so it looks like this.
> Agency: Paper co.
> Home Date: 12-12-2005
> etc....
Whereever you print the stuff, hardcoding a list of param/label pairs is
one way:
my @labels = (
[ clientname => 'Client Name' ],
[ agency => 'Agency' ],
[ homedate => 'Home Date' ],
[ a1 => 'A1' ],
[ a2 => 'A2' ],
);
for (@labels) {
if ( $query->param( $$_[0] ) ) {
print "$$_[1]: ", $query->param( $$_[0] ), "\n";
}
}
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: 14 Jan 2005 00:30:07 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: convention regarding lexical filehandles
Message-Id: <slrncue4kf.e1.abigail@alexandra.abigail.nl>
Sherm Pendley (spamtrap@dot-app.org) wrote on MMMMCLIII September
MCMXCIII in <URL:news:NuGdnX-8JPJ0fXvcRVn-hw@adelphia.com>:
@@ Paul Lalli wrote:
@@
@@ > This one I've never really understood. I'm going to go take a look at
@@ > perlopentut, but if you'd care to explain in what way the two-argument
@@ > form is dangerous, I'd appreciate it.
@@
@@ Think about what might happen if one of your users names a file ">file.txt",
@@ and your app uses "open HANDLE, $filename" to open $filename for reading.
Well, so what? The user loses his file. Big deal. Had he typed
$ cat >file.txt
he would have lost his file too.
If someone is stupid (and knowledged) enough to create a file called
">file.txt", it's HIS responsibility to make sure the file won't get
globbered.
Abigail
--
# Count the number of lines; code doesn't match \w. Linux specific.
()=<>;$!=$=;($:,$,,$;,$")=$!=~/.(.)..(.)(.)..(.)/;
$;++;$*++;$;++;$*++;$;++;`$:$,$;$" $. >&$*`;
------------------------------
Date: Thu, 13 Jan 2005 21:43:47 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: convention regarding lexical filehandles
Message-Id: <ELudnWxHf9V4rHrcRVn-pg@adelphia.com>
Abigail wrote:
> Well, so what? The user loses his file. Big deal. Had he typed
>
> $ cat >file.txt
>
> he would have lost his file too.
Yes, but that's due to a mistake on the user's part, not cat's. Had the user
correctly typed
$ cat ">file.txt"
instead, "cat" would have behaved correctly. In the case of a Perl script
that uses "open FILE, $filename", there would be *no* correct way for the
user to run the script. The file gets overwritten even if the user
correctly quotes it when he runs the script.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Thu, 13 Jan 2005 21:49:27 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: convention regarding lexical filehandles
Message-Id: <slrncuega7.2i7.tadmc@magna.augustmail.com>
Paul Lalli <mritty@gmail.com> wrote:
> Prior to the invention of lexical file handles, I'd always seen the
> convention that filehandles should be given in all capital letters:
> open FILE, 'file.txt' or die "...";
>
> Now that we have lexical file handles, I'm wondering if there is a
> consensus as towards this convention.
IMO, the reason for the convention is to avoid collisions
with built-in functions:
open file, 'file.txt' or die "...";
works fine today, but will break when you update your perl version
and it introduces a brand-new function named file().
In other words, the convention is a consequence of filehandles
being sigil-less, hence confusing the parser when the FH is
a function call rather than a bareword.
Or, maybe it would just confuse the programmer that his untouched
program stopped working when he upgraded perl...
So, you only need upper case to get the parser to apply the
semantic that you intend with filehandles, you don't need
to resort to that trickery with lexical filehandles.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 13 Jan 2005 22:00:19 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Formmail Question
Message-Id: <slrncueguj.2i7.tadmc@magna.augustmail.com>
Deepster <deepiceman@yahoo.com> wrote:
> I want to use formmail
No you don't.
Crackers cruise the web looking for sites that use Matt's scripts
so they can exploit any of several security holes.
If you still *want* that, then you must be a real thrill seeker,
consider taking up skydiving instead. :-)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 13 Jan 2005 18:42:45 -0800
From: "NCS+" <mic.check@gmail.com>
Subject: how could i get perl module in unix?
Message-Id: <1105670565.634346.138200@c13g2000cwb.googlegroups.com>
i'm a stater in Perl.
when wrote the code
use LWP 5.64
an error occured.
------------------------------
Date: Thu, 13 Jan 2005 21:54:21 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: how could i get perl module in unix?
Message-Id: <rbWdnaL6XrPCqXrcRVn-tQ@adelphia.com>
NCS+ wrote:
> i'm a stater in Perl.
A great place to start is here:
<http://learn.perl.org>
Also, if you haven't done so already, please read the posting guidelines for
this group. They appear here frequently.
> when wrote the code
>
> use LWP 5.64
>
> an error occured.
Naturally - that's not how you use "use". Have a look at the docs for the
function you're using:
perldoc -f use
The questions of how to get modules, how to find out what ones you have, and
how to install them are all answered in the FAQ. Have a look at:
perldoc -q module
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Thu, 13 Jan 2005 20:55:10 -0600
From: Tony Curtis <tony_curtis32@yahoo.com>
Subject: Re: how could i get perl module in unix?
Message-Id: <87zmzcbtyp.fsf@limey.hpcc.uh.edu>
>> On 13 Jan 2005 18:42:45 -0800,
>> "NCS+" <mic.check@gmail.com> said:
> i'm a stater in Perl. when wrote the code
> use LWP 5.64
> an error occured.
But you don't feel like sharing the error text with us?
$ perl -e 'use LWP 5.64'
$
Not sure what you're trying to do, but it doesn't generate an
error. There's more code isn't there? Please show us a
small program that generates this error, and the output from a
run of it. (Also, platform you're using, perl version).
------------------------------
Date: Thu, 13 Jan 2005 21:59:33 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: how could i get perl module in unix?
Message-Id: <rbWdnd36XrMIqHrcRVn-tQ@adelphia.com>
Sherm Pendley wrote:
> NCS+ wrote:
>
>> use LWP 5.64
>>
>> an error occured.
>
> Naturally - that's not how you use "use".
Scratch that part. You *can* specify a minimum version number for a module -
I'd forgotten that. Sorry, my mistake.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: 14 Jan 2005 03:19:28 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: how could i get perl module in unix?
Message-Id: <Xns95DDE317D4BABasu1cornelledu@132.236.56.8>
Sherm Pendley <spamtrap@dot-app.org> wrote in
news:rbWdnd36XrMIqHrcRVn-tQ@adelphia.com:
> Sherm Pendley wrote:
>
>> NCS+ wrote:
>>
>>> use LWP 5.64
>>>
>>> an error occured.
>>
>> Naturally - that's not how you use "use".
>
> Scratch that part. You *can* specify a minimum version number for a
> module - I'd forgotten that. Sorry, my mistake.
OTOH, the missing semi-colon at the end of the line above would cause
problems if it appeared in a source file.
The OP would benefit from reading the posting guidelines posted here
regularly in so that he can better describe the context in which he is
encountering this problem.
Sinan.
------------------------------
Date: Fri, 14 Jan 2005 12:02:16 +0800
From: "sonet" <sonet.all@msa.hinet.net>
Subject: how to control stdout buffer??
Message-Id: <cs7g9d$sv9$1@netnews.hinet.net>
#!/usr/bin/perl
$|=1;
print "Content-Type: text/plain\r\n\r\n";
print `ldapsearch -b dc=abc,dc=edu -D cn=Manager,dc=abc,dc=edu -w abc -h
ldap.abc.edu -LLL "uid=*"`;
If i do this job in unix comand ,the stdout will continue output.
But if i do this job in cgi,the stdout will pause to output until the
ldapsearch complete.
And this process will cost about 10 mins.
How to control the cgi stdout buffer?
------------------------------
Date: 14 Jan 2005 04:34:16 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: how to control stdout buffer??
Message-Id: <Xns95DDEFC6E689Casu1cornelledu@132.236.56.8>
"sonet" <sonet.all@msa.hinet.net> wrote in
news:cs7g9d$sv9$1@netnews.hinet.net:
> #!/usr/bin/perl
> $|=1;
> print "Content-Type: text/plain\r\n\r\n";
> print `ldapsearch -b dc=abc,dc=edu -D cn=Manager,dc=abc,dc=edu -w abc
> -h ldap.abc.edu -LLL "uid=*"`;
>
> If i do this job in unix comand ,the stdout will continue output.
> But if i do this job in cgi,the stdout will pause to output until the
> ldapsearch complete.
The output is not being paused. You have told perl to read all the lines
output by ldapsearch and then print them rather than reading the output
of ldapsearch line by line.
> And this process will cost about 10 mins.
> How to control the cgi stdout buffer?
I am not sure exactly what you are asking, but, either:
http://www.stonehenge.com/merlyn/LinuxMag/col39.html
or
#! perl
$| = 1;
use strict;
use warnings;
open my $ls, 'ls -l . |'
or die "Cannot open pipe to ls: $!";
while(<$ls>) {
print;
sleep 1;
}
close $ls
or die "Cannot close pipe to ls: $!";
__END__
might help.
See perldoc perlopentut and perldoc perlipc for more information on
pipes. Clearly, you would open a pipe to the command whose output you are
interested in rather than to ls.
Sinan.
------------------------------
Date: Thu, 13 Jan 2005 22:52:24 -0500
From: "George Monappallil" <georgemj@sympatico.ca>
Subject: Log File parser
Message-Id: <ZlHFd.32843$b64.1060827@news20.bellglobal.com>
Hi guys:
I am new to perl.Anyone has a perl script that would look for certain words
( ERROR, WARN ) in a log file? I would like the script to send me an
email/page when it encounters any of the words.
Thanks in advance,
-George
------------------------------
Date: Thu, 13 Jan 2005 23:25:54 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Log File parser
Message-Id: <1fCdnWzQUvlI1HrcRVn-ug@adelphia.com>
George Monappallil wrote:
> I am new to perl.Anyone has a perl script that would look for certain
> words ( ERROR, WARN ) in a log file? I would like the script to send me an
> email/page when it encounters any of the words.
What have you written so far? Post what you have, and tell us what part
you're having trouble with, and someone here will undoubtedly be happy to
answer your questions.
If you need help getting started, there are a number of tutorials to be
found at:
<http://learn.perl.org>
If you haven't done so already, please read the posting guidelines for this
group - they're posted here twice a week, so a recent copy should still be
on your news server.
Or to put it another way: "Give a man to fish, and you feed him for a day.
Teach him to fish, and you feed him for a lifetime." We prefer to give
fishing lessons here.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Thu, 13 Jan 2005 23:37:23 -0500
From: "George Monappallil" <georgemj@sympatico.ca>
Subject: Re: Log File parser
Message-Id: <j0IFd.32940$b64.1069805@news20.bellglobal.com>
Great...will do so surely.
-G
"Sherm Pendley" <spamtrap@dot-app.org> wrote in message
news:1fCdnWzQUvlI1HrcRVn-ug@adelphia.com...
> George Monappallil wrote:
>
> > I am new to perl.Anyone has a perl script that would look for certain
> > words ( ERROR, WARN ) in a log file? I would like the script to send me
an
> > email/page when it encounters any of the words.
>
> What have you written so far? Post what you have, and tell us what part
> you're having trouble with, and someone here will undoubtedly be happy to
> answer your questions.
>
> If you need help getting started, there are a number of tutorials to be
> found at:
> <http://learn.perl.org>
>
> If you haven't done so already, please read the posting guidelines for
this
> group - they're posted here twice a week, so a recent copy should still be
> on your news server.
>
> Or to put it another way: "Give a man to fish, and you feed him for a day.
> Teach him to fish, and you feed him for a lifetime." We prefer to give
> fishing lessons here.
>
> sherm--
>
> --
> Cocoa programming in Perl: http://camelbones.sourceforge.net
> Hire me! My resume: http://www.dot-app.org
------------------------------
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 7644
***************************************
