[29727] in Perl-Users-Digest
Perl-Users Digest, Issue: 971 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 24 18:09:41 2007
Date: Wed, 24 Oct 2007 15:09:05 -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 Wed, 24 Oct 2007 Volume: 11 Number: 971
Today's topics:
ANNOUNCE: Text::CSV_XS 0.32 <h.m.brand@xs4all.nl>
Re: configurable variables in own file? <bik.mido@tiscalinet.it>
Re: configurable variables in own file? <ben@morrow.me.uk>
Crypt::TripleDES and public/private keys <SteveSpamTrap@yahoo.com>
Re: Crypt::TripleDES and public/private keys <1usa@llenroc.ude.invalid>
Re: Crypt::TripleDES and public/private keys <SteveSpamTrap@yahoo.com>
Re: Crypt::TripleDES and public/private keys <m@rtij.nl.invlalid>
Re: Crypt::TripleDES and public/private keys <jgibson@mail.arc.nasa.gov>
From "The Camel Book", Ch. 16 (IPC) <rihad@mail.ru>
Re: Implementation of file input operator <> <uri@stemsystems.com>
Re: Implementation of file input operator <> <ben@morrow.me.uk>
Perl based eCommerce site <charlie.h.turner@googlemail.com>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <bik.mido@tiscalinet.it>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <blb8@po.cwru.edu>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <bik.mido@tiscalinet.it>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <cwilbur@chromatico.net>
Re: TeX pestilence (was Distributed RVS, Darcs, tech lo <jurgenex@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 24 Oct 2007 11:45:52 GMT
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Subject: ANNOUNCE: Text::CSV_XS 0.32
Message-Id: <JqF7L5.K11@zorch.sf-bay.org>
The following report has been written by the PAUSE namespace indexer.
Please contact modules@perl.org if there are any open questions.
Id: mldistwatch 925 2007-09-16 15:41:11Z k
User: HMBRAND (H.Merijn Brand)
Distribution file: Text-CSV_XS-0.32.tgz
Number of files: 28
*.pm files: 1
README: Text-CSV_XS-0.32/README
META.yml: Text-CSV_XS-0.32/META.yml
Timestamp of file: Wed Oct 24 11:26:57 2007 UTC
Time of this run: Wed Oct 24 11:28:25 2007 UTC
2007-10-24 0.32 - H.Merijn Brand <h.m.brand@xs4all.nl>
* Added $csv->error_diag () to SYNOPSIS
* Added need for diag when new () fails to TODO
* Fixed a sneaked-in defined or in examples/csv2xls
* Plugged a 32byte memory leak in the cache code (valgrind++)
* Some perlcritic level1 changes
2007-07-23 0.31 - H.Merijn Brand <h.m.brand@xs4all.nl>
* Removed prototypes in examples/csv2xls
* Improved usage for examples/csv2xls (GetOpt::Long now does
--help/-?)
* Extended examples/csv2xls to deal with Unicode (-u)
* Serious bug in Text::CSV_XS::NV () type setting, causing the
resulting field to be truncated to IV
2007-06-21 0.30 - H.Merijn Brand <h.m.brand@xs4all.nl>
* ,\rx, is definitely an error without binary (used to HANG!)
* Fixed bug in attribute caching for undefined eol
* Cleaned up some code after -W*** warnings
* Added verbatim.
* More test to cover the really dark corners and edge cases
* Even more typo fixes in the docs
* Added error_diag ()
* Added t/80_diag.t - Will not be mirrored by Text::CSV_PP
* Added DIAGNOSTICS section to pod - Will grow
* Small pod niot (abeltje)
* Doc fix in TODO (Miller Hall)
------------------------------
Date: Wed, 24 Oct 2007 13:19:54 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: configurable variables in own file?
Message-Id: <udauh3hlrvtf9lbvm74l5h7iuigbfk8h0r@4ax.com>
On Wed, 24 Oct 2007 03:29:32 -0000, ivowel@gmail.com wrote:
>optimally, I would like syntax like
>
>package mypackage:
Just don't use all lowercase, since these
>require Exporter;
>our @ISA= qw(Exporter);
>our @EXPORT = qw( v1 v2 v3 v4 );
>include mypackageconfig;
>our ($v2, $v3, $v4) = ("a", "b", "c");
>($v1=~ /whatisit/);
>## a lot more stuff, a lot more variables, etc.
>
>and the file mypackageconfig would just contain
>
>our $v1= "user-please-set";
>
>is there a standard way to do this? I have been trying to accomplish
>this, but always run into import/export problems.
I can't see what problem could you possibly incur with require(), or
even do(). I don't see that you really need to import or export
anything, but which problems anyway?
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Wed, 24 Oct 2007 21:42:48 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: configurable variables in own file?
Message-Id: <8bn4v4-nb1.ln1@osiris.mauzo.dyndns.org>
Quoth ivowel@gmail.com:
>
> Dear perl experts: I want to create a rather lightweight package that
> just uses what is installed in standard perl. this problem must be
> very common.
>
> package mypackage:
> require Exporter;
> our @ISA= qw(Exporter);
> our @EXPORT = qw( v1 v2 v3 v4 );
> our ($v1, $v2, $v3, $v4) = ("user-please-set", "a", "b", "c");
> ($v1=~ /whatisit/);
> ## a lot more stuff, a lot more variables, etc.
>
> so far so good. alas, I now realize that $v1 is something that I
> would like my package users to change. instead of leaving it in
> mypackage, I think it would be nice to have such variables layed out
> into mypackageconfig.pm . mypackage should just load in
> mypackageconfig.pm at compile time, and treat everything in it as its
> own---like the C preprocessor #include.
>
> optimally, I would like syntax like
>
> package mypackage:
This line has a syntax error. Please copy-and-paste the *actual* code
you have run.
Also, don't use all-lowercase package names. These are reserved for
pragmas. It's probably better not to use top-level namespaces (those
without :: in) either, as the chance of conflict with some other
installed module is high. Choose some sensible top-level package for
your app, and keep everything under that. I tend to use BMORROW::* for
'private' modules I don't intend to distribute, where BMORROW is my CPAN
id.
> require Exporter;
> our @ISA= qw(Exporter);
> our @EXPORT = qw( v1 v2 v3 v4 );
> include mypackageconfig;
> our ($v2, $v3, $v4) = ("a", "b", "c");
> ($v1=~ /whatisit/);
> ## a lot more stuff, a lot more variables, etc.
>
> and the file mypackageconfig would just contain
>
> our $v1= "user-please-set";
>
> is there a standard way to do this? I have been trying to accomplish
> this, but always run into import/export problems.
If you want to use a separate package, you can use something like
package MyPackage::Config;
require Exporter;
our @ISA = qw(Exporter);
our @EXPORT = qw($v1 $v2 $v3);
our $v1 = 'foo';
our $v2 = 'bar';
our $v3 = 'baz';
__END__
package MyPackage;
use MyPackage::Config;
# now $v1 etc. have been imported into MyPackage
__END__
If you don't like all the mess at the top of MyPackage/Config.pm, you
could simply put the variables in it and load it with 'do' instead. In
that case you should not name it '.pm', as it is no longer a Perl
module.
A better (cleaner, safer) solution would be to use a proper data format.
You can use something like YAML::Tiny or Config::Tiny, and if you
*really* want to avoid any external dependencies, both those modules are
pure-Perl (they don't require a compiler to install) and have no
dependencies themselves, so you can include them directly in your own
file, like this:
package MyPackage;
use warnings;
use strict;
BEGIN {
# This persuades perl that we've actually loaded Config::Tiny
$INC{'Config/Tiny.pm'} = $0;
# copy and paste here Config/Tiny.pm, from
package Config::Tiny;
# up to
__END__
}
BEGIN { Config::Tiny->import }
Ben
------------------------------
Date: Wed, 24 Oct 2007 10:51:23 -0400
From: Steve <SteveSpamTrap@yahoo.com>
Subject: Crypt::TripleDES and public/private keys
Message-Id: <5o94fcFlovu5U1@mid.individual.net>
I've been asked to look into TripleDES encryption for a project, and
have what may sound like a silly newbie question. Is TripleDES based on
a public-key / private-key kind of setup, such as PGP? I notice that
the documentation for Perl's "Crypt::TripleDES" module only involves
three input parameters... the plaintext to be encrypted, or the
cyphertext to be decrypted, and a passphrase. There is no reference
whatsoever to telling the module about a public or private key.
Is this really all there is to it, and communicating with another party
via TripleDES means that you have to exchange and store the common
passphrase in some other secure means?
------------------------------
Date: Wed, 24 Oct 2007 15:05:54 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Crypt::TripleDES and public/private keys
Message-Id: <Xns99D370E6DCC04asu1cornelledu@127.0.0.1>
Steve <SteveSpamTrap@yahoo.com> wrote in news:5o94fcFlovu5U1
@mid.individual.net:
> I've been asked to look into TripleDES encryption for a project, and
> have what may sound like a silly newbie question. Is TripleDES based on
> a public-key / private-key kind of setup, such as PGP?
http://en.wikipedia.org/wiki/Triple_DES
http://www.rsa.com/rsalabs/node.asp?id=2231
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
clpmisc guidelines: <URL:http://www.augustmail.com/~tadmc/clpmisc.shtml>
------------------------------
Date: Wed, 24 Oct 2007 14:39:27 -0400
From: Steve <SteveSpamTrap@yahoo.com>
Subject: Re: Crypt::TripleDES and public/private keys
Message-Id: <5o9hr0Fls1v7U1@mid.individual.net>
> http://en.wikipedia.org/wiki/Triple_DES
>
> http://www.rsa.com/rsalabs/node.asp?id=2231
Well, obviously I started my search with Google and Wikipedia, and
didn't find a direct answer to the question I asked. I understand that
Triple-DES involves a "key"... but is this simply referring to the
passphrase (used as a salt value), or is there a true public-key /
private-key exchange involved? If so, how does that factor in with
Perl's "Crypt::TripleDES" module... which only takes in as input the
string to encrypt/decrypt and a passphrase?
------------------------------
Date: Wed, 24 Oct 2007 21:04:57 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Crypt::TripleDES and public/private keys
Message-Id: <pan.2007.10.24.19.04.57@rtij.nl.invlalid>
On Wed, 24 Oct 2007 14:39:27 -0400, Steve wrote:
>> http://en.wikipedia.org/wiki/Triple_DES
>>
>> http://www.rsa.com/rsalabs/node.asp?id=2231
>
>
> Well, obviously I started my search with Google and Wikipedia, and
> didn't find a direct answer to the question I asked. I understand that
Two mouse clicks took me to http://en.wikipedia.org/wiki/
Symmetric_key_algorithm. But then, I knew what I was looking for.
HTH,
M4
------------------------------
Date: Wed, 24 Oct 2007 13:20:28 -0700
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: Crypt::TripleDES and public/private keys
Message-Id: <241020071320283719%jgibson@mail.arc.nasa.gov>
In article <5o9hr0Fls1v7U1@mid.individual.net>, Steve
<SteveSpamTrap@yahoo.com> wrote:
> > http://en.wikipedia.org/wiki/Triple_DES
> >
> > http://www.rsa.com/rsalabs/node.asp?id=2231
>
>
> Well, obviously I started my search with Google and Wikipedia, and
> didn't find a direct answer to the question I asked. I understand that
> Triple-DES involves a "key"... but is this simply referring to the
> passphrase (used as a salt value), or is there a true public-key /
> private-key exchange involved? If so, how does that factor in with
> Perl's "Crypt::TripleDES" module... which only takes in as input the
> string to encrypt/decrypt and a passphrase?
DES has a single, private key, TripleDES can have 3 keys, or just use
the same key for the three encryption steps. The same key used for
encryption is used for decryption, therefore the key must be kept
private.
In most public-private encryption schemes, a symmetric,
private-key-only method is used to actually encrypt and decrypt the
message, because the symmetric methods are usually much faster than the
public/private methods. What is done is to encrypt the symmetric key(s)
using the slower public-private algorithm. The receiver uses the public
key to decrypt the symmetric key, and uses that key to decrypt the
message using the fast symmetric method.
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Wed, 24 Oct 2007 07:28:28 -0700
From: rihad <rihad@mail.ru>
Subject: From "The Camel Book", Ch. 16 (IPC)
Message-Id: <1193236108.967393.126460@v23g2000prn.googlegroups.com>
Chapter 16 "Interprocess Communication" of "Programming Perl" has this
part:
use Fcntl ':flock';
eval {
local $SIG{ALRM} = sub { die "alarm clock restart" };
alarm 10; # schedule alarm in 10 seconds
eval {
flock(FH, LOCK_EX) # a blocking, exclusive lock
or die "can't flock: $!";
};
alarm 0; # cancel the alarm
};
alarm 0; # race condition protection
die if $@ && $@ !~ /alarm clock restart/; # reraise
If the alarm hits while you're waiting for the lock, and you simply
catch the signal and return, you'll go right back into the flock
because Perl automatically restarts syscalls where it can. The only
way out is to raise an exception through die and then let eval catch
it. (This works because the exception winds up calling the C library's
longjmp(3) function, which is what really gets you out of the
restarting syscall.)
End quote. I've been banging my head against he wall because I do not
understand what the second alarm 0 is for, and given Mr. Wall's
special way of telling you the truth, the commentary doesn't help much
either ;-) Neither "perldoc -f alarm" or "perldoc perlipc" were of any
help (they didn't even call the second "alarm 0" in a similar
example). Where's the catch?
Thank you.
------------------------------
Date: Wed, 24 Oct 2007 15:02:26 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Implementation of file input operator <>
Message-Id: <x7hckg369q.fsf@mail.sysarch.com>
>>>>> "hg" == himanshu garg <himanshu.garg@gmail.com> writes:
hg> Could you tell me which file in the perl source distro I should
hg> look at for the implementation of the file input operators <>.
hg> I suspect that one 'call' of <> is leading to two read system
hg> calls.
do you think that is a bug? or why would 2 read calls bother you? it is
entirely possible for one readline call (what <> really is) could make
many read calls if the next input record (i didn't say line) overlaps
i/o buffer boundaries. perl's i/o subsystem (or stdio if you are using
that) manages read calls so it can satisfy your <> call. you want it to
make multiple read calls as needed.
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: Wed, 24 Oct 2007 21:58:14 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Implementation of file input operator <>
Message-Id: <68o4v4-nb1.ln1@osiris.mauzo.dyndns.org>
Quoth himanshu.garg@gmail.com:
>
> Could you tell me which file in the perl source distro I should
> look at for the implementation of the file input operators <>.
<> is implemented as pp_readline in pp_hot.c, which calls
pp_hot.c:Perl_do_readline, which calls sv.c:Perl_sv_gets, which calls
PerlIO_read to perform the actual read. Note that understanding the Perl
IO system is not easy.
> I suspect that one 'call' of <> is leading to two read system
> calls.
As Uri pointed out, this is expected and desired. If you want to do your
own buffering, push a :unix layer or use sysread.
Ben
------------------------------
Date: Wed, 24 Oct 2007 10:59:51 -0700
From: Charles Turner <charlie.h.turner@googlemail.com>
Subject: Perl based eCommerce site
Message-Id: <1193248791.614179.91950@q3g2000prf.googlegroups.com>
I am wondering if anyone knows of a project like OsCommerce (It's an
eCommerce website template by the way), but built using perl? I have a
project I'd like to do in perl, I'm still a beginner, therefore,
building the application myself is a far call for the moment. I just
need some working examples at a bare minimum.
Thank you for your time.
Charles.
------------------------------
Date: Wed, 24 Oct 2007 17:01:01 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <bsmuh395c84agrgk0g8juiflq4g72r6s8a@4ax.com>
On Mon, 22 Oct 2007 09:07:37 -0400, Lew <lew@lewscanon.com> wrote:
>Xah Lee wrote:
>> i have written ... No coherent argument,
I've long killfiled XL to the effect that all of his threads are
ignored altogether, since the guy is "nice" enough to only take part
to his own rants, but occasionally some posts slip out and now from
the Subject I infer that the new target for his hate is TeX, which
makes me wonder, given his views on Perl (and "unixisms in general"
iirc) what our "friend" would think about such a wonderful tool as
PerlTeX - from his POV certainly a synergy between two of the worst
devil's devices. :)
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Wed, 24 Oct 2007 18:21:35 +0000 (UTC)
From: Brian Blackmore <blb8@po.cwru.edu>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <ffo2fe$seq$2@gnus01.u.washington.edu>
In comp.text.tex Michele Dondi <bik.mido@tiscalinet.it> wrote:
> On Mon, 22 Oct 2007 09:07:37 -0400, Lew <lew@lewscanon.com> wrote:
> >Xah Lee wrote:
> >> i have written ... No coherent argument,
> I've long killfiled XL to the effect that all of his threads are
> ignored altogether, since the guy is "nice" enough to only take part
> to his own rants, but occasionally some posts slip out and now from
> the Subject I infer that the new target for his hate is TeX, which
> makes me wonder, given his views on Perl (and "unixisms in general"
> iirc) what our "friend" would think about such a wonderful tool as
> PerlTeX - from his POV certainly a synergy between two of the worst
> devil's devices. :)
I find it very sad and, perhaps, very telling, that XL attacks TeX on
all the non-TeX newsgroups. This is, perhaps, strange? I did some
searching around just to find the original thread and it seems to be
hiding on the python group; this might explain all of his cross-posting,
but it doesn't explain how someone so confused about a simple language
like TeX can't even figure out how to post to the appropriate group.
I would be happy to disagree with him on several points, in particular
as regards to the programming language TeX. As I quickly glance at his
original rant on his web page, I see many other things that seem to be
misunderstood. Perhaps if I were to look at his background and
qualifications, some of it would become clear.
In any case, since this is the TeX channel, I will mention that I think
TeX is an excellent programming language and, given the state of affairs
in computer science departments these days, I think every f...ing CS
grad should have to do a semester of TeX _programming_. (Hey, XL uses
so many words that are completely meaningless and oft regarded as foul,
so I figured I'd better use one.) I see too many CS grads these days
that can't do anything unless there's already a java module to do it,
and then they get confused about using the module according to the
documentation. Most of these people would garner nothing but benefit
from having to spend time _thinking_, and that is one thing that TeX
programming requires.
In many cases, helping people with TeX is just making them realize how
to think about the problem in the correct way (for the system at hand).
The ability to `change gears' in this fashion is a general aspect of
problem solving that they seem, in general, to lack.
--
Brian Blackmore
blb8 at po dot cwru dot edu
------------------------------
Date: Wed, 24 Oct 2007 21:17:29 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <ug6vh39748gk83an8gjfn2bk7s484prmcs@4ax.com>
On Wed, 24 Oct 2007 18:21:35 +0000 (UTC), Brian Blackmore
<blb8@po.cwru.edu> wrote:
>I would be happy to disagree with him on several points, in particular
>as regards to the programming language TeX. As I quickly glance at his
Don't! It's a (well known) troll, there's no point in feeding a troll.
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 24 Oct 2007 16:09:20 -0400
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <871wbkb7gv.fsf@mithril.chromatico.net>
>>>>> "BB" == Brian Blackmore <blb8@po.cwru.edu> writes:
BB> I find it very sad and, perhaps, very telling, that XL attacks
BB> TeX on all the non-TeX newsgroups. This is, perhaps, strange?
It's strange by the standards of reasonable Usenettery, insofar as
such a thing exists, but Xah is well known for this kind of nonsense.
For a while he was attempting to promote inter-newsgroup communication
by posting a sample of his Perl and an improved version in Python to
comp.lang.python and comp.lang.perl.misc; it fizzled when, instead of
the Perlers and Pythonistas flaming each other, they joined together
to criticize his code.
I wouldn't waste any more energy on Xah, unless it were expended
adding him to your killfile.
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: Wed, 24 Oct 2007 20:15:56 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: TeX pestilence (was Distributed RVS, Darcs, tech love)
Message-Id: <0KNTi.2621$qo2.1247@trndny06>
Lew wrote:
> Xah Lee wrote:
>> i have written ... No coherent argument,
Actually the modified title is wrong. It should be
The Xah Lee pestilence
Please see his posting history of off-topic random rambling for details.
Oh, and PLEASE
+-------------------+ .:\:\:/:/:.
| PLEASE DO NOT | :.:\:\:/:/:.:
| FEED THE TROLLS | :=.' - - '.=:
| | '=(\ 9 9 /)='
| Thank you, | ( (_) )
| Management | /`-vvv-'\
+-------------------+ / \
| | @@@ / /|,,,,,|\ \
| | @@@ /_// /^\ \\_\
@x@@x@ | | |/ WW( ( ) )WW
\||||/ | | \| __\,,\ /,,/__
\||/ | | | jgs (______Y______)
/\/\/\/\/\/\/\/\//\/\\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
==============================================================
jue
------------------------------
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 971
**************************************
