[30252] in Perl-Users-Digest
Perl-Users Digest, Issue: 1495 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Apr 30 16:09:45 2008
Date: Wed, 30 Apr 2008 13:09:09 -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, 30 Apr 2008 Volume: 11 Number: 1495
Today's topics:
Re: Compress::Zlib inflateInit help (hymie!)
Devel::SmallProf claims "return 1" needs much time !? <w.c.humann@arcor.de>
Re: Devel::SmallProf claims "return 1" needs much time xhoster@gmail.com
Re: Devel::SmallProf claims "return 1" needs much time <w.c.humann@arcor.de>
Re: Pipe and Par questions <edgrsprj@ix.netcom.com>
Re: Python's doc problems: sort <jpthing@online.no>
Re: Read 20 lines when pressing n for next <syscjm@sumire.gwu.edu>
Re: Read 20 lines when pressing n for next <jurgenex@hotmail.com>
Re: Read 20 lines when pressing n for next <1usa@llenroc.ude.invalid>
Re: Read 20 lines when pressing n for next <tzz@lifelogs.com>
Re: use perl to draw Venn Diagram <tzz@lifelogs.com>
Re: use perl to draw Venn Diagram <simon.chao@fmr.com>
Re: use perl to draw Venn Diagram <tzz@lifelogs.com>
Re: What's wrong with transparency by GD? <smallpond@juno.com>
Re: What's wrong with transparency by GD? <ela@yantai.org>
Re: What's wrong with transparency by GD? <smallpond@juno.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 30 Apr 2008 10:45:13 -0500
From: hymie_@_lactose.homelinux.net (hymie!)
Subject: Re: Compress::Zlib inflateInit help
Message-Id: <ZaSdnYNcCeKUCYXVnZ2dnUVZ_qCunZ2d@comcast.com>
In our last episode, the evil Dr. Lacto had captured our hero,
Paul Marquess <paul.marquess@btinternet.com>, who said:
>The key part I didn't know was you are dealing with a sequence of compressed
>RFC 1951 data streams that are each prefixed with a bespoke header. So that
>means you need to deal with reading both compressed & non-compressed data
>from the socket.
Sorry. I didn't realize that the data and the acquisition of the data
were so badly intertwined.
>my $header;
>my $header_size = 8 + 4 + 4; # time + sequence + size
>while (read($socket, $header, $header_size) == $header_size)
>{
>
> my ($time1, $time2, $sequence, $size) = unpack "NNNN", $header;
>
> rawinflate $socket => \$data, InputLength => $size
> or die "Cannot uncompress: $RawInflateError\n";
> print "$data\n";
>}
This is perfect!!!
Thank you so much for your help.
--hymie! http://lactose.homelinux.net/~hymie hymie@lactose.homelinux.net
------------------------ Without caffeine for 547 days ------------------------
------------------------------
Date: Wed, 30 Apr 2008 05:51:21 -0700 (PDT)
From: whumann <w.c.humann@arcor.de>
Subject: Devel::SmallProf claims "return 1" needs much time !?
Message-Id: <269193e8-0d57-41f4-8cdd-41cf2ea86c87@25g2000hsx.googlegroups.com>
I'm trying to do some profiling on DBM::Deep. I started with
Devel::DProf and Devel::Profile but for some subs I had no idea *why*
they took long, so I tried Devel::SmallProf for additional detail.
Much of what I see makes sense but results like this puzzle me (these
are the subs that do the low-level disc read and write):
count wall tm cpu time line
0 0.00000 0.00000 103:sub print_at {
314000 0.96161 3.67000 104: my $self = shift;
314000 0.88398 3.34000 105: my $loc = shift;
0 0.00000 0.00000 106:
314000 1.51351 3.89000 107: local ($/,$\);
0 0.00000 0.00000 108:
314000 1.07561 3.94000 109: my $fh = $self->{fh};
314000 4.39820 7.83000 110: if ( defined $loc ) {
0 0.00000 0.00000 111: seek( $fh, $loc + $self-
0 0.00000 0.00000 112: }
0 0.00000 0.00000 113:
314000 3.46850 6.32000 114: print( $fh @_ ) or die
"Internal Error
0 0.00000 0.00000 115:
314000 6.65324 9.86000 116: return 1;
0 0.00000 0.00000 117:}
0 0.00000 0.00000 118:
0 0.00000 0.00000 119:sub read_at {
500507 1.43996 6.05000 120: my $self = shift;
500507 1.60207 5.78000 121: my ($loc, $size) = @_;
0 0.00000 0.00000 122:
500507 2.44265 7.01000 123: local ($/,$\);
0 0.00000 0.00000 124:
500507 1.43653 5.88000 125: my $fh = $self->{fh};
500507 7.14111 11.73000 126: if ( defined $loc ) {
0 0.00000 0.00000 127: seek( $fh, $loc + $self-
0 0.00000 0.00000 128: }
0 0.00000 0.00000 129:
500507 1.41859 6.08000 130: my $buffer;
500507 4.36185 8.77000 131: read( $fh, $buffer, $size);
0 0.00000 0.00000 132:
500507 7.96107 12.04000 133: return $buffer;
0 0.00000 0.00000 134:}
Much of the time is spent in "seek", "print" and "read" -- as expected
(although I'm surprised it's only tenths of microseconds per call -- I
suppose disc caches work their wonders...). But even more time is
spent in the two "return" statements, and I don't know why! I thought
that maybe they contain the overhead of function calling/returning but
coudn't verify that in a simple testscript. Is this an artifact of the
perl debugger? Or what else is the cause for this?
Thanks for any help understanding this.
Wolfram
------------------------------
Date: 30 Apr 2008 16:38:13 GMT
From: xhoster@gmail.com
Subject: Re: Devel::SmallProf claims "return 1" needs much time !?
Message-Id: <20080430123814.919$nI@newsreader.com>
whumann <w.c.humann@arcor.de> wrote:
> I'm trying to do some profiling on DBM::Deep. I started with
> Devel::DProf and Devel::Profile but for some subs I had no idea *why*
> they took long, so I tried Devel::SmallProf for additional detail.
> Much of what I see makes sense but results like this puzzle me (these
> are the subs that do the low-level disc read and write):
I often find SmallProf to be unreliable, especially when trying to profile
code portions which are fast on each execution but are executed very often.
>
> count wall tm cpu time line
> 0 0.00000 0.00000 103:sub print_at {
> 314000 0.96161 3.67000 104: my $self = shift;
> 314000 0.88398 3.34000 105: my $loc = shift;
> 0 0.00000 0.00000 106:
> 314000 1.51351 3.89000 107: local ($/,$\);
> 0 0.00000 0.00000 108:
> 314000 1.07561 3.94000 109: my $fh = $self->{fh};
> 314000 4.39820 7.83000 110: if ( defined $loc ) {
This just seems weird. My 3GHz machine does an if defined test 32 times
faster, so unless you have an old computer I would say that this casts
doubt on the entire reliability of the SmallProf output.
...
> 0 0.00000 0.00000 115:
> 314000 6.65324 9.86000 116: return 1;
> 0 0.00000 0.00000 117:}
...
>
> Much of the time is spent in "seek", "print" and "read" -- as expected
> (although I'm surprised it's only tenths of microseconds per call -- I
> suppose disc caches work their wonders...). But even more time is
> spent in the two "return" statements, and I don't know why! I thought
> that maybe they contain the overhead of function calling/returning but
> coudn't verify that in a simple testscript.
Your return is only taking ~50-100% longer than your "if defined". While
both of them are taking absurdly long, that ratio is about what I find in a
simple test script. Is your machine old and slow? Is it perhaps swapping
itself to death during this test, or heavily loaded with other people's
processes?
If you can post the entire harness (provided it is small) you are using to
profile DBM::Deep, I'll play with it a bit.
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: Wed, 30 Apr 2008 13:06:24 -0700 (PDT)
From: Wolfram Humann <w.c.humann@arcor.de>
Subject: Re: Devel::SmallProf claims "return 1" needs much time !?
Message-Id: <23ce7347-04fc-4712-b0e1-f1f2049318bf@r66g2000hsg.googlegroups.com>
On Apr 30, 6:38=A0pm, xhos...@gmail.com wrote:
>
> This just seems weird. =A0My 3GHz machine does an if defined test 32 times=
> faster, so unless you have an old computer I would say that this casts
> doubt on the entire reliability of the SmallProf output.
I think you got somthing wrong here. The profiler runs on the comiled
and optimized code where several source-lines may have become one. If
you look at the "count"-column, you will see that line 110 includes
the time for seek() in the next line. Im my experience, the shortest-
running lines in a script (e.g. "my $self =3D shift;") will indeed vary
a lot from run to run because of the nulltime-compensation im
SmallProf. The lines we're talking about are fairly stable.
> If you can post the entire harness (provided it is small) you are using to=
> profile DBM::Deep, I'll play with it a bit.
Every script that imports heavily in DBM::Deep will do. Mine looks
like this:
BEGIN
{
$DB::profile =3D 0;
%DB::packages =3D ( 'DBM::Deep::Engine' =3D> 1,
'DBM::Deep::Engine::Sector' =3D> 1, 'DBM::Deep::File' =3D> 1 );
}
use strict;
use warnings;
use DBM::Deep;
my $text =3D 'this is always the same dummy text';
my $inner =3D 500;
my $outer =3D 2;
my $profilefile =3D "prof.out";
my $db =3D DBM::Deep->new( "deeptest2.db" );
for my $j (1..$outer)
{
my $data;
for my $i (1..$inner)
{
my %hash =3D map { +"subkey$_" =3D> $text } (12..30);
$data->{"key$i"} =3D \%hash;
}
$DB::profile =3D 1 if $j =3D=3D $outer;
my $t =3D time();
$db->import($data);
print "Import duration: ", time() - $t, "\n";
}
But I can't say exactly how $inner and $outer were set when I created
the posted profile. Also, I already did some changes in DBM::Deep that
might affect performance.
Wolfram
------------------------------
Date: Wed, 30 Apr 2008 08:50:47 -0500
From: "E.D.G." <edgrsprj@ix.netcom.com>
Subject: Re: Pipe and Par questions
Message-Id: <9eGdnXB0u9ah5IXVnZ2dnUVZ_vudnZ2d@earthlink.com>
> Is there a specific reason why you stealth CCed me? I happen to read the
> NGs I am writing in!
Yes. I am posting some of these notes using a new computer with Windows
Vista and associated e-mail programs etc. instead of the more familiar
Windows XP. And that first response was sent by accident to your e-mail
address instead of to this Newsgroup.
> It's not a command (well, it could be on Unix) but a Perl module that
> provides an interface similar to the expect utility.
>
> jue
I understand. Thanks again.
------------------------------
Date: Wed, 30 Apr 2008 12:35:10 +0200
From: "John Thingstad" <jpthing@online.no>
Subject: Re: Python's doc problems: sort
Message-Id: <op.uae6cwlgut4oq5@pandora.alfanett.no>
På Wed, 30 Apr 2008 06:26:31 +0200, skrev George Sakkis
<george.sakkis@gmail.com>:
> On Apr 29, 11:13 pm, Jürgen Exner <jurge...@hotmail.com> wrote:
>
>> "xah...@gmail.com" <xah...@gmail.com> wrote:
>>
>> Is this self-promoting maniac still going at it?
>>
>> >Although i disliked Perl very much [...]
>>
>> Then why on earth do you bother polluting this NG?
>>
>> Back into the killfile you go
>>
>> jue
>
> \|||/
> (o o)
> ,----ooO--(_)-------.
> | Please |
> | don't feed the |
> | TROLL's ! |
> '--------------Ooo--'
> |__|__|
> || ||
> ooO Ooo
Doesn't copying Rainer Joswig's troll warning constitute a copywright
infrigment :)
--------------
John Thingstad
------------------------------
Date: Wed, 30 Apr 2008 10:49:27 -0500
From: Chris Mattern <syscjm@sumire.gwu.edu>
Subject: Re: Read 20 lines when pressing n for next
Message-Id: <slrng1h584.r80.syscjm@sumire.gwu.edu>
On 2008-04-30, A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
> s9uzaa@gmail.com wrote in news:37b9eb38-e188-4dc2-b3a7-
> 5f09cc3b81ea@a70g2000hsh.googlegroups.com:
>
>> I would like to write a perl script with the following criteria match.
>
> Give it a shot. Then post any questions you might encounter (please read
> the posting guidelines first).
>
>> 1. open any text file taken the name from the command line.
>> 2. read top 20 lines and stops, then
>> 3. ask to press letter "n or p" (for next/previous) to print next or
>> previous 20 lines.
>> would appreciate any kind of help.
>> 4. must have subroutine used.
>
> Look up $. in perldoc perlvar
>
I got $5 that says this is homework. "must have subroutine used" is
a dead giveaway.
--
Christopher Mattern
NOTICE
Thank you for noticing this new notice
Your noticing it has been noted
And will be reported to the authorities
------------------------------
Date: Wed, 30 Apr 2008 16:46:52 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Read 20 lines when pressing n for next
Message-Id: <rc8h14hn74hmr1dqeg340vlfg1af0k7sf4@4ax.com>
Chris Mattern <syscjm@sumire.gwu.edu> wrote:
>On 2008-04-30, A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
>> s9uzaa@gmail.com wrote in news:37b9eb38-e188-4dc2-b3a7-
>>> 4. must have subroutine used.
>>
>> Look up $. in perldoc perlvar
>>
>I got $5 that says this is homework. "must have subroutine used" is
>a dead giveaway.
Absolutely agree. However, the tutor isn't that smart, either.
A sub
sub do_nothing{};
that is called somewhere in the program would already fulfill that
requirement. Probably not what he had in mind but apparently he couldn't
come up with a more appropriate one.
jue
------------------------------
Date: Wed, 30 Apr 2008 17:51:31 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Read 20 lines when pressing n for next
Message-Id: <Xns9A908CF974FFDasu1cornelledu@127.0.0.1>
Chris Mattern <syscjm@sumire.gwu.edu> wrote in
news:slrng1h584.r80.syscjm@sumire.gwu.edu:
> On 2008-04-30, A. Sinan Unur <1usa@llenroc.ude.invalid> wrote:
>> s9uzaa@gmail.com wrote in news:37b9eb38-e188-4dc2-b3a7-
>> 5f09cc3b81ea@a70g2000hsh.googlegroups.com:
>>
>>> I would like to write a perl script with the following criteria
>>> match.
>>
>> Give it a shot. Then post any questions you might encounter (please
>> read the posting guidelines first).
>>
>>> 1. open any text file taken the name from the command line.
>>> 2. read top 20 lines and stops, then
>>> 3. ask to press letter "n or p" (for next/previous) to print next or
>>> previous 20 lines.
>>> would appreciate any kind of help.
>>> 4. must have subroutine used.
>>
>> Look up $. in perldoc perlvar
>>
> I got $5 that says this is homework. "must have subroutine used" is
> a dead giveaway.
Agreed. Which is why he does not get any fish before showing his
attempts at fishing for himself ;-)
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://www.rehabitation.com/clpmisc/
------------------------------
Date: Wed, 30 Apr 2008 13:15:47 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Read 20 lines when pressing n for next
Message-Id: <86ej8np5t8.fsf@lifelogs.com>
On Tue, 29 Apr 2008 18:21:12 -0700 (PDT) s9uzaa@gmail.com wrote:
s> I would like to write a perl script with the following criteria match.
s> 1. open any text file taken the name from the command line.
s> 2. read top 20 lines and stops, then
s> 3. ask to press letter "n or p" (for next/previous) to print next or
s> previous 20 lines.
s> would appreciate any kind of help.
s> 4. must have subroutine used.
perl -e'sub { exec less => -20 => @_}->(@ARGV)' FILE1 FILE2 ...
Unfortunately this uses SPACE or `f' instead of `n' to advance to the
next 20 lines, but I think it meets all the other criteria.
Good luck!
Ted
------------------------------
Date: Wed, 30 Apr 2008 13:17:01 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: use perl to draw Venn Diagram
Message-Id: <86abjbp5r6.fsf@lifelogs.com>
On Tue, 29 Apr 2008 12:31:06 GMT zentara <zentara@highstream.net> wrote:
z> On Mon, 28 Apr 2008 23:55:57 +0800, "Ela" <ela@yantai.org> wrote:
>>> You could probably also use brushes instead. Anyway all the
>>> information is really there in the docs. If you're unable to create a
>>> working script from that, you may want to post at least what you've
>>> got now and what you're having difficulty with *exactly*. Just
>>> claiming GD doesn't do what you want when it clearly does and even
>>> provide examples in the docs isn't helping.
>>>
>>> Take some time to read the full manpage linked above, it's not that
>>> big and you should be able to figure it out yourself.
>>>
>> I feel sorry for not understanding what "holes" refer to... Not
>> complimenting Matlab, but I am used to its elegant library to provide
>> intuitive and powerful functions... Certainly, GD provides a greater control
>> over how wide the holes can be...
>>
z> If you need to do this without X, you might want to look at the Cairo
z> module
z> http://cairographics.org/samples/
z> You can save them to many file formats. Gtk2's graphics are based
z> on Cairo.
Also the OP may want to consider Matlab's own scripting abilities which
are pretty decent.
Ted
------------------------------
Date: Wed, 30 Apr 2008 11:23:07 -0700 (PDT)
From: nolo contendere <simon.chao@fmr.com>
Subject: Re: use perl to draw Venn Diagram
Message-Id: <d1763ea8-b5f7-4d92-82b8-6c3b98bec910@c65g2000hsa.googlegroups.com>
On Apr 30, 2:17=A0pm, Ted Zlatanov <t...@lifelogs.com> wrote:
> On Tue, 29 Apr 2008 12:31:06 GMT zentara <zent...@highstream.net> wrote:
>
> z> On Mon, 28 Apr 2008 23:55:57 +0800, "Ela" <e...@yantai.org> wrote:
>
> >>> You could probably also use brushes instead. Anyway all the
> >>> information is really there in the docs. If you're unable to create a
> >>> working script from that, you may want to post at least what you've
> >>> got now and what you're having difficulty with *exactly*. Just
> >>> claiming GD doesn't do what you want when it clearly does and even
> >>> provide examples in the docs isn't helping.
>
> >>> Take some time to read the full manpage linked above, it's not that
> >>> big and you should be able to figure it out yourself.
>
> >> I feel sorry for not understanding what "holes" refer to... Not
> >> complimenting Matlab, but I am used to its elegant library to provide
> >> intuitive and powerful functions... Certainly, GD provides a greater co=
ntrol
> >> over how wide the holes can be...
>
> z> If you need to do this without X, you might want to look at the Cairo
> z> module
> z>http://cairographics.org/samples/
>
> z> You can save them to many file formats. Gtk2's graphics are based
> z> on Cairo.
>
> Also the OP may want to consider Matlab's own scripting abilities which
> are pretty decent.
Really? I have only cursory experience with Matlab, which was used in
a genomics course I took, but I wasn't very impressed. Guess I didn't
look closely enough at it.
------------------------------
Date: Wed, 30 Apr 2008 14:56:59 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: use perl to draw Venn Diagram
Message-Id: <86ve1znmk4.fsf@lifelogs.com>
On Wed, 30 Apr 2008 11:23:07 -0700 (PDT) nolo contendere <simon.chao@fmr.com> wrote:
nc> On Apr 30, 2:17 pm, Ted Zlatanov <t...@lifelogs.com> wrote:
>> Also the OP may want to consider Matlab's own scripting abilities which
>> are pretty decent.
nc> Really? I have only cursory experience with Matlab, which was used in
nc> a genomics course I took, but I wasn't very impressed. Guess I didn't
nc> look closely enough at it.
It's pretty decent for what it does. For example, you can easily loop
over N values and do a plot that depends on the current value, which is
what the OP wanted. There's nntp:comp.soft-sys.matlab too.
See:
http://www.math.ucdavis.edu/~sawilliams/MATLABguide.html
http://physics.gac.edu/~huber/envision/tutor2/mtlscrip.htm
... and many other M-file examples Google returned, plus Mathworks' own site ...
Note I use "scripts" when I mean functions as well in the Matlab
context.
Ted
------------------------------
Date: Wed, 30 Apr 2008 07:11:03 -0700 (PDT)
From: smallpond <smallpond@juno.com>
Subject: Re: What's wrong with transparency by GD?
Message-Id: <05ebef10-432d-4d51-8d0e-98d889712a3a@m3g2000hsc.googlegroups.com>
On Apr 30, 4:05 am, "Ela" <e...@yantai.org> wrote:
> After testing different parameters, I'm still unable to obtain 2 transparent
> circles. Could anybody tell me what's wrong in the following codes?
>
> #!/usr/bin/perl
> use GD;
>
> $im = new GD::Image(550,450);
> $white = $im->colorAllocate(255,255,255);
> $black = $im->colorAllocate(0,0,0);
> $red = $im->colorAllocateAlpha(255,0,0,119);
> $blue = $im->colorAllocateAlpha(0,0,255,119);
> $im->transparent($white);
> $im->alphaBlending(1);
> $im->setStyle($black);
>
> $im->filledArc(460,380,95,75,0,360,$red);
> $im->filledArc(500,380,95,75,0,360,$blue);
>
> open(IMG, ">test.png");
> binmode IMG;
> print IMG $im->png;
> close IMG;
"Blending mode is not available when drawing on palette images."
You need to be in true color mode, the default is palette mode.
--S
------------------------------
Date: Wed, 30 Apr 2008 23:20:45 +0800
From: "Ela" <ela@yantai.org>
Subject: Re: What's wrong with transparency by GD?
Message-Id: <fva2oh$jkb$1@ijustice.itsc.cuhk.edu.hk>
> "Blending mode is not available when drawing on palette images."
> You need to be in true color mode, the default is palette mode.
> --S
You're correct. But why does color mode change lead to background
blackening?
------------------------------
Date: Wed, 30 Apr 2008 09:05:45 -0700 (PDT)
From: smallpond <smallpond@juno.com>
Subject: Re: What's wrong with transparency by GD?
Message-Id: <a7875a4d-d322-4276-bb1e-ad6d03cac9df@m73g2000hsh.googlegroups.com>
On Apr 30, 11:20 am, "Ela" <e...@yantai.org> wrote:
> > "Blending mode is not available when drawing on palette images."
> > You need to be in true color mode, the default is palette mode.
> > --S
>
> You're correct. But why does color mode change lead to background
> blackening?
New questions should go in new threads.
You need to initialize the background.
# Draw a transparent background
$bkg = $im->colorAllocateAlpha(0,0,0,127);
$im->transparent($bkg);
$im->alphaBlending(0); # replace pixels
$im->filledRectangle(0,0,549,449,$bkg);
# Now draw with blending
$im->alphaBlending(1);
now draw your circles
------------------------------
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 1495
***************************************
