[29779] in Perl-Users-Digest
Perl-Users Digest, Issue: 1022 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Nov 10 18:10:13 2007
Date: Sat, 10 Nov 2007 15:09:06 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sat, 10 Nov 2007 Volume: 11 Number: 1022
Today's topics:
calculate the number of days between two dates <lucavilla@cashette.com>
Re: calculate the number of days between two dates <jurgenex@hotmail.com>
Re: File handling and regex <tadmc@seesig.invalid>
Re: File handling and regex <lucavilla@cashette.com>
Re: Platypus - Current Working Directory - write files <hjp-usenet2@hjp.at>
Re: Why can't you slice an array @a[3..-1]? <tzz@lifelogs.com>
Re: Why can't you slice an array @a[3..-1]? <tzz@lifelogs.com>
Re: Why can't you slice an array @a[3..-1]? <tzz@lifelogs.com>
Re: Why can't you slice an array @a[3..-1]? <tzz@lifelogs.com>
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <1usa@llenroc.ude.invalid>
Re: Why can't you slice an array @a[3..-1]? <jurgenex@hotmail.com>
Re: Why can't you slice an array @a[3..-1]? xhoster@gmail.com
Re: Why can't you slice an array @a[3..-1]? <bik.mido@tiscalinet.it>
Re: Why can't you slice an array @a[3..-1]? <m@rtij.nl.invlalid>
Re: Why can't you slice an array @a[3..-1]? <abigail@abigail.be>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 10 Nov 2007 14:47:17 -0800
From: Luca Villa <lucavilla@cashette.com>
Subject: calculate the number of days between two dates
Message-Id: <1194734837.517810.150430@d55g2000hsg.googlegroups.com>
Given two dates like the following
Feb-14-07 18:20:11
Mar-03-07 20:32:19
how can I calculate the number of days (with decimals!) between the
first an
d the second?
Are there any ready solution on the web?
------------------------------
Date: Sat, 10 Nov 2007 22:52:51 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: calculate the number of days between two dates
Message-Id: <7DqZi.3011$cD.2806@trndny08>
Luca Villa wrote:
> how can I calculate the number of days (with decimals!) between the
> first and the second?
> Are there any ready solution on the web?
Your Question is Asked Frequently, please see "perldoc -q date":
How can I compare two dates and find the difference?
jue
------------------------------
Date: Sat, 10 Nov 2007 07:27:36 -0600
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: File handling and regex
Message-Id: <slrnfjbce8.qcb.tadmc@tadmc30.sbcglobal.net>
Luca Villa <lucavilla@cashette.com> wrote:
>> If you are going to mess with the special variables anyway,
>> then you could replace all of that with:
>>
>> local @ARGV = $_;
>> local $/;
>> my $data = <>;
>
> I received this error:
> "Can't do inplace edit: . is not a regular file at c:\script.src line
> 12."
The error message has nothing to do with the code you quoted above.
> inplace edit? What does it want to do?
It wants to edit the file "inplace", that is, with the same name.
You have turned on inplace editing either with the -i command line
switch, or by setting the $^I variable somewhere...
Also, what it is trying to edit is not a file, it is a directory. You
may want to test what find() is operating on with the -d or -f filetest.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Sat, 10 Nov 2007 09:11:19 -0800
From: Luca Villa <lucavilla@cashette.com>
Subject: Re: File handling and regex
Message-Id: <1194714679.502937.31010@57g2000hsv.googlegroups.com>
Hi Tad,
I'm not using any argument a part of the "source.src" that contains
the script.
I started to get the error since I used your suggested substitutive
block.
This is the source.src exact content, that gives the mentioned error:
use File::Find;
find(\&found, 'c:/tempebay/1');
sub found {
local @ARGV = $_;
local $/;
my $data = <>;
my($type, $number);
if($data =~ /<td align="right" nowrap>\s+Item number:\s+(\d+)<\/
td>/) {
$number=$1;
$type="item_description_html";
}
elsif($data =~ /Item number:\s*<img src="http:\/\/pics
\.ebaystatic\.com\/aw\/pics\/s\.gif" width="\d+">(\d+)<\/div>/) {
$number=$1;
$type="buyers_history_html";
}
else {
warn "File $File::Find::name is of not interesting type,
for example an eBay page of item\n";
return;
}
my $outfn="c:/tempebay/2/$number-$type.htm";
if(-e $outfn) {
warn "File $outfn already exists.\n";
return;
}
unless(open(OUT,">$outfn")) {
warn "Could not open $outfn: $!\n";
return;
}
print OUT $data;
close(OUT);
}
___
I launch: perl script.src
and despite that initial error message it actually works!
Can you understand why does it want to do that inplace edit?
------------------------------
Date: Sat, 10 Nov 2007 23:24:06 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Platypus - Current Working Directory - write files
Message-Id: <slrnfjcbs6.qmo.hjp-usenet2@zeno.hjp.at>
On 2007-11-06 12:25, Markus S <youcontrol@hispeed.ch> wrote:
> On 2007-11-06 5:02, Larry said:
>> in Platypus window:
>>
>> Script Type: Shell
>> Script Path: your start.sh
>>
>> the followin is the start.sh file:
>>
>> #!/bin/sh
>> #
>> # start.sh
>>
>> cd $1/Contents/Resources/
>>
>> /usr/bin/perl $1/Contents/Resources/my_perl_script.pl
>
> Thanks. Unfortunately, the $1 contains a space in my case and the cd
> command therefore fails. I would know how to deal with this within Perl
> but not on the Shell level.
Put double quotes around $1.
Or do the chdir inside the perl script.
hp
--
_ | Peter J. Holzer | It took a genius to create [TeX],
|_|_) | Sysadmin WSR | and it takes a genius to maintain it.
| | | hjp@hjp.at | That's not engineering, that's art.
__/ | http://www.hjp.at/ | -- David Kastrup in comp.text.tex
------------------------------
Date: Sat, 10 Nov 2007 09:05:55 -0600
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <m2lk96nnsc.fsf@lifelogs.com>
On Sat, 10 Nov 2007 02:48:40 +0000 (UTC) Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
IZ> [A complimentary Cc of this posting was sent to
IZ> Ted Zlatanov
IZ> <tzz@lifelogs.com>], who wrote in article <m21wazow25.fsf@lifelogs.com>:
>> I think Perl, normally a clever language, is not clever on this.
>> Ask any child what 3..-1 should generate as a sequence, and they
>> won't say "empty list."
IZ> IMO, child's opinion should not have very high priority in design of
IZ> programming languages.
OK, ask anyone at all what "3 .. -1" should be, mathematician or not,
that's not a Perl programmer. The design of Perl 5 chose consistency
(.. always counts up and generates an empty list if it can't) over DWIM
(count from x to y, either up or down) here.
I don't think the DWIM mode is wrong, as evidenced by the percentage of
people that would tell you it's what they expect (informal poll on 5
people by me: 100%). It would break code, though, so I don't propose
that it be the default.
IZ> Hint: your proposal breaks the fundamental proportion:
IZ> 5..7 ==> 5 6 7
IZ> 5..6 ==> 5 6
IZ> 5..5 ==> 5
IZ> 5..4 ==> ???
You see .. as a forward vector on the integer number line. I think the
vector could point down as well:
5..4 ==> 5 4
5..1 ==> 5 4 3 2 1
1..-1 ==> 1 0 -1
Again, this is not my overactive imagination, it's what people expect.
>> If 3..-1 returned a downward range, it would be trivial to look at the
>> array slice offsets, check if the last number is negative, and do the
>> right thing for that case.
IZ> I see, you want YET ANOTHER "right thing". How nice of you... And
IZ> what @a[5,2] should return, in your opinion?
That's irrelevant. My point is:
1) in @array[x..y] make the .. operator count down IFF y is negative
("subscript context"). As an alternative, make it count down everywhere
with a pragma, or make it count down in subscript context with a pragma.
2) any negative subscripts refer to the last-minus-y offset (which is
already the case).
So the change is only to .. and entirely optional. Another operator,
some Unicode character, could be used instead of .. if you think it's a
better choice.
Ted
------------------------------
Date: Sat, 10 Nov 2007 09:09:19 -0600
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <m2hcjunnmo.fsf@lifelogs.com>
On Sat, 10 Nov 2007 12:08:43 +0100 Michele Dondi <bik.mido@tiscalinet.it> wrote:
MD> On Sat, 10 Nov 2007 10:19:19 +0100, Martijn Lievaart
MD> <m@rtij.nl.invlalid> wrote:
>> for (3 .. 1)
>> It would be very useful to have that count back, and it would be very
>> intuitive imo.
MD> No, it wouldn't, reverse() is what one wants.
No, it's what Perl 5 wants and the programmer has to satisfy it. People
want the intuitive range, up or down.
Ted
------------------------------
Date: Sat, 10 Nov 2007 09:16:28 -0600
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <m2d4uinnar.fsf@lifelogs.com>
On 10 Nov 2007 12:34:59 GMT Abigail <abigail@abigail.be> wrote:
A> I don't know which one is more useful. But that doesn't matter; it's
A> too late to change. Even if there's more benefit that 3 .. 1 'counts
A> backwards' than 3 .. 1 being an empty list, the disadvantage of
A> changing the meaning (and hence having lots of potential code that
A> breaks; it's not that .. is an uncommon operation) far outweights
A> any possible benefit.
That's why my proposal was with a pragma and only in subscript context
(although in global context it would work too).
A> Note however that having .. count backwards if the second argument
A> is smaller than the first, does NOT solve the slice issue.
A> @array = qw [one two three four five six];
A> @array [3 .. $#array]; # 'four', 'five', 'six'; indented value
A> # of @array [3 .. -1].
A> @array [3 .. -1] # 'four', 'three', 'two', 'one', 'six';
A> # value if .. counts backwards.
Ah, you're right, I wasn't thinking. So counting down is not the answer
(though it makes intuitive sense). .. in subscript context would have
to replace -x with the corresponding offset. The resulting mess is not
DWIM, so consider my arguments crap :)
Ted
------------------------------
Date: Sat, 10 Nov 2007 09:17:37 -0600
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <m28x56nn8u.fsf@lifelogs.com>
On Sat, 10 Nov 2007 12:17:37 +0100 Michele Dondi <bik.mido@tiscalinet.it> wrote:
MD> On Sat, 10 Nov 2007 10:24:23 +0100, "Dr.Ruud"
MD> <rvtol+news@isolution.nl> wrote:
>> Another DWIM-candidate:
>>
>> being able to write
>>
>> return \%data{@keys}
MD> Well, without even mentioning the referencing thing, first one useful
MD> dwimmery would be the ability to slice a hash like that.
MD> my %sliced=%data{@keys};
A "slice" operator? Maybe look for a Unicode "knife" symbol? :)
Ted
------------------------------
Date: Sat, 10 Nov 2007 17:15:11 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <2nkbj39r4trjj7mjngberdt6nefjbj3gi5@4ax.com>
On Sat, 10 Nov 2007 09:09:19 -0600, Ted Zlatanov <tzz@lifelogs.com>
wrote:
>On Sat, 10 Nov 2007 12:08:43 +0100 Michele Dondi <bik.mido@tiscalinet.it> wrote:
>
>MD> On Sat, 10 Nov 2007 10:19:19 +0100, Martijn Lievaart
>MD> <m@rtij.nl.invlalid> wrote:
>
>>> for (3 .. 1)
>>> It would be very useful to have that count back, and it would be very
>>> intuitive imo.
>
>MD> No, it wouldn't, reverse() is what one wants.
>
>No, it's what Perl 5 wants and the programmer has to satisfy it. People
>want the intuitive range, up or down.
No people who find the range intuitive that way want it that way. To
me and someone else it is counter-intuitive. I'm not a mathematician
nor do I have extraordinary mathematical skills, but mathematics is
*very* intuitive to me. That other use is confusing and inconsistent.
Perhaps because I have some more experience than you with
combinatorics where e.g. a sum from n to m where n>m is naturally
null. If it were to have "your" meaning, it would make calculations
terribly clumsy. Your "intuitive" idea is more that of a *segment*
than a range, but I don't see it as extremely useful unless there
where three different operators (or one operator with suitable
adverbs, but we don't have adverbs in Perl 5 yet) with the semanticts
of respectively "upto", "downto", "between".
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: Sat, 10 Nov 2007 17:16:34 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <4ambj3decp8hoe2bu642eiuh529h6isfnt@4ax.com>
On Sat, 10 Nov 2007 09:16:28 -0600, Ted Zlatanov <tzz@lifelogs.com>
wrote:
>Ah, you're right, I wasn't thinking. So counting down is not the answer
>(though it makes intuitive sense). .. in subscript context would have
>to replace -x with the corresponding offset. The resulting mess is not
>DWIM, so consider my arguments crap :)
say "Whoa, at least!"; # just kidding ;)
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: Sat, 10 Nov 2007 17:22:37 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <hembj3t8lrskcsim5uo5uh9eap0he5r4jd@4ax.com>
On Sat, 10 Nov 2007 09:17:37 -0600, Ted Zlatanov <tzz@lifelogs.com>
wrote:
>MD> my %sliced=%data{@keys};
>
>A "slice" operator? Maybe look for a Unicode "knife" symbol? :)
We're not ready yet for unicode operators. We have to wait for 6. And
call me old-fashioned, but I think I would often use the ascii
equivalent operators most of the times with it too. OTOH I don't see
that we need a special operator at all since the above syntax seems
fine, except that currently generates an error. Of course some p5p'er
may explain that in fact it's *not* fine, e.g. not compatible with...
well anything else.
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: Sat, 10 Nov 2007 17:04:02 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <Xns99E47ABDAE1ECasu1cornelledu@127.0.0.1>
Martijn Lievaart <m@rtij.nl.invlalid> wrote in
news:pan.2007.11.10.09.17.10@rtij.nl.invlalid:
> On Sat, 10 Nov 2007 02:48:40 +0000, Ilya Zakharevich wrote:
...
>> Hint: your proposal breaks the fundamental proportion:
>>
>> 5..7 ==> 5 6 7
>> 5..6 ==> 5 6
>> 5..5 ==> 5
>> 5..4 ==> ???
>>
>
> Yes, but how about
>
> for (3 .. 1) {
> ...
> }
>
> It would be very useful to have that count back, and it would be very
> intuitive imo.
Really? That would break a lot of my code: Right now, I know that if
$first > $last, the body of the loop:
for my $i ( $first .. $last ) {
will not run so I use that fact.
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: Sat, 10 Nov 2007 17:25:43 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <rQlZi.185$WM.134@trndny05>
Martijn Lievaart wrote:
> Yes, but how about
> for (3 .. 1) {...}
> It would be very useful to have that count back, and it would be very
> intuitive imo.
Absolutely not. I at least don't want to have to check explicitely every
single time
if ($start <= $end) {
for ($start .. $end) {...}
} # else do nothing
That would be so nuts
If you want to count down then just use
for (reverse (1..3)) {...}
jue
------------------------------
Date: 10 Nov 2007 17:39:31 GMT
From: xhoster@gmail.com
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <20071110123933.409$K2@newsreader.com>
Michele Dondi <bik.mido@tiscalinet.it> wrote:
> On Sat, 10 Nov 2007 10:19:19 +0100, Martijn Lievaart
> <m@rtij.nl.invlalid> wrote:
>
> >Yes, but how about
> >
> > for (3 .. 1) {
> > ...
> > }
> >
> >It would be very useful to have that count back, and it would be very
> >intuitive imo.
>
> No, it wouldn't, reverse() is what one wants. Admittedly, it is
> slightly long to write down.
It also materializes its list (currently). So
foreach (reverse 1..1e7) {
might not be such a good idea.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Sat, 10 Nov 2007 19:16:10 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <n8tbj35msqll9ikn0sccani79ddrgdh635@4ax.com>
On 10 Nov 2007 17:39:31 GMT, xhoster@gmail.com wrote:
>> No, it wouldn't, reverse() is what one wants. Admittedly, it is
>> slightly long to write down.
>
>It also materializes its list (currently). So
>foreach (reverse 1..1e7) {
>might not be such a good idea.
That's right. Of course we all want lazy list evaluation by default.
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: Sat, 10 Nov 2007 21:42:51 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <pan.2007.11.10.20.40.29@rtij.nl.invlalid>
On Sat, 10 Nov 2007 17:04:02 +0000, A. Sinan Unur wrote:
> Martijn Lievaart <m@rtij.nl.invlalid> wrote in
> news:pan.2007.11.10.09.17.10@rtij.nl.invlalid:
>
>> On Sat, 10 Nov 2007 02:48:40 +0000, Ilya Zakharevich wrote:
> ...
>
>>> Hint: your proposal breaks the fundamental proportion:
>>>
>>> 5..7 ==> 5 6 7
>>> 5..6 ==> 5 6
>>> 5..5 ==> 5
>>> 5..4 ==> ???
>>>
>>>
>> Yes, but how about
>>
>> for (3 .. 1) {
>> ...
>> }
>>
>> It would be very useful to have that count back, and it would be very
>> intuitive imo.
>
> Really? That would break a lot of my code: Right now, I know that if
> $first > $last, the body of the loop:
>
> for my $i ( $first .. $last ) {
>
> will not run so I use that fact.
I'm aware of that and I'm not proposing to change this, or anything other.
I was just commenting on what is intuitive for me and what would have
been useful imo. As changing this idiom breaks a lot of code, we cannot
change this.
Besides, your example is a good counterexample where I would expect the
loop not to run if $last<$first. As someone else wrote, to disambiguate
you would need three different operators, upto, downto and between. Well
downto can be done with reverse and upto, but as already shown, that
breaks lazy evaluation. Although it needn't with a sufficiently smart
reverse.
And there is also the fact that this has nothing to do with the original
problem of using negative integers to denote elements from the end.
All this is just academic, perl is perl and we can't change this. It's
just fun to think about it, sharpens the mind and sometimes something
very useful can come from these discussions.
M4
------------------------------
Date: 10 Nov 2007 21:44:57 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: Why can't you slice an array @a[3..-1]?
Message-Id: <slrnfjc9ip.ka.abigail@alexandra.abigail.be>
_
xhoster@gmail.com (xhoster@gmail.com) wrote on VCLXXXIV September
MCMXCIII in <URL:news:20071110123933.409$K2@newsreader.com>:
@@ Michele Dondi <bik.mido@tiscalinet.it> wrote:
@@ > On Sat, 10 Nov 2007 10:19:19 +0100, Martijn Lievaart
@@ > <m@rtij.nl.invlalid> wrote:
@@ >
@@ > >Yes, but how about
@@ > >
@@ > > for (3 .. 1) {
@@ > > ...
@@ > > }
@@ > >
@@ > >It would be very useful to have that count back, and it would be very
@@ > >intuitive imo.
@@ >
@@ > No, it wouldn't, reverse() is what one wants. Admittedly, it is
@@ > slightly long to write down.
@@
@@ It also materializes its list (currently). So
@@ foreach (reverse 1..1e7) {
@@ might not be such a good idea.
Nope. Which is why we have C-style loops:
for (my $i = 1e7; $i; $i --) { ... }
Abigail
--
perl -wle 'print "Prime" if (1 x shift) !~ /^1?$|^(11+?)\1+$/'
------------------------------
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 1022
***************************************
