[30265] in Perl-Users-Digest
Perl-Users Digest, Issue: 1508 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun May 4 11:09:42 2008
Date: Sun, 4 May 2008 08:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sun, 4 May 2008 Volume: 11 Number: 1508
Today's topics:
Re: FAQ 3.23 Can I write useful Perl programs on the co <spamtrap@dot-app.org>
Re: FAQ 3.23 Can I write useful Perl programs on the co <benkasminbullock@gmail.com>
How to clear all previous terminal output which is curr (Jason Stacy)
Re: How to clear all previous terminal output which is <jurgenex@hotmail.com>
How to print formatted (!) the current timestamp? (Thomas Blabb)
Re: How to print formatted (!) the current timestamp? <xemoth@gmail.com>
master perl calling slave perl <ela@yantai.org>
Re: master perl calling slave perl <joost@zeekat.nl>
Re: master perl calling slave perl <ela@yantai.org>
Re: master perl calling slave perl <jo@nosp.invalid>
Re: master perl calling slave perl <jurgenex@hotmail.com>
Re: master perl calling slave perl <ela@yantai.org>
new CPAN modules on Sun May 4 2008 (Randal Schwartz)
Re: Read 20 lines when pressing n for next <get@bentsys.com>
Re: Stuffing @users into $self->{'users'} <ben@morrow.me.uk>
Re: Stuffing @users into $self->{'users'} <hjp-usenet2@hjp.at>
Re: Stuffing @users into $self->{'users'} <peter@makholm.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 04 May 2008 00:59:43 -0400
From: Sherman Pendley <spamtrap@dot-app.org>
Subject: Re: FAQ 3.23 Can I write useful Perl programs on the command line?
Message-Id: <m1zlr6u0jk.fsf@dot-app.org>
Ben Bullock <benkasminbullock@gmail.com> writes:
> On Sat, 03 May 2008 12:03:02 -0700, PerlFAQ Server wrote:
>
>> 3.23: Can I write useful Perl programs on the command line?
>
> Has anybody ever, even once, asked this question, or even something
> similar to it? I just can't imagine anybody asking that kind of question.
That's the ever-lasting mystery of FAQs - if they do their job, the Qs are
no longer so F any more. :-)
sherm--
--
My blog: http://shermspace.blogspot.com
Cocoa programming in Perl: http://camelbones.sourceforge.net
------------------------------
Date: Sun, 4 May 2008 05:37:14 -0700 (PDT)
From: Ben Bullock <benkasminbullock@gmail.com>
Subject: Re: FAQ 3.23 Can I write useful Perl programs on the command line?
Message-Id: <43a75974-ec4c-41d3-8912-4a8b873190e3@u12g2000prd.googlegroups.com>
On May 4, 1:59 pm, Sherman Pendley <spamt...@dot-app.org> wrote:
> Ben Bullock <benkasminbull...@gmail.com> writes:
> > On Sat, 03 May 2008 12:03:02 -0700, PerlFAQ Server wrote:
>
> >> 3.23: Can I write useful Perl programs on the command line?
>
> > Has anybody ever, even once, asked this question, or even something
> > similar to it? I just can't imagine anybody asking that kind of question.
>
> That's the ever-lasting mystery of FAQs - if they do their job, the Qs are
> no longer so F any more. :-)
I'm pretty sure that Q has never been F let alone A.
------------------------------
Date: 04 May 2008 12:17:33 GMT
From: jjstacy@yahoo.net (Jason Stacy)
Subject: How to clear all previous terminal output which is currently visible?
Message-Id: <481da95d$0$7537$9b4e6d93@newsspool1.arcor-online.net>
Assume I have opened a terminal and already performed some commands which produced some
output lines.
Then I start a perl script which outputs also some line of text.
However I want at first all previous output lines in the terminal to be wiped.
All output should start with an "empty" terminal (of cause beside the prompt).
How can I wipe all old stuff?
In Windows command prompt there is a "cls" command but is not working in
perl/Linux terminals.
Is there an equivalent command?
Jason
------------------------------
Date: Sun, 04 May 2008 12:31:21 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: How to clear all previous terminal output which is currently visible?
Message-Id: <v1br145c2trf51io6o8dc9b8oblthfs0u1@4ax.com>
jjstacy@yahoo.net (Jason Stacy) wrote:
>However I want at first all previous output lines in the terminal to be wiped.
>How can I wipe all old stuff?
perldoc -q clear: "How do I clear the screen?"
jue
------------------------------
Date: 04 May 2008 09:09:46 GMT
From: t.blabb@gmail.com (Thomas Blabb)
Subject: How to print formatted (!) the current timestamp?
Message-Id: <481d7d5a$0$6503$9b4e6d93@newsspool4.arcor-online.net>
I want to print the current time(stamp) in formatted style.
The following does not work:
print STDOUT "Now=%Y%m%d-%H%M\n", localtime(time);
What is wrong?
How else can I print out a formatted timestamp?
Tom
------------------------------
Date: Sun, 4 May 2008 03:03:51 -0700 (PDT)
From: Owen <xemoth@gmail.com>
Subject: Re: How to print formatted (!) the current timestamp?
Message-Id: <faf097ae-d354-4638-a358-bf512b268e61@b5g2000pri.googlegroups.com>
On May 4, 7:09 pm, t.bl...@gmail.com (Thomas Blabb) wrote:
> I want to print the current time(stamp) in formatted style.
> The following does not work:
>
> print STDOUT "Now=%Y%m%d-%H%M\n", localtime(time);
>
> What is wrong?
>
> How else can I print out a formatted timestamp?
>
> Tom
Try
use POSIX qw(strftime);
print strftime "%Y%m%d-%H%M\n", localtime;
Owen
------------------------------
Date: Sun, 4 May 2008 14:32:59 +0800
From: "Ela" <ela@yantai.org>
Subject: master perl calling slave perl
Message-Id: <fvjlas$kj2$1@ijustice.itsc.cuhk.edu.hk>
In slave perl prog, there're some print codes.
However, when the master perl calling the slave one by system(command), the
slave perl print cannot be redirected to STDOUT. how to solve that?
------------------------------
Date: Sun, 04 May 2008 09:04:31 +0200
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: master perl calling slave perl
Message-Id: <87zlr6blds.fsf@zeekat.nl>
"Ela" <ela@yantai.org> writes:
> In slave perl prog, there're some print codes.
> However, when the master perl calling the slave one by system(command), the
> slave perl print cannot be redirected to STDOUT.
What? That's what it already does by default.
> how to solve that?
Did you mean something like
system("perl my_other_program.pl > /dev/null") and die;
?
--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/
------------------------------
Date: Sun, 4 May 2008 16:05:04 +0800
From: "Ela" <ela@yantai.org>
Subject: Re: master perl calling slave perl
Message-Id: <fvjqnh$mt6$1@ijustice.itsc.cuhk.edu.hk>
> Did you mean something like
>
> system("perl my_other_program.pl > /dev/null") and die;
>
> ?
>
This makes STDOUT nothing to print, I guess?
When running the slave prog directly by perl slave.pl, something is printed
onto screen
but perl master.pl (master.pl call salve.pl by system) does not
------------------------------
Date: 04 May 2008 10:10:31 GMT
From: Jo <jo@nosp.invalid>
Subject: Re: master perl calling slave perl
Message-Id: <481d8b97$0$14343$e4fe514c@news.xs4all.nl>
Ela said:
> When running the slave prog directly by perl slave.pl, something is
> printed onto screen but
> perl master.pl (master.pl call salve.pl by > system)
> does not
On my system it does.
Maybe you should post a simple example of master.pl and slave.pl
showing when it doesn't.
------------------------------
Date: Sun, 04 May 2008 13:37:55 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: master perl calling slave perl
Message-Id: <ater149ucch8btkdqavcn7s37a1j7oudnn@4ax.com>
"Ela" <ela@yantai.org> wrote:
>In slave perl prog, there're some print codes.
>However, when the master perl calling the slave one by system(command), the
>slave perl print cannot be redirected to STDOUT. how to solve that?
I cannot reproduce your problem:
C:\tmp>type master.pl
use strict; use warnings;
system 'slave.pl';
C:\tmp>type slave.pl
use strict; use warnings;
print "Slave here\n";
C:\tmp>master.pl
Slave here
Obviously the slave program prints to STDOUT just fine.
Please provide a minimal program that demonstrates your problem.
jue
------------------------------
Date: Sun, 4 May 2008 23:03:49 +0800
From: "Ela" <ela@yantai.org>
Subject: Re: master perl calling slave perl
Message-Id: <fvkj8m$1pt$1@ijustice.itsc.cuhk.edu.hk>
"Jo" <jo@nosp.invalid> wrote in message
news:481d8b97$0$14343$e4fe514c@news.xs4all.nl...
> Ela said:
>> When running the slave prog directly by perl slave.pl, something is
>> printed onto screen but
>> perl master.pl (master.pl call salve.pl by > system)
>> does not
>
> On my system it does.
> Maybe you should post a simple example of master.pl and slave.pl
> showing when it doesn't.
>
Oh sorry the perl is called by a master SHELL master.sh but not master
perl...
#!/bin/sh
`perl slave.pl $dirname`
So how to solve?
------------------------------
Date: Sun, 4 May 2008 04:42:17 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Sun May 4 2008
Message-Id: <K0BuEH.1Dun@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Apache-AppSamurai-1.01
http://search.cpan.org/~pauldoom/Apache-AppSamurai-1.01/
An Authenticating Mod_Perl Front End
----
Apache2-ASP-1.39
http://search.cpan.org/~johnd/Apache2-ASP-1.39/
Perl extension for ASP on mod_perl2.
----
App-SVN-Bisect-0.4
http://search.cpan.org/~infinoid/App-SVN-Bisect-0.4/
binary search through svn revisions
----
AutoXS-Header-0.02
http://search.cpan.org/~smueller/AutoXS-Header-0.02/
Container for the AutoXS header files
----
Catalyst-Authentication-Store-Jifty-DBI-0.01
http://search.cpan.org/~ishigaki/Catalyst-Authentication-Store-Jifty-DBI-0.01/
A storage class for Catalyst Authentication using Jifty::DBI
----
Class-XSAccessor-0.03
http://search.cpan.org/~smueller/Class-XSAccessor-0.03/
Generate fast XS accessors without runtime compilation
----
Class-XSAccessor-Array-0.01
http://search.cpan.org/~smueller/Class-XSAccessor-Array-0.01/
Generate fast XS accessors without runtime compilation
----
Curses-UI-POE-0.03
http://search.cpan.org/~tag/Curses-UI-POE-0.03/
----
Date-Holidays-DE-1.0
http://search.cpan.org/~mschmitt/Date-Holidays-DE-1.0/
Determine German holidays
----
Date-Holidays-DE-1.0.1
http://search.cpan.org/~mschmitt/Date-Holidays-DE-1.0.1/
Determine German holidays
----
Encode-ZapCP1252-0.11
http://search.cpan.org/~dwheeler/Encode-ZapCP1252-0.11/
Zap Windows Western Gremlins
----
Games-RailRoad-1.00
http://search.cpan.org/~jquelin/Games-RailRoad-1.00/
a train simulation game
----
Gift-0.7
http://search.cpan.org/~casiano/Gift-0.7/
Parser for Moodle Gift format
----
Gift-0.8
http://search.cpan.org/~casiano/Gift-0.8/
Parser for Moodle Gift format
----
Gtk2-Net-LDAP-Widgets-2.0.1
http://search.cpan.org/~adamowski/Gtk2-Net-LDAP-Widgets-2.0.1/
LDAP-related widget library for Gtk2
----
JS-YUI-Loader-0.05
http://search.cpan.org/~rkrimen/JS-YUI-Loader-0.05/
Load (and cache) the Yahoo JavaScript YUI framework
----
JS-jQuery-Loader-0.01
http://search.cpan.org/~rkrimen/JS-jQuery-Loader-0.01/
Load (and cache) the jQuery JavaScript library
----
MSDOS-Attrib-1.04
http://search.cpan.org/~cjm/MSDOS-Attrib-1.04/
Get or set MS-DOS file attributes
----
Mac-Apps-Seasonality-Constants-v1.0.2
http://search.cpan.org/~elliotjs/Mac-Apps-Seasonality-Constants-v1.0.2/
Static definitions of aspects of Seasonality.
----
MasonX-Interp-WithCallbacks-1.18
http://search.cpan.org/~dwheeler/MasonX-Interp-WithCallbacks-1.18/
Mason callback support via Params::CallbackRequest.
----
MojoMojo-0.999015
http://search.cpan.org/~mramberg/MojoMojo-0.999015/
A Catalyst & DBIx::Class powered Wiki.
----
Net-CouchDb-0.02
http://search.cpan.org/~dgl/Net-CouchDb-0.02/
Interface to CouchDb
----
POE-Component-Cron-0.019
http://search.cpan.org/~cfedde/POE-Component-Cron-0.019/
Schedule POE Events using a cron spec
----
Params-CallbackRequest-1.18
http://search.cpan.org/~dwheeler/Params-CallbackRequest-1.18/
Functional and object-oriented callback architecture
----
Params-Validate-0.91
http://search.cpan.org/~drolsky/Params-Validate-0.91/
Validate method/function parameters
----
Parse-Marpa-0.211_003
http://search.cpan.org/~jkegl/Parse-Marpa-0.211_003/
Earley's algorithm with LR(0) precomputation
----
Perl-Critic-Swift-v1.0.3
http://search.cpan.org/~elliotjs/Perl-Critic-Swift-v1.0.3/
A set of additional policies for Perl::Critic.
----
Pg-Pcurse-0.07
http://search.cpan.org/~ioannis/Pg-Pcurse-0.07/
Monitors a Postgres cluster
----
RDF-Simple-Serialiser-Notation3-1.005
http://search.cpan.org/~mthurn/RDF-Simple-Serialiser-Notation3-1.005/
Output RDF triples in Notation3 format
----
RDF-Simple-Serialiser-Notation3-1.006
http://search.cpan.org/~mthurn/RDF-Simple-Serialiser-Notation3-1.006/
Output RDF triples in Notation3 format
----
SVN-Notify-2.73
http://search.cpan.org/~dwheeler/SVN-Notify-2.73/
Subversion activity notification
----
Test-Smoke-1.32
http://search.cpan.org/~abeltje/Test-Smoke-1.32/
The Perl core test smoke suite
----
Text-Diff-HTML-0.05
http://search.cpan.org/~dwheeler/Text-Diff-HTML-0.05/
XHTML format for Text::Diff::Unified
----
Text-Summary-MediaWiki-0.01
http://search.cpan.org/~dgl/Text-Summary-MediaWiki-0.01/
Produce a short summary from MediaWiki markup
----
Tk-TextVi-0.01
http://search.cpan.org/~jstrom/Tk-TextVi-0.01/
Tk::Text widget with Vi-like commands
----
Weather-Google-0.02
http://search.cpan.org/~possum/Weather-Google-0.02/
Perl interface to Google's Weather API
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Sat, 3 May 2008 20:33:40 -0700
From: "Gordon Etly" <get@bentsys.com>
Subject: Re: Read 20 lines when pressing n for next
Message-Id: <684p4mF2ruqugU1@mid.individual.net>
Uri Guttman wrote:
> Gordon Etly <get@bentsys.com> writes:
...
> > Uri Guttman wrote:
> > So what? Point me ot a rule that says every question has to be a
> > "technical" one or sod off. Anyone can comment on someone else post,
> > which you invite by posting in the first place. If you can't handle
> > it, don't post.
>
> hmm. see the guidelines. this group is about discussing perl, not the
> posters.
Seems you need to swallow your own advice, as you are the one who keeps
trying ot makes things personal.
> > By posting you invite comments, if you can't handle it, then don't
> > post. And would you care to tell me how making a point about
> > something found in the documentation of Perl to be off topic in a
> > Perl news group?
>
> because the answer is already there (and shown many times) and flaming
> about it ad nauseum does no one but you any good.
I haven't flamed anyone. I made comments. You came after me, like you
are here, rather than address the points.
> huh?? wrapping issues? you must use some strange usenet reader. emacs
> has no problems here. nor do i. try another useless offtopic.
Like I said, the only time, whine I smack "reply", that I see the
wrapping (after 3 levels of quoting) to be quite off. Most anyone else I
reply to doesn't yield such a result. What are your max character cut
offs set to for quoting? Mine is set to 72. It seem, after going over
your lines you are set to 74. Over the years I've most commonly seen 72
(and sometimes 76) as the recommended cut off. Especially in technical
groups.
Albeit the fact that 72 and 76 cause no problems for about a dozen quote
levels and 74 becomes a mess after 3 levels may be a deficiency in the
quoting mechanism in my reader. I suspect this is because of the leading
white space in the lines you quote. This would appear to be an uncommon
practice and apparently some readers don't deal with that too well. If
you could, please don't include leading white space in quoted lines.
> > > i have nothing to prove to you. you have tons to prove here.
>
> > As I have nothing to prove to you, yet you insist on coming after me
> > as if I and others do.
>
> you do have something to prove
Sorry, but no I do not. No one does. Not in order to post a comment.
I've been programming, administrating (UNIX, Linux, Solaris, Windows,
etc), and such for a long time, I've dealt with your type countless
times - the supposed veteran of a forum or news group who thinks they
can push people around for what ever reason because they believe they
have earned the right to do so. Sorry, but I don't care if you've been
around for just 20 minutes or 20 years, unacceptable behavior and same
rules should apply to everyone, not just what you might consider to be a
lower cast denizen.
> such as actual skill in helping others
I'll tell you what, learn to use your shift key properly, and I'll shift
around some time to help people out in this group. I don't really have a
problem taking time off from one forum, that I regularly help in, to
contribute help to another, but as I already told you before, it's
ludicrous to expect one to be a regular helper in every single group
they go to all the time, as there are only so many hours in the day and
for many who also work there are only so many out of the remaining hours
one can spend on forums, news groups, and mailing lists, so that does
necessitate being selective.
--
G.Etly
------------------------------
Date: Sun, 4 May 2008 03:27:52 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Stuffing @users into $self->{'users'}
Message-Id: <8ijve5-hqa.ln1@osiris.mauzo.dyndns.org>
Quoth xhoster@gmail.com:
> Ben Morrow <ben@morrow.me.uk> wrote:
> > Quoth "Peter J. Holzer" <hjp-usenet2@hjp.at>:
> > > On 2008-05-01 14:44, A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
> > > >
> > > > If $x is a reference to an array, then @{ $x } dereferences it.
> > > >
> > > > my @users = @{ $self->{users} };
> > >
> > > Yup. That's one of the two rules to remember. The other is to use -> to
> > > access individual members.
> >
> > I'm currently considering writing a module that would allow the syntax
> >
> > my @users = $self->{users}[];
> >
> > instead[1]. Given that it will be rather tricky, would people actually
> > find such a thing useful, or would the 'effort' of loading a module be
> > enough to put people off using it?
>
> The module would have to be based on something like Filter::Util::Call,
> right? I've heard bad things about the stability of that, which would put
> me off using such a module on a regular basis.
Source filters that try to heuristically parse Perl, or something like
it, (Switch being the canonical example) are typically unreliable, since
it's essentially impossible to parse Perl except by running it through
perl and looking at the resulting optree. Even PPI (a newish Perl module
that almost-perfectly parses Perl) isn't good enough, as there are cases
that simply cannot be parsed correctly without actually running the
code.
There are two ways I can see to avoid this. Devel::Declare gets around
the issue by (extremely hackishly) inserting hooks into the real parser,
which can then parse a short section of new syntax and return control.
While this has the advantage of using the real parser to parse
everything that isn't the new syntax, I'm not sure it can be done in
this case: I suspect the 'Syntax error' case fires too soon.
The alternative would be to ship my modified versions of toke.c and
perly.y (and derived files) with the module. This way I can compile
copies of yylex() and yyparse() that are actually correct, and still
call the functions in op.c to build the optree. Then I should be able to
install this parser as a source filter (in this case, one that simply
builds an optree and doesn't return any text to the 'real' parser, much
like ByteLoader) while avoiding the heuristics that usually make them so
unreliable.
> Other than that, I'd like it very much.
OK, cool. As you can see, it's quite a bit of work, so I'm not making
any promises :).
Ben
--
Raise your hand if you're invulnerable.
[ben@morrow.me.uk]
------------------------------
Date: Sun, 4 May 2008 10:24:40 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Stuffing @users into $self->{'users'}
Message-Id: <slrng1qsme.4np.hjp-usenet2@hrunkner.hjp.at>
On 2008-05-03 23:19, Ben Morrow <ben@morrow.me.uk> wrote:
>
> Quoth "Peter J. Holzer" <hjp-usenet2@hjp.at>:
>> On 2008-05-01 14:44, A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
>> >
>> > If $x is a reference to an array, then @{ $x } dereferences it.
>> >
>> > my @users = @{ $self->{users} };
>>
>> Yup. That's one of the two rules to remember. The other is to use -> to
>> access individual members.
>
> I'm currently considering writing a module that would allow the syntax
>
> my @users = $self->{users}[];
>
> instead[1].
Nice. Is there a way to extend this to array slices?
my @users = $self->{users}[1, 3 .. 5]
But I guess that collides with existing valid syntax.
> Given that it will be rather tricky, would people actually
> find such a thing useful, or would the 'effort' of loading a module be
> enough to put people off using it?
>
> Ben
>
> [1] I originally did it as a patch for core perl, which was considerably
> easier; the consensus on p5p was that such minor and not-obviously-
> terribly-useful syntax changes should be tested on CPAN first, if at all
> possible.
I would find that very useful. The effort of loading a module wouldn't
put me off, instabilities introduces by a source-filter might, though.
hp
------------------------------
Date: Sun, 04 May 2008 08:47:13 +0000
From: Peter Makholm <peter@makholm.net>
Subject: Re: Stuffing @users into $self->{'users'}
Message-Id: <87r6cih2we.fsf@hacking.dk>
Philluminati <Phillip.Ross.Taylor@gmail.com> writes:
> Oh wow it works perfectly.
>
> Thank you Peter I really appreciate the time you've taken to answer my
> post. :-)
Note that it took less than an hour from you posted the right pieces
of code till you got an working answer. Before you posted the code
where you actually uses you package to get the error nobody would be
able to help without making som wild assumptions about what you were
doing.
Posting a complete minimal example showing you problem would have
helped you from the first post.
//Makholm
------------------------------
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 V11 Issue 1508
***************************************
