[31587] in Perl-Users-Digest
Perl-Users Digest, Issue: 2846 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Mar 3 03:09:25 2010
Date: Wed, 3 Mar 2010 00:09:08 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 3 Mar 2010 Volume: 11 Number: 2846
Today's topics:
Automatic Web Form Submission <andygough1974@gmail.com>
Re: Can you compile a perl executable? <ralph.malph@altavista.com>
floating point issue? <kevin0051@gmail.com>
floating point issue? <kevin0051@gmail.com>
Re: floating point issue? <sreservoir@gmail.com>
Re: floating point issue? <sreservoir@gmail.com>
Re: floating point issue? <john@castleamber.com>
Re: floating point issue? <tadmc@seesig.invalid>
Re: floating point issue? <jurgenex@hotmail.com>
Re: floating point issue? <xhoster@gmail.com>
Re: flushing buffer for printing to the screen (Alan Curry)
Re: how to speed up a string-substitution loop? <adam.kellas@gmail.com>
Re: how to speed up a string-substitution loop? <uri@StemSystems.com>
Re: how to speed up a string-substitution loop? <jurgenex@hotmail.com>
Re: how to speed up a string-substitution loop? <adam.kellas@gmail.com>
Re: how to speed up a string-substitution loop? <adam.kellas@gmail.com>
Re: how to speed up a string-substitution loop? <adam.kellas@gmail.com>
Re: how to speed up a string-substitution loop? <uri@StemSystems.com>
Re: how to speed up a string-substitution loop? <derykus@gmail.com>
Re: strange behavior <ben@morrow.me.uk>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 2 Mar 2010 22:54:12 -0800 (PST)
From: andy <andygough1974@gmail.com>
Subject: Automatic Web Form Submission
Message-Id: <26d1a93a-b3ca-43dd-bc24-7a5388455c04@q23g2000yqd.googlegroups.com>
Hi Everyone,
I am looking for some advice on where to start research for a problem
I have which I would like to solve using perl.
I have to do many travel request searches for flights and would like
to automate it, I'd like to write a script to input to my favorite
travel sites things like:
Departure Point, Destination, Departure Date, Return Date. Submit the
form and parse the results.
I can parse the results with regular expressions no problem, but I am
not sure about entering the form info, submitting and retrieving the
results.
I read a little about WWW::Mechanize, is this the module you experts
would recommend me to use?
Can you recommend any other modules I should also research?
Many thanks in advance, your advice is always much appreciated.
Andy
------------------------------
Date: Tue, 02 Mar 2010 22:06:47 -0500
From: Ralph Malph <ralph.malph@altavista.com>
Subject: Re: Can you compile a perl executable?
Message-Id: <hmkjo7$hoj$1@speranza.aioe.org>
Steve wrote:
> If I made an application, and wanted to make it portable, is it
> possible to compile it into a single binary?
http://www.indigostar.com/perl2exe.php is the best tool
for the job I have used.
------------------------------
Date: Tue, 2 Mar 2010 17:54:03 -0800 (PST)
From: kevin0051 <kevin0051@gmail.com>
Subject: floating point issue?
Message-Id: <0f6e9c38-319d-49a6-8ae7-c53e4dcc6742@k5g2000pra.googlegroups.com>
I made a perl program as follows.
-----------------
$AAA = 4.31;
$AAA *= 100;
printf ("%f\n", $AAA);
printf ("%d\n", $AAA);
----------------
The output of this program is
431.000000
430
I don't know why the second output is 431 instead of 431.
Can anyone help?
Thanks
Kevin
------------------------------
Date: Tue, 2 Mar 2010 17:55:55 -0800 (PST)
From: kevin0051 <kevin0051@gmail.com>
Subject: floating point issue?
Message-Id: <f41dd5c2-4c50-499d-a613-062b5d1e8d9e@z1g2000prc.googlegroups.com>
I made a perl program as follows.
-----------------
$AAA = 4.31;
$AAA *= 100;
printf ("%f\n", $AAA);
printf ("%d\n", $AAA);
----------------
The output of this program is
431.000000
430
I don't know why the second output is 430 instead of 431.
Can anyone help?
Thanks
Kevin
------------------------------
Date: Tue, 02 Mar 2010 20:55:56 -0500
From: sreservoir <sreservoir@gmail.com>
Subject: Re: floating point issue?
Message-Id: <hmkfjj$bgs$1@speranza.aioe.org>
On 3/2/2010 8:54 PM, kevin0051 wrote:
> Can anyone help?
yes
--
"Six by nine. Forty two."
"That's it. That's all there is."
"I always thought something was fundamentally wrong with the universe"
------------------------------
Date: Tue, 02 Mar 2010 20:56:54 -0500
From: sreservoir <sreservoir@gmail.com>
Subject: Re: floating point issue?
Message-Id: <hmkfld$bgs$2@speranza.aioe.org>
On 3/2/2010 8:54 PM, kevin0051 wrote:
> The output of this program is
> 431.000000
> 430
>
> I don't know why the second output is 431 instead of 431.
> Can anyone help?
yes
--
"Six by nine. Forty two."
"That's it. That's all there is."
"I always thought something was fundamentally wrong with the universe"
------------------------------
Date: Tue, 02 Mar 2010 20:11:02 -0600
From: John Bokma <john@castleamber.com>
Subject: Re: floating point issue?
Message-Id: <87sk8irw7d.fsf@castleamber.com>
kevin0051 <kevin0051@gmail.com> writes:
> I made a perl program as follows.
>
> -----------------
> $AAA = 4.31;
> $AAA *= 100;
> printf ("%f\n", $AAA);
> printf ("%d\n", $AAA);
> ----------------
>
> The output of this program is
> 431.000000
> 430
>
> I don't know why the second output is 430 instead of 431.
> Can anyone help?
http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems
--
John Bokma j3b
Hacking & Hiking in Mexico - http://johnbokma.com/
http://castleamber.com/ - Perl & Python Development
------------------------------
Date: Tue, 02 Mar 2010 21:25:43 -0600
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: floating point issue?
Message-Id: <slrnhorlej.bso.tadmc@tadbox.sbcglobal.net>
kevin0051 <kevin0051@gmail.com> wrote:
> I made a perl program as follows.
You would have the same problem with any programming language.
The problem is related to how numbers are implemented on computers
rather than how any particular language behaves.
> -----------------
> $AAA = 4.31;
> $AAA *= 100;
> printf ("%f\n", $AAA);
> printf ("%d\n", $AAA);
> ----------------
>
> The output of this program is
> 431.000000
> 430
>
> I don't know why the second output is 430 instead of 431.
See if running this gives you any clues:
-----------------
#!/usr/bin/perl
use warnings;
use strict;
my $AAA = 4.31;
$AAA *= 100;
printf ("%30.20f\n", $AAA);
printf ("%d\n", $AAA);
printf ("%.0f\n", $AAA);
-----------------
see also:
perldoc -q numbers
Why am I getting long decimals (eg, 19.9499999999999) instead of
the numbers I should be getting (eg, 19.95)?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
------------------------------
Date: Tue, 02 Mar 2010 20:02:58 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: floating point issue?
Message-Id: <hcnro51hp4lvddqps3cn6opdvsv62t15la@4ax.com>
kevin0051 <kevin0051@gmail.com> wrote:
>I made a perl program as follows.
>
>-----------------
>$AAA = 4.31;
>$AAA *= 100;
>printf ("%f\n", $AAA);
>printf ("%d\n", $AAA);
>----------------
>
>The output of this program is
>431.000000
>430
>
>I don't know why the second output is 431 instead of 431.
I suppose you meant "430 instead of 431".
>Can anyone help?
Yes, among others your teacher for "Introduction into Fundamentals of
Basic Computer Numerics".
For more details please also try
printf("%.20f\n",$AAA);
to force 20 digits after the decimal.
For further explanations please see "perldoc -q 999' or previous
discussions in this NG about this ever popular topic.
jue
------------------------------
Date: Tue, 02 Mar 2010 22:15:49 -0800
From: Xho Jingleheimerschmidt <xhoster@gmail.com>
Subject: Re: floating point issue?
Message-Id: <4b8dfe67$0$11354$ed362ca5@nr5-q3a.newsreader.com>
John Bokma wrote:
> kevin0051 <kevin0051@gmail.com> writes:
>
>> I made a perl program as follows.
>>
>> -----------------
>> $AAA = 4.31;
>> $AAA *= 100;
>> printf ("%f\n", $AAA);
>> printf ("%d\n", $AAA);
>> ----------------
>>
>> The output of this program is
>> 431.000000
>> 430
>>
>> I don't know why the second output is 430 instead of 431.
>> Can anyone help?
>
> http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems
>
This surprised me. I knew int() would truncate of course, but I thought
printf with would round in the same way for %d as it does for %.0f,
rather than truncate.
Xho
------------------------------
Date: Wed, 3 Mar 2010 06:22:33 +0000 (UTC)
From: pacman@kosh.dhis.org (Alan Curry)
Subject: Re: flushing buffer for printing to the screen
Message-Id: <hmkv79$g5$1@speranza.aioe.org>
In article <878waatkvi.fsf@quad.sysarch.com>,
Uri Guttman <uri@StemSystems.com> wrote:
|but as i keep posting, the code as shown goes to stdout and the tty
|unless he redirects it. it is obvious he is looking for the support of
|print to the terminal without a newline. that is almost the only real
|use for $|.
My most usual real use for $| is when I've got normal output going to
stdout and verbose trace messages going to stderr, and want to pipe them
both into a pager. $| keeps them in order
--
Alan Curry
------------------------------
Date: Tue, 2 Mar 2010 16:55:48 -0800 (PST)
From: Adam Kellas <adam.kellas@gmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <dfa489bc-de77-4b7a-a981-a2b54ee79fe6@q21g2000yqm.googlegroups.com>
On Mar 2, 2:23=A0pm, "Uri Guttman" <u...@StemSystems.com> wrote:
> you would have to post all the code and some data and hopefully that
> would exhibit the problem. calling brk() means you are doing serious
> data allocation which shouldn't happen in this style of code. maybe you
> are doing something else that you didn't tell us. s/// ops on a string
> may add some ram needs but not insane amounts. massive unnecessary ram
> needs are usually leaks, either a rare perl bug or some poorly designed
> data structure that leaks.
For the record, this rewrite seems to solve the problem:
sub varify {
my $text =3D shift;
$text =3D~ s%\$%\$\$%g;
for (keys %MakeVars) {
my $name =3D $MakeVars{$_};
$text =3D~ s%$_%$name%g;
}
return $text;
}
Here the hash keys are precompiled REs, e.g.
my $re =3D qr/\Q$text\E/;
$MakeVars{$re} =3D $macro_name;
Thanks for the advice,
AK
------------------------------
Date: Tue, 02 Mar 2010 20:04:05 -0500
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <87fx4irzay.fsf@quad.sysarch.com>
>>>>> "AK" == Adam Kellas <adam.kellas@gmail.com> writes:
AK> On Mar 2, 2:23 pm, "Uri Guttman" <u...@StemSystems.com> wrote:
>> you would have to post all the code and some data and hopefully that
>> would exhibit the problem. calling brk() means you are doing serious
>> data allocation which shouldn't happen in this style of code. maybe you
>> are doing something else that you didn't tell us. s/// ops on a string
>> may add some ram needs but not insane amounts. massive unnecessary ram
>> needs are usually leaks, either a rare perl bug or some poorly designed
>> data structure that leaks.
AK> For the record, this rewrite seems to solve the problem:
AK> sub varify {
AK> my $text = shift;
AK> $text =~ s%\$%\$\$%g;
why the strange use of % for a delimiter? it is impossible to
read. actually one of the worst choices you can make IMO. besides you
don't need to do that as / is fine since you have no / in your regex.
AK> for (keys %MakeVars) {
use a named variable for loops. it is cleaner and easier to read. $_ can
be easily clobbered or some action at a distance can happen. my vars are
lexical to the loop and much safer
AK> my $name = $MakeVars{$_};
AK> $text =~ s%$_%$name%g;
again with the % delimiter. i would go blind reading that. and there is
no need for the temp $name as you can put that hash lookup directly in
the replacement string.
AK> }
AK> return $text;
AK> }
AK> Here the hash keys are precompiled REs, e.g.
AK> my $re = qr/\Q$text\E/;
you don't use % there, so why in the s/// ops?
AK> $MakeVars{$re} = $macro_name;
again, you don't need the temp var. and that will cause you to lose the
precompiled nature of qr. all keys in a hash are just plain strings (not
perl values). it may work anyhow but if you had something that needed to
be a real regex feature that broke when putting it in as a hash key, you
would be very sorry. why don't you make the hash based on the name
instead with the qr// as the value? it will always work correctly as a regex.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 02 Mar 2010 17:36:50 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <d1fro5pqp8cra1dg21ns8b9b3mqv64hnp8@4ax.com>
Adam Kellas <adam.kellas@gmail.com> wrote:
>For the record, this rewrite seems to solve the problem:
As execution speed was the issue at hand ...
>sub varify {
> my $text = shift;
> $text =~ s%\$%\$\$%g;
> for (keys %MakeVars) {
> my $name = $MakeVars{$_};
> $text =~ s%$_%$name%g;
... I would get rid of that unnecessary temporary variable $name and
thus save a string copy:
$text =~ s%$_%$MakeVars{$_}%g;
BTW: I find your % signs as s///-delimeters hard to read. Yes, they are
legal, yes there are occasions where using the standard slash is awkward
because you have to escape slashes that are part of the RE or the
replacement string. But none of those reasons exist here.
jue
------------------------------
Date: Tue, 2 Mar 2010 20:22:35 -0800 (PST)
From: Adam Kellas <adam.kellas@gmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <6497cc41-a541-484c-8cb2-d23edf62d007@q21g2000yqm.googlegroups.com>
On Mar 2, 8:04=A0pm, "Uri Guttman" <u...@StemSystems.com> wrote:
> why the strange use of % for a delimiter? it is impossible to
> read. actually one of the worst choices you can make IMO. besides you
> don't need to do that as / is fine since you have no / in your regex.
Style ... aesthetics ... religion ... I decided years ago that my
personal style guide would be to always use m%% and s%%%. It may be
ugly but it's consistent; I can always find patterns in my code by
searching for m% or s%. Try that with //! The other problem with // is
that half the time there are slashes in the pattern, and often the
pattern changes in such a way that you either can or have to change
the delimiter. I've never regretted adding this convention to my style
guide, though I'm sure a case could be made for preferring some other
inert character like s,,,.
> =A0 AK> =A0 =A0 for (keys %MakeVars) {
>
> use a named variable for loops. it is cleaner and easier to read. $_ can
> be easily clobbered or some action at a distance can happen. my vars are
> lexical to the loop and much safer
Use of $_ was deliberate here because I gather it's marginally faster
and I was trying to tune the loop for speed. But in general I agree
that named variables are preferable.
> =A0 AK> =A0 =A0 =A0 =A0my $name =3D $MakeVars{$_};
> =A0 AK> =A0 =A0 =A0 =A0$text =3D~ s%$_%$name%g;
>
> again with the % delimiter. i would go blind reading that. and there is
> no need for the temp $name as you can put that hash lookup directly in
> the replacement string.
Style ... aesthetics ... religion ...
> again, you don't need the temp var. and that will cause you to lose the
> precompiled nature of qr. all keys in a hash are just plain strings (not
> perl values). it may work anyhow but if you had something that needed to
> be a real regex feature that broke when putting it in as a hash key, you
> would be very sorry. why don't you make the hash based on the name
> instead with the qr// as the value? it will always work correctly as a re=
gex.
Thanks, I was not aware of that and will make changes as suggested.
AK
------------------------------
Date: Tue, 2 Mar 2010 20:26:28 -0800 (PST)
From: Adam Kellas <adam.kellas@gmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <186a2ce7-ab6a-4e7e-903c-be0d1677d42e@y17g2000yqd.googlegroups.com>
On Mar 2, 8:36=A0pm, J rgen Exner <jurge...@hotmail.com> wrote:
> BTW: I find your % signs as s///-delimeters hard to read. Yes, they are
> legal, yes there are occasions where using the standard slash is awkward
> because you have to escape slashes that are part of the RE or the
> replacement string. But none of those reasons exist here.
As noted, this is a deliberate tradeoff. Yes, it requires an
additional keystroke (or 4 if you count the shift key) and may
reasonably be called ugly. But OTOH I've legislated leaning toothpick
syndrome out of existence, and I've never once had to escape a % in a
regular expression. YMMV.
AK
------------------------------
Date: Tue, 2 Mar 2010 20:38:19 -0800 (PST)
From: Adam Kellas <adam.kellas@gmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <13315156-29e9-41d0-ac69-a5c569a54e78@z35g2000yqd.googlegroups.com>
On Mar 2, 1:07=A0pm, J rgen Exner <jurge...@hotmail.com> wrote:
> BTW: $substr is an awful name considering there is a function substr()
Granted, changed.
> and capitalized names ($Variables) normally indicate file handles.
OT I know, but I thought ALLCAPS names indicated file handles (as in
STDOUT) and CamelCase indicated global (or more properly "widely
scoped") variables?
AK
------------------------------
Date: Wed, 03 Mar 2010 00:12:08 -0500
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <87r5o2q993.fsf@quad.sysarch.com>
>>>>> "AK" == Adam Kellas <adam.kellas@gmail.com> writes:
AK> On Mar 2, 8:04 pm, "Uri Guttman" <u...@StemSystems.com> wrote:
>> why the strange use of % for a delimiter? it is impossible to
>> read. actually one of the worst choices you can make IMO. besides you
>> don't need to do that as / is fine since you have no / in your regex.
AK> Style ... aesthetics ... religion ... I decided years ago that my
AK> personal style guide would be to always use m%% and s%%%. It may be
AK> ugly but it's consistent; I can always find patterns in my code by
AK> searching for m% or s%. Try that with //! The other problem with // is
AK> that half the time there are slashes in the pattern, and often the
AK> pattern changes in such a way that you either can or have to change
AK> the delimiter. I've never regretted adding this convention to my style
AK> guide, though I'm sure a case could be made for preferring some other
AK> inert character like s,,,.
this isn't religion. there are plenty of religious wars on the net. this
is about quality code. readability matters. it makes your code easier to
understand, maintain, modify, etc. you may think this is cute and your
style but most others don't. someone else posted the same thing. as for
having / in the data, there is no way it is used that often. and regexes
don't usually change on the fly too often. finally the best (and this
comes from damian conway, among many others) alternate delimiter is
{}. it allows nested pairs of {} inside without escaping, it is easy to
see, it doesn't hide the regex itself. and you can even split the two
parts of s{} {} with spaces and it works.
>> AK> for (keys %MakeVars) {
>>
>> use a named variable for loops. it is cleaner and easier to read. $_ can
>> be easily clobbered or some action at a distance can happen. my vars are
>> lexical to the loop and much safer
AK> Use of $_ was deliberate here because I gather it's marginally faster
AK> and I was trying to tune the loop for speed. But in general I agree
AK> that named variables are preferable.
not fast enough to be worth it. we are talking minute speedups and your
code has other issues. readibility and safety easily trump the miniscule
speedup you may get in this case.
>> AK> my $name = $MakeVars{$_};
>> AK> $text =~ s%$_%$name%g;
>>
>> again with the % delimiter. i would go blind reading that. and there is
>> no need for the temp $name as you can put that hash lookup directly in
>> the replacement string.
AK> Style ... aesthetics ... religion ...
wrong, wronger and wrongest.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 2 Mar 2010 22:24:22 -0800 (PST)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: how to speed up a string-substitution loop?
Message-Id: <2cd71c88-ee93-4260-b746-e2b0a31708c4@g8g2000pri.googlegroups.com>
On Mar 2, 8:22=A0pm, Adam Kellas <adam.kel...@gmail.com> wrote:
> On Mar 2, 8:04=A0pm, "Uri Guttman" <u...@StemSystems.com> wrote:
>
> > why the strange use of % for a delimiter? it is impossible to
> > read. actually one of the worst choices you can make IMO. besides you
> > don't need to do that as / is fine since you have no / in your regex.
>
> Style ... aesthetics ... religion ... I decided years ago that my
> personal style guide would be to always use m%% and s%%%. It may be
> ...
You know of course religious threads will go on and on :)
The non-denominational /x switch can help with 's' pattern
readability:
$text =3D~ s% $_ %$name%gx;
And bracketing delimiters such as (),<>,{},[] can help in
seeing pattern/replacement parts if you're ever tempted to
stray from The True Way:
$test =3D~ s{ $_ } {$name}gx;
and can even be on multiple lines:
$test =3D~ s[ really long pattern ]
[some_replacement]gx;
--
Charles DeRykus
------------------------------
Date: Wed, 3 Mar 2010 00:10:03 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: strange behavior
Message-Id: <rvl067-8p2.ln1@osiris.mauzo.dyndns.org>
Quoth "efoss@fhcrc.org" <efoss@fhcrc.org>:
>
> Thanks very much. I just tried the first one - installing Perl 5.10.1.
> I had 5.10.0 before, which I checked with "perl -v". I then went
> here:
>
> http://www.activestate.com/activeperl/downloads/
>
> and I downloaded the recommended version. (I'm using MacOS X with the
> Snowleopard operating system.) Below is what it said it recommended:
>
> Recommended version(s) for your platform:
> ActivePerl 5.10.1.1007 for Mac OS X (Universal)
Hmmm. I wouldn't recommend AS Perl for Mac OS (or Win32 nowadays, for
that matter). Building perl from source is not difficult: install the
dev tools (last time I had anything to do with Mac OS they were on the
third or fourth install CD), download the tarball, untar it and run
./Configure -des
make
make test
make install
This will install the new perl into /usr/local/bin, which is correct
(see below). You realy don't want to overwrite Apple's perl in /usr/bin.
> I then restarted my computer and tried again and got the same error.
> However, then when I tried "perl -v" again, it said that I was using
> 5.10.0 rather than 5.10.1. I'm puzzled by this, since installing perl
> was pretty straight forward - just clicking "next" a bunch of times
> and accepting all the default settings. I'll screw around more with
> this to see if I can figure out what I'm doing wrong.
Your PATH environment variable is set wrong. If you type 'which perl' it
will tell you you are using /usr/bin/perl, which is Apple's perl. You
need to find out where AS perl gets installed (it might be
/usr/local/bin, it might not...) and prepend that directory to your
PATH.
Ben
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2846
***************************************
