[31317] in Perl-Users-Digest
Perl-Users Digest, Issue: 2562 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Aug 20 09:09:47 2009
Date: Thu, 20 Aug 2009 06:09:08 -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 Thu, 20 Aug 2009 Volume: 11 Number: 2562
Today's topics:
Detecting non-printing characters(?) <ldolan@thinkinghatbigpond.net.au>
Re: Detecting non-printing characters(?) <ben@morrow.me.uk>
Re: Detecting non-printing characters(?) <jurgenex@hotmail.com>
Re: Detecting non-printing characters(?) sln@netherlands.com
Re: How to code an implicit $_ argument? (Tim McDaniel)
Re: How to code an implicit $_ argument? <nospam-abuse@ilyaz.org>
Re: How to code an implicit $_ argument? <ben@morrow.me.uk>
Re: How to code an implicit $_ argument? <m@rtij.nl.invlalid>
Perl/Postgresql Content Management Systems(?) (Jamie)
Re: Perl/Postgresql Content Management Systems(?) <bugbear@trim_papermule.co.uk_trim>
Re: python doc available in emacs info format? <politza@googlemail.com>
Re: python doc available in emacs info format? <nat.k@gm.ml>
Re: replace everything from the 6th character on with a <someone@example.com>
Re: replace everything from the 6th character on with a <tadmc@seesig.invalid>
Re: revisiting web development in Perl...where to start <nat.k@gm.ml>
Re: search for hex characters in a binary file and remo <josef.moellers@ts.fujitsu.com>
trapping errors using $! <john1949@yahoo.com>
Re: trapping errors using $! <peter@makholm.net>
Re: trapping errors using $! <bugbear@trim_papermule.co.uk_trim>
Re: windows one liner to output unix line feed <glennj@ncf.ca>
Re: windows one liner to output unix line feed <glennj@ncf.ca>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 19 Aug 2009 23:14:33 GMT
From: "Peter Jamieson" <ldolan@thinkinghatbigpond.net.au>
Subject: Detecting non-printing characters(?)
Message-Id: <tH%im.12881$ze1.11521@news-server.bigpond.net.au>
Each day I use the LWP module to retrieve web pages then parse out useful
information from a single site, all OK except that occasionally a page does
not parse as expected. I examined the errant page but could see no
visual difference. I examined the source HTML line by line comparing the
errant page with a normal page but no visible difference at all.
Is it possible that there are non-printing characters present in the errant
pages that are causing my parser script to fail?
If so how can I detect and remove them?
Thanx for any assistance! Cheers, Peter
------------------------------
Date: Thu, 20 Aug 2009 00:24:25 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Detecting non-printing characters(?)
Message-Id: <96eul6-8j31.ln1@osiris.mauzo.dyndns.org>
Quoth "Peter Jamieson" <ldolan@thinkinghatbigpond.net.au>:
> Each day I use the LWP module to retrieve web pages then parse out useful
> information from a single site, all OK except that occasionally a page does
> not parse as expected. I examined the errant page but could see no
> visual difference. I examined the source HTML line by line comparing the
> errant page with a normal page but no visible difference at all.
>
> Is it possible that there are non-printing characters present in the errant
> pages that are causing my parser script to fail?
> If so how can I detect and remove them?
Removing non-printing characters is a simple matter of
$page =~ s/[^[:print:]]+//g;
though you should be aware of potential issues with non-ASCII pages. You
may need to decode and then use \P{Print} instead.
If you have further questions, you will need to post the code you are
using for parsing, an example that works and an example that doesn't. If
you make the effort to cut down both code and examples to the minimum
required to demonstrate the failure, you are more likely to get a useful
response. (You are also more likely to figure out the problem on your
owm, which is better for everyone.)
Ben
------------------------------
Date: Wed, 19 Aug 2009 18:23:58 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Detecting non-printing characters(?)
Message-Id: <c49p85hs2666hd9p3gf3n362uf303h1c49@4ax.com>
"Peter Jamieson" <ldolan@thinkinghatbigpond.net.au> wrote:
>Each day I use the LWP module to retrieve web pages then parse out useful
>information from a single site, all OK except that occasionally a page does
>not parse as expected. I examined the errant page but could see no
>visual difference. I examined the source HTML line by line comparing the
>errant page with a normal page but no visible difference at all.
Did you try a diff between the working and the errant page?
>Is it possible that there are non-printing characters present in the errant
>pages that are causing my parser script to fail?
Don't know, maybe. However IMO it's more likely that either the page is
not correct HTML (did you check with an HTML validator) and therefore
the parser chokes or the there is an error in your parser.
>If so how can I detect and remove them?
Perl's regular expressions support the POSIX :print: character class.
jue
------------------------------
Date: Wed, 19 Aug 2009 19:45:33 -0700
From: sln@netherlands.com
Subject: Re: Detecting non-printing characters(?)
Message-Id: <v8dp85147fdr1k9ahpulcnj7m9khqo83kr@4ax.com>
On Wed, 19 Aug 2009 23:14:33 GMT, "Peter Jamieson" <ldolan@thinkinghatbigpond.net.au> wrote:
>Each day I use the LWP module to retrieve web pages then parse out useful
>information from a single site, all OK except that occasionally a page does
>not parse as expected. I examined the errant page but could see no
>visual difference. I examined the source HTML line by line comparing the
>errant page with a normal page but no visible difference at all.
>
>Is it possible that there are non-printing characters present in the errant
>pages that are causing my parser script to fail?
>If so how can I detect and remove them?
>
>Thanx for any assistance! Cheers, Peter
>
What kind of error? Even wrong encodings should parse. I mean its
not die'ing is it?
How do you parse it, write it to file then pass the handler to the parser,
or just pass the buffer to it? Is the buffer bytes or utf8 promoted with
embed chars.
Have you examined the buffer with something like this?
for (map {ord $_} split //, $line) {
printf ("%x ",$_);
}
How does an errant page equal a normal page. Are they supposed to
be the same all the time?
-sln
------------------------------
Date: Wed, 19 Aug 2009 18:36:59 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Re: How to code an implicit $_ argument?
Message-Id: <h6hgob$8aq$1@reader1.panix.com>
In article <ojjtl6-7f03.ln1@osiris.mauzo.dyndns.org>,
Ben Morrow <ben@morrow.me.uk> wrote:
>
>Quoth tmcd@panix.com:
>> sub trim(_) {
>> my $var = $_[0];
>
> my $var = \$_[0];
Wait, you can *do* that?! I knew you could assign to $_[expr] itself
to change the caller's argument, but you can take a reference to it
and use that to change it too?
... clickity click ...
Sumbitch, you can! And it works for the aliasing in foreach too
(presumably because it's the exact same concept).
-- Tim McDaniel, tmcd@panix.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#! /usr/bin/perl -w
use strict;
sub foo(_) {
my $var = \$_[0];
++$$var;
return undef;
}
$_ = 19;
my $v = 23;
foo($v);
print "v: $v\n";
($v == 24) || die;
foo();
print "_: $_\n";
($_ == 20) || die;
my @a = (123, 456, 789);
foreach (@a) {
my $var = \$_;
$$var *= 10;
}
foreach (@a) {
print "a value is $_\n";
die unless $_ % 10 == 0;
}
exit 0;
------------------------------
Date: Wed, 19 Aug 2009 20:53:03 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: How to code an implicit $_ argument?
Message-Id: <slrnh8ophf.25c.nospam-abuse@chorin.math.berkeley.edu>
On 2009-08-19, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>>> if (@_ == 0) {
>>> $_[0] = \$_;
>>> goto &trim;
>>> }
>>
>> push @_, $_ unless @_;
>
> That pushes a copy of $_ onto @_.
Thanks, indeed. (I always wanted to implement
hard_set(\@array, $slot) = $var;
which would alias a slot in array/hash to a scalar...)
Thanks again,
Ilya
------------------------------
Date: Wed, 19 Aug 2009 22:20:14 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to code an implicit $_ argument?
Message-Id: <et6ul6-liv.ln1@osiris.mauzo.dyndns.org>
Quoth Ilya Zakharevich <nospam-abuse@ilyaz.org>:
>
> Thanks, indeed. (I always wanted to implement
>
> hard_set(\@array, $slot) = $var;
>
> which would alias a slot in array/hash to a scalar...)
I believe Chip is working on a patch to implement
$array[$slot] := $var;
like in Perl 6.
Ben
------------------------------
Date: Thu, 20 Aug 2009 07:08:45 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: How to code an implicit $_ argument?
Message-Id: <tb2vl6-7pb.ln1@news.rtij.nl>
On Wed, 19 Aug 2009 16:01:38 +0000, Tim McDaniel wrote:
>>Just drop the first test and it looks fine.
>
> You didn't notice what I wrote in a previous article, that I want it to
> silently ignore arguments that are undef, and not emit "Use of
> uninitialized value $_ in substitution (s///)" messages.
Oops, sorry. However, you may wonder if this terseness is worth this
potential confusion.
M4
------------------------------
Date: Thu, 20 Aug 2009 07:38:26 GMT
From: nospam@geniegate.com (Jamie)
Subject: Perl/Postgresql Content Management Systems(?)
Message-Id: <Lc1250753072194170x1788950@saturn>
Every now and then I get the urge to try out CMS's, mainly just to
see whats so great about them, so far, the ones I've looked at have
been PHP + mysql, but.. I'd really like to find a popular CMS
that's based on postgresql and perl.
The only perl solution I've found is bricolage, but.. it needs
mod_perl 1.x and has a lot of dependencies (that don't seem
to work)
The documentation looks impressive though. (and it appears to be some-what
popular too) it's just that installing this thing in a separate area, (I don't
want it in my system directories) has turned into a 2 day project that still
doesn't work. It's got to work on FreeBSD and Linux.
Any other perl CMS's that are postgresql based? (would be nice
if they used CGI/FastCGI instead of mod_perl, but for something like
this, mod_perl is OK)
I've seen a few that are mysql based, but I'm interested in postgresql.
Jamie
--
http://www.geniegate.com Custom web programming
Perl * Java * UNIX User Management Solutions
------------------------------
Date: Thu, 20 Aug 2009 08:58:52 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: Perl/Postgresql Content Management Systems(?)
Message-Id: <hrydnbvCcOihnxDXnZ2dnUVZ8gNi4p2d@brightview.co.uk>
Jamie wrote:
> Every now and then I get the urge to try out CMS's, mainly just to
> see whats so great about them, so far, the ones I've looked at have
> been PHP + mysql, but.. I'd really like to find a popular CMS
> that's based on postgresql and perl.
>
> The only perl solution I've found is bricolage, but.. it needs
> mod_perl 1.x and has a lot of dependencies (that don't seem
> to work)
>
> The documentation looks impressive though. (and it appears to be some-what
> popular too) it's just that installing this thing in a separate area, (I don't
> want it in my system directories) has turned into a 2 day project that still
> doesn't work. It's got to work on FreeBSD and Linux.
>
> Any other perl CMS's that are postgresql based? (would be nice
> if they used CGI/FastCGI instead of mod_perl, but for something like
> this, mod_perl is OK)
>
> I've seen a few that are mysql based, but I'm interested in postgresql.
>
> Jamie
If the PHP/Perl layer is doing its job, it shouldn't
really matter what the DB is.
BugBear
------------------------------
Date: Wed, 19 Aug 2009 13:17:19 -0700 (PDT)
From: "A.Politz" <politza@googlemail.com>
Subject: Re: python doc available in emacs info format?
Message-Id: <c760331d-9e9b-4b30-b00e-35f2fe29af36@d21g2000vbm.googlegroups.com>
On Aug 17, 6:43=A0am, Xah Lee <xah...@gmail.com> wrote:
> btw, is there still [no] info format for python doc?
>
> i feel kinda sad [...]
> Part of this is due to [other peoples fault]
Someone started a rst2info project (google it), maybe you want to help
this guy out.
Though, he might be a techgeeker, so watch out !
-ap
------------------------------
Date: Wed, 19 Aug 2009 17:58:15 -0700
From: Nathan Keel <nat.k@gm.ml>
Subject: Re: python doc available in emacs info format?
Message-Id: <Ic1jm.269514$Ta5.187649@newsfe15.iad>
A.Politz wrote:
> On Aug 17, 6:43Â am, Xah Lee <xah...@gmail.com> wrote:
>> btw, is there still [no] info format for python doc?
>>
>> i feel kinda sad [...]
>> Part of this is due to [other peoples fault]
>
> Someone started a rst2info project (google it), maybe you want to help
> this guy out.
>
> Though, he might be a techgeeker, so watch out !
>
> -ap
Don't bother with this Xah Lee clown. He posts random crap because he
thinks everyone wants to hear what he has to say about unrelated
subject material and thinks he looks smart for doing it. Unfortunately,
he usually lacks a clue about any topic he brings up (and he always
starts a new thread like he's some authority). His goals are nothing
more than to post arrogant, clueless rants thinking he's showing off.
this is why he ALWAYS cross posts to the same groups (Emacs, Python,,
Perl, etc.), even when the topic or content has nothing to do with
those things. He thinks people in these groups automatically respect
him, when most have killfiled him.
------------------------------
Date: Wed, 19 Aug 2009 11:19:38 -0700
From: "John W. Krahn" <someone@example.com>
Subject: Re: replace everything from the 6th character on with asterisks
Message-Id: <YmXim.146515$zq1.32881@newsfe22.iad>
jaredsubman@yahoo.com wrote:
> The code I have to do this so far is:
>
> #!/usr/bin/env perl
>
> use strict;
> use warnings;
>
> my $string = 'ABCDEFG8IJK2MNOPbRST7VW5YZ';
> print "$string\n";
> # grab first 5 characters
> my $match1=substr($string,0,5);
> # grab from the 6th character to the end of the string
> my $match2=substr($string,5);
> # replace all of the 2nd set of matched chars with asterisks
> $match2 =~ tr/[0-9][a-z][A-Z]/*/;
Repeated characters will be ignored so that would more simply be:
$match2 =~ tr/[]0-9a-zA-Z/*/;
Although I don't see any '[' or ']' characters in your string.
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Wed, 19 Aug 2009 13:21:11 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: replace everything from the 6th character on with asterisks
Message-Id: <slrnh8og3l.9o2.tadmc@tadmc30.sbcglobal.net>
jaredsubman@yahoo.com <jaredsubman@yahoo.com> wrote:
> $match2 =~ tr/[0-9][a-z][A-Z]/*/;
tr/// does not make use of regular expressions, so the metacharacters
in tr are different.
In particular, square brackets are not meta, so the above is equivalent to:
$match2 =~ tr/0-9a-zA-Z[]/*/;
but you probably were trying for one equivalent to:
$match2 =~ tr/0-9a-zA-Z/*/;
unless you actually wanted square brackets to be replaced with asterisks.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Wed, 19 Aug 2009 11:12:15 -0700
From: Nathan Keel <nat.k@gm.ml>
Subject: Re: revisiting web development in Perl...where to start?
Message-Id: <5gXim.133026$qx1.33966@newsfe04.iad>
Eli Morris-Heft wrote:
> On Aug 18, 5:15Â pm, Nathan Keel <na...@gm.ml> wrote:
>> Jamie wrote:
>> > I suspect most of the php coders out there have PHP as their first
>> > "language" and aren't programmers so much as web designers, they
>> > figure out how to do a couple things with it and walla, they jump
>> > into writing full-fledged php applications that aren't planned out.
>>
>> That's exactly what I've seen. Â Of course, none of us are claiming
>> there aren't skilled coders in PHP, but far more unskilled people
>> code in PHP than in Perl.
>
> Ack. A bit of a self-fulfilling prophecy there. While it's not
> guaranteed that most of the PHP coders out there have PHP as their
> first language, I'll be a lot of them do - which is why they code in
> PHP. From my professional experience, the closest most web designers
> get to a programming language is either HTML (and many don't learn
> that too well) or Flash (which isn't a programming language, though
> Actionscript is, and 3.0 is actually a fairly respectable one - did I
> write that?).
>
> Both PHP and Perl suffer from being languages that are easy to start
> learning, but difficult to build out in. They tend to breed
> overconfidence from novice programmers, as sometimes exhibited on this
> very newsgroup and its sister comp.lang.php. The fault, though, isn't
> in the languages. It's in the programmer who fails to design, fails to
> recognize limits, fails to ask before leaping. (And, really, which one
> of us hasn't been that programmer at one time or another?)
>
> From my experience, there's a lot of unskilled people out there coding
> in Perl too - it's just that their scripts stay in their home
> directories on their servers rather than being served for the whole
> world to judge.
>
> EMH, JAP{HP,erl}H
Perhaps, but when PHP scripts usually don't relate to needing to
understand outputting the right content type/headers or have specific
permissions to work, and can more easily have the user add code
directly into what they otherwise see as just an HTML document, they
tend to gravitate toward that and can get away with knowing less (from
their point of view) to get things to work. This often leads to other
problems, but certainly it exists in any language, including Perl. I
don't mind PHP that much, but it seems wonky compared to other
languages, it feels less serious and has a lot more bugs and security
issues than most others. One can attribute security findings to the
popularity of it, but that's bullshit when people say that (i.e., more
Windows exploits than Linux, but more web sites run on Linux, so that
doesn't hold true, unless you're talking about desktop related
exploits). But, the bugs, the bugs... Anyway, yeah, all languages
have their unskilled people and there were certainly a lot of what you
could call Perl scripts by Matt Wright that were floating around for
many years causing many people a lot of misery.
------------------------------
Date: Thu, 20 Aug 2009 14:11:27 +0200
From: Josef Moellers <josef.moellers@ts.fujitsu.com>
Subject: Re: search for hex characters in a binary file and remove them
Message-Id: <h6jeg8$urq$1@nntp.fujitsu-siemens.com>
venkateshwar D wrote:
> Hi All,
>
> I need to look for a sequence of hex characters in a binary file and
> remove them. the binary file has 00 00 02 02 01 00 sequence somewhere
> in the file.
> The script should open the file and look for this sequence 00 00 02 02
> 01 00 <18 variable bytes> and remove the 18 + 6 = 24 bytes from the
> file.can someone please help. I can open the binary file and buffer
> byte by byte but since the pattern can be anywhere in the file i dont
> know how to proceed
I've done this a couple of times in order to find some embedded files in
some documents (most often to find images in xls, doc, ppt, ...),
although I usually discard whatever is not of interest to me.
You have to read the file byte-by-byte and check for the header:
(Untested Code follows!)
my $special = pack('C*', 0x00, 0x00, 0x02, 0x02, 0x01, 0x00);
open(my $src, '<', $srcname) or die "$0: cannot open $srcname: $!\n";
open(my $dst, '>', $dstname) or die "$0: Cannot create $dstname: $!\n";
binmode $src;
my $buf;
read($src, $buf, length($special));
while (1) {
if ($buf eq $special) {
seek($src, 18, 0);
last if read($src, $buf, length($special)) != length($special);
next;
}
print $dst substr($buf, 1, 1);
substr($buf, 1, 1, '');
last if read($src, $buf, 1, -1) != 1;
}
print $dst $buf;
close($src);
close($dst);
HTH,
Josef
--
These are my personal views and not those of Fujitsu Technology Solutions!
Josef Möllers (Pinguinpfleger bei FTS)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://de.ts.fujitsu.com/imprint.html
------------------------------
Date: Thu, 20 Aug 2009 12:54:13 +0100
From: "John" <john1949@yahoo.com>
Subject: trapping errors using $!
Message-Id: <h6jdh2$2l5$1@news.albasani.net>
Hi
This part of code is in a web service so there is no output to screen.
I've turned off printing to standard error.
open STDERR,'>/dev/null';
....
read (STDIN,$request,$length);
if ($1 > 0) {$response=$error1};
Would the above condition trap any error?
Regards
John
------------------------------
Date: Thu, 20 Aug 2009 14:09:10 +0200
From: Peter Makholm <peter@makholm.net>
Subject: Re: trapping errors using $!
Message-Id: <87skfmu1p5.fsf@vps1.hacking.dk>
"John" <john1949@yahoo.com> writes:
> open STDERR,'>/dev/null';
>
> ....
> read (STDIN,$request,$length);
> if ($1 > 0) {$response=$error1};
I guess that you meant to use $! here?
> Would the above condition trap any error?
No, $! is at most true for the last system call you've made. So this
construct would only trap errors from you read call.
//Makholm
------------------------------
Date: Thu, 20 Aug 2009 13:59:21 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: trapping errors using $!
Message-Id: <N9qdnSs11fo31RDXnZ2dnUVZ8uGdnZ2d@brightview.co.uk>
John wrote:
> Hi
>
> This part of code is in a web service so there is no output to screen.
> I've turned off printing to standard error.
>
> open STDERR,'>/dev/null';
Why not send it somewhere else, either a file
or a RAM file?
BugBear
------------------------------
Date: 19 Aug 2009 20:25:50 GMT
From: Glenn Jackman <glennj@ncf.ca>
Subject: Re: windows one liner to output unix line feed
Message-Id: <slrnh8onuf.eta.glennj@smeagol.ncf.ca>
At 2009-08-19 01:28PM, "boman" wrote:
> I have a simple one liner running on Windows that does a substitution.
> However, with the -p option, the line endings are coming out \r\n, and
> I need them to be just \n.
>
> perl -pi.bak -e "s|foo|bar|g" myfile.txt
perhaps you need to chomp the windows line ending, and add the unix line
ending manually:
perl -pi.bak -e "s|foo|bar|g; chomp; print qq{$_\n}" myfile.txt
--
Glenn Jackman
Write a wise saying and your name will live forever. -- Anonymous
------------------------------
Date: 19 Aug 2009 20:28:23 GMT
From: Glenn Jackman <glennj@ncf.ca>
Subject: Re: windows one liner to output unix line feed
Message-Id: <slrnh8oo39.eta.glennj@smeagol.ncf.ca>
At 2009-08-19 04:25PM, "Glenn Jackman" wrote:
> At 2009-08-19 01:28PM, "boman" wrote:
> > I have a simple one liner running on Windows that does a substitution.
> > However, with the -p option, the line endings are coming out \r\n, and
> > I need them to be just \n.
> >
> > perl -pi.bak -e "s|foo|bar|g" myfile.txt
>
> perhaps you need to chomp the windows line ending, and add the unix line
> ending manually:
>
> perl -pi.bak -e "s|foo|bar|g; chomp; print qq{$_\n}" myfile.txt
oops, should be -n, not -p
--
Glenn Jackman
Write a wise saying and your name will live forever. -- Anonymous
------------------------------
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 2562
***************************************
