[23192] in Perl-Users-Digest
Perl-Users Digest, Issue: 5413 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Aug 23 03:05:53 2003
Date: Sat, 23 Aug 2003 00:05: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 Sat, 23 Aug 2003 Volume: 10 Number: 5413
Today's topics:
Re: Commonly used modules (Tad McClellan)
Re: Image::Magick jpeg compression <mgjv@tradingpost.com.au>
Re: imagemagick composite problem <mgjv@tradingpost.com.au>
Re: operator in a variable? <jwillmore@cyberia.com>
Re: Problem with split function <tzz@lifelogs.com>
Re: Problem with split function (Tad McClellan)
Re: Pure Perl SQL server <tzz@lifelogs.com>
root wants to use perldoc <jidanni@jidanni.org>
Re: root wants to use perldoc (Sam Holden)
Re: What ever happened to comp.lang.perl ? (Jon Bell)
Re: What ever happened to comp.lang.perl ? <luriel@gfy.yahoo.com>
Re: What ever happened to comp.lang.perl ? <luriel@gfy.yahoo.com>
Re: What ever happened to comp.lang.perl ? <luriel@gfy.yahoo.com>
Re: What ever happened to comp.lang.perl ? (Sam Holden)
Re: What ever happened to comp.lang.perl ? (Tad McClellan)
Re: What ever happened to comp.lang.perl ? <uri@stemsystems.com>
Re: What ever happened to comp.lang.perl ? (Jon Bell)
Re: What ever happened to comp.lang.perl ? <tim@vegeta.ath.cx>
Re: What ever happened to comp.lang.perl ? <tim@vegeta.ath.cx>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 23 Aug 2003 00:32:21 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Commonly used modules
Message-Id: <slrnbkdv35.212.tadmc@magna.augustmail.com>
Jon <jonov@iprimus.com.au> wrote:
> I'm curious to know what CPAN modules people use in their general day-to-day
> perl scripting (or can't live without).
LWP rocks!
I have many agents/scrapers that bounce around the web and
collect "interesting" stuff for me.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 23 Aug 2003 15:29:13 +1000
From: Martien Verbruggen <mgjv@tradingpost.com.au>
Subject: Re: Image::Magick jpeg compression
Message-Id: <slrnbkdut9.ilo.mgjv@martien.heliotrope.home>
On Thu, 21 Aug 2003 21:35:51 GMT,
Jay Tilton <tiltonj@erols.com> wrote:
> "Andrew Harton" <andrew_harton@agilent.com> wrote:
>: Basically, I'm trying to read a source image, resize to 400x300 and
>: write that, then resize to 100x75 and then write that. I notice that
>: the typical filesize I get for the 400x300 image is between 50-60k,
>: however the filesize for the thumbnail is roughly 25k. Using
>: Paintshop Pro I can produce compressed images of around 5k.
> I recall seeing what you describe with a thumbnail generator of my
> own. The files shrank dramatically when I inserted a call to the
> Profile() method, which removed a huge chunk of data that was being
> carried forward from the full-size image to the thumbnail.
>
> $magick->Read( $ifile );
> $magick->Profile();
It's probably clearer to use Strip() when your intention is stripping
the image of its profiling information. Strip() also removes comments
and such, so if you want to retain those, using Profile() is the right
thing to do.
The identify tool that comes with the ImageMagick distribution can tell
you whether your original image has a profile, and how large it is.
It is also probably not a bad idea to make sure that you adjust the
image compression quality to something lower, or at least check that
it's low enough. Thumbnails generally can get away with low quality
compression.
> I'm not sure anymore what an "ICC or IPTC image profile" is or why it
> has to be removed manually, but it made sense back when I wrote the
> program.
Image::Magick tends to carry all information in an image forward, if
possible, even non-visible information. The Strip() method is there to
get rid of all non-visible data.
\begin{offtopic}
ICC and IPTC are just some standardised ways for adding extra
information to images.
ICC = International Color Consortium color profile
IPTC = IPTC Newsphoto profile (www.iptc.org)
This is not the only profile information that ImageMagick can carry
around in an image (and besides profile information, there is other
stuff as well), but I think that JPEG only has these two as
possibilities, but I could be wrong.
\end{offtopic}
Martien
--
|
Martien Verbruggen | Useful Statistic: 75% of the people make up
| 3/4 of the population.
|
------------------------------
Date: Sat, 23 Aug 2003 15:15:06 +1000
From: Martien Verbruggen <mgjv@tradingpost.com.au>
Subject: Re: imagemagick composite problem
Message-Id: <slrnbkdu2q.ilo.mgjv@martien.heliotrope.home>
On Fri, 22 Aug 2003 11:36:17 +0200,
Lam <lam-no-spamm-thanks@nospam.org> wrote:
> Martien Verbruggen <mgjv@tradingpost.com.au> writes:
[solution to earlier question removed]
> but i have another problem :
>
> i must create a result image Y (geometry 230x150)
> in this image, a can insert an image X, with geometry (x,y)
> if X is smaller than the result image i would like to compose the rest
> (Y - X) with background black
Create a black image (xc:black) of geometry 230x150, combine the new
image with that image, probably using "Over". Pretty much what you were
doing in the code you showed before.
> i see the function Montage, but i can't make what i want :(
I don't think Montage is what you want.
Martien
--
|
Martien Verbruggen | System Administration is a dirty job, but
| someone said I had to do it.
|
------------------------------
Date: Sat, 23 Aug 2003 06:38:15 GMT
From: James Willmore <jwillmore@cyberia.com>
Subject: Re: operator in a variable?
Message-Id: <20030823023754.21f20e47.jwillmore@cyberia.com>
On Fri, 22 Aug 2003 13:46:00 -0500
tadmc@augustmail.com (Tad McClellan) wrote:
> For those of you following along at home, you should note that
> what is being discussed here is the "eval EXPR" form.
>
> "eval BLOCK" is not evil.
We now return to ... "The Eval Perl Programmers Do" ... already in
progress.
--
Jim
------------------------------
Date: Sat, 23 Aug 2003 00:10:28 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Problem with split function
Message-Id: <4n7k55qaiz.fsf@lockgroove.bwh.harvard.edu>
On 22 Aug 2003, altalingua@hotmail.com wrote:
> I am having a problem with the split function.
> Here is my code:
>
>$_ = "123 a 456 b 789 c";
> my @words = split /[^a-z]+/, $_;
> print $words[0], $words[1], $words[2];
>
> I want the output to be: abc
> However, the actual output of this code is: ab
> ($words[0] is equal to "" not "a").
>
> What am I doing wrong? Why isn't the output abc?
See "perldoc -f split" - you have an empty leading field which went
into $words[0], and 'c' is in $words[3].
Ted
------------------------------
Date: Sat, 23 Aug 2003 00:40:52 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Problem with split function
Message-Id: <slrnbkdvj4.212.tadmc@magna.augustmail.com>
David Morel <altalingua@hotmail.com> wrote:
> I am having a problem with the split function.
Others have already helped with that, I'll jump in to point out
that split() may not be the best tool for your task.
> $_ = "123 a 456 b 789 c";
> my @words = split /[^a-z]+/, $_;
You should use split() when you want to specify what to throw away,
and use m//g when you want to specify what to keep.
Discarding non-letters (split) can be inverted into matching letters (m//g):
my @words = /([a-z]+)/g;
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 23 Aug 2003 00:17:22 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Pure Perl SQL server
Message-Id: <4n3cftqa7h.fsf@lockgroove.bwh.harvard.edu>
On Sat, 23 Aug 2003, newsfeed@boog.co.uk wrote:
> By "SQL server", I mean replicating something like MySQL entirely in
> Perl. So, yeah, you'd create a DBD, and use DBI, as you would with
> anything else, but the actual database /backend/ (like your MySQL,
> Oracle, etc) would be Perl code.. and it wouldn't be CSV, or in
> RAM.. but fast binary files.
That's an interesting idea, but a RDBMS is a very difficult piece of
software to write correctly. I haven't heard about something written
in Perl. I would love to see one, though.
Ted
------------------------------
Date: Sat, 23 Aug 2003 14:04:57 +0800
From: Dan Jacobson <jidanni@jidanni.org>
Subject: root wants to use perldoc
Message-Id: <87zni09aeu.fsf@jidanni.org>
# perldoc -f my
Superuser must not run /usr/bin/perldoc without security audit and taint checks.
Gee whiz, what if man(1) did that too? grep, ls?
Can't perldoc be made safe? Why can't it just call itself again, this
time as user 'nobody' or something.
The point is I only have a limited set of windows and don't want to
open another. Or I'm working on the single console and just want to
check a quick doc. Anyway, I don't want to have to check my id before
I say perldoc.
What do I have to do? Make a ~root/bin/perldoc:
su -c "/usr/bin/perldoc $@" nobody #untested
Ugh.
------------------------------
Date: 23 Aug 2003 06:52:31 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: root wants to use perldoc
Message-Id: <slrnbke3pf.247.sholden@flexal.cs.usyd.edu.au>
On Sat, 23 Aug 2003 14:04:57 +0800, Dan Jacobson <jidanni@jidanni.org> wrote:
> # perldoc -f my
> Superuser must not run /usr/bin/perldoc without security audit and taint checks.
>
> Gee whiz, what if man(1) did that too? grep, ls?
> Can't perldoc be made safe? Why can't it just call itself again, this
> time as user 'nobody' or something.
>
> The point is I only have a limited set of windows and don't want to
> open another. Or I'm working on the single console and just want to
> check a quick doc. Anyway, I don't want to have to check my id before
> I say perldoc.
>
> What do I have to do? Make a ~root/bin/perldoc:
> su -c "/usr/bin/perldoc $@" nobody #untested
> Ugh.
You RTFM. "man perldoc"
Paying particular attention to the "-U" option
--
Sam Holden
------------------------------
Date: Sat, 23 Aug 2003 04:30:45 GMT
From: jtbellq2f@presby.edu (Jon Bell)
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <HK21v9.CLu@presby.edu>
In article <PAy1b.4299$iW6.682@newssvr27.news.prodigy.com>,
Luriel <luriel@gfy.yahoo.com> wrote:
>Alan J. Flavell wrote:
>> On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
>[....]
>>> It isn't much of a stretch for me to understand why new programmers
>>> trying to get their scripts to run in Apache (simply as an example
>>> that occurs quite frequently), would think it perfectly reasonable
>>> to post to comp.lang.perl.misc to ask other Perl programmers what
>>> the problem might be (without expecting to be flamed). One would
>>> assume that Perl programmers would probably be familiar with
>>> setting up the environment in which to run their scripts, and be
>>> willing to help.
>>
>> That's where you'd be dead wrong, for many of the serious users of
>> Perl here. (Myself, for one, excluded... but then, maybe I'm not
>> serious enough... ;-)
>
>And you can speak for each_and_every person in this group? Do you really
>think no "serious" programmer would use it on a www platform???
No, Alan is alluding to the fact that many serious Perl programmers don't
do CGI scripts. Perl existed for many years, and had a strong following,
even before it became popular for CGI scripts. I've been using Perl
extensively for about ten years, but wrote my first CGI script only
about a year and a half ago.
--
Jon Bell <jbell@presby.edu> Presbyterian College
Dept. of Physics and Computer Science Clinton, South Carolina USA
------------------------------
Date: Sat, 23 Aug 2003 04:26:20 GMT
From: "Luriel" <luriel@gfy.yahoo.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <M1C1b.586$oK1.3878146@newssvr14.news.prodigy.com>
Gunnar Hjalmarsson wrote:
> Luriel wrote:
>> No offense instended Flavell, but I think on this note is "where
>> you'd be dead wrong".
>
> Hey, relax, Luriel! There was some irony in Alan's post which I
> thought was obvious. Seems as if it wasn't that obvious, after all.
> ;-)
Point well taken ;p
I don't mean to get so worked up over such things.
Sorry about that ;p
------------------------------
Date: Sat, 23 Aug 2003 04:38:04 GMT
From: "Luriel" <luriel@gfy.yahoo.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <McC1b.587$fS1.4362277@newssvr14.news.prodigy.com>
Jürgen Exner wrote:
> Matt Garrish wrote:
>> "Rafael Garcia-Suarez" <rgarciasuarez@free.fr> wrote in message
>> news:slrnbkcsrc.gn1.rgarciasuarez@dat.local...
>> It isn't much of a stretch for me to understand why new programmers
>> trying to get their scripts to run in Apache (simply as an example
>> that occurs quite frequently), would think it perfectly reasonable to
>> post to comp.lang.perl.misc to ask other Perl programmers what the
>> problem might be (without expecting to be flamed).
>
> Except that Apache and Perl have pretty much nothing to do with each
> other?
Ever heard of mod_perl? Apache is only one of the largest (web orientated)
platforms where Perl is used! As has been said already, virually any *NIX
distro for the past many years has been coming pre packaged with Apache and
Perl, and in more times then not Perl is already setup to run on it.
Face it, CGI is a huge use of Perl and has been for quite some time. Yes
thye have their own territories but thye also have many overlapping
properties.
>> One would assume
>> that Perl programmers would probably be familiar with setting up the
>> environment in which to run their scripts, and be willing to help.
>
> Certainly. Just set your path to perl (or perl.exe on Windows) and
> off you go.
For that matter there is and has been Win32 versions of Apache too ;p
> What does that have to do with Apache? I'm writing Perl programs on
> and off for the last 10 years or so. I've never used Apache or any
> other web server for that matter.
I've written many web based server management scripts in Perl that run on a
ww server (Apache in my case.) Hell, WEBMIN is written entirely in Perl!
Ok, it doesn't *directly* have anything to do with Apache, but Apache can,
at the same time, be considered a tool to augment Perl.
------------------------------
Date: Sat, 23 Aug 2003 04:43:13 GMT
From: "Luriel" <luriel@gfy.yahoo.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <BhC1b.588$ZK1.3915996@newssvr14.news.prodigy.com>
Jon Bell wrote:
> In article <PAy1b.4299$iW6.682@newssvr27.news.prodigy.com>,
> Luriel <luriel@gfy.yahoo.com> wrote:
>> Alan J. Flavell wrote:
>>> On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
>> [....]
>>>> It isn't much of a stretch for me to understand why new programmers
>>>> trying to get their scripts to run in Apache (simply as an example
>>>> that occurs quite frequently), would think it perfectly reasonable
>>>> to post to comp.lang.perl.misc to ask other Perl programmers what
>>>> the problem might be (without expecting to be flamed). One would
>>>> assume that Perl programmers would probably be familiar with
>>>> setting up the environment in which to run their scripts, and be
>>>> willing to help.
>>>
>>> That's where you'd be dead wrong, for many of the serious users of
>>> Perl here. (Myself, for one, excluded... but then, maybe I'm not
>>> serious enough... ;-)
>>
>> And you can speak for each_and_every person in this group? Do you
>> really think no "serious" programmer would use it on a www
>> platform???
>
> No, Alan is alluding to the fact that many serious Perl programmers
> don't do CGI scripts. Perl existed for many years, and had a strong
> following, even before it became popular for CGI scripts. I've been
> using Perl extensively for about ten years, but wrote my first CGI
> script only about a year and a half ago.
WEll, the notion that "serious Perl programmers don't do CGI scripts" is
just plain wrong. Hell, what are cgi script but shell based scripts that
send output to the browser instead of a tty.
I'm sorry, but you can only speak_for_thy_self. I've been at it for nearly a
decade as well, and a lot of that time was spent writing both shell based
and web based scripts. Both have their place. Why is this so hard to
swallow?
------------------------------
Date: 23 Aug 2003 04:59:10 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <slrnbkdt4u.of.sholden@flexal.cs.usyd.edu.au>
On Sat, 23 Aug 2003 04:38:04 GMT, Luriel <luriel@gfy.yahoo.com> wrote:
> Jürgen Exner wrote:
>> Matt Garrish wrote:
>>> "Rafael Garcia-Suarez" <rgarciasuarez@free.fr> wrote in message
>>> news:slrnbkcsrc.gn1.rgarciasuarez@dat.local...
>
>>> One would assume
>>> that Perl programmers would probably be familiar with setting up the
>>> environment in which to run their scripts, and be willing to help.
>>
>> Certainly. Just set your path to perl (or perl.exe on Windows) and
>> off you go.
>
> For that matter there is and has been Win32 versions of Apache too ;p
>
>> What does that have to do with Apache? I'm writing Perl programs on
>> and off for the last 10 years or so. I've never used Apache or any
>> other web server for that matter.
>
> I've written many web based server management scripts in Perl that run on a
> ww server (Apache in my case.) Hell, WEBMIN is written entirely in Perl!
>
> Ok, it doesn't *directly* have anything to do with Apache, but Apache can,
> at the same time, be considered a tool to augment Perl.
I use perl with Solaris. So I should ask all my questions about configuring
Solaris here? It's a tool to augment Perl after all.
I edit my perl scripts in vi. Should I ask here for help on vi commands?
--
Sam Holden
------------------------------
Date: Sat, 23 Aug 2003 00:30:19 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <slrnbkduvb.212.tadmc@magna.augustmail.com>
Sam Holden <sholden@flexal.cs.usyd.edu.au> wrote:
> Should I ask here for help on vi commands?
How do I get this durn thing out of "beep mode"?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 23 Aug 2003 05:51:16 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <x7d6eworaj.fsf@mail.sysarch.com>
>>>>> "TM" == Tad McClellan <tadmc@augustmail.com> writes:
TM> Sam Holden <sholden@flexal.cs.usyd.edu.au> wrote:
>> Should I ask here for help on vi commands?
TM> How do I get this durn thing out of "beep mode"?
use Emacs ;
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Sat, 23 Aug 2003 06:36:28 GMT
From: jtbellq2f@presby.edu (Jon Bell)
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <HK27os.JF5@presby.edu>
In article <BhC1b.588$ZK1.3915996@newssvr14.news.prodigy.com>,
Luriel <luriel@gfy.yahoo.com> wrote:
>Jon Bell wrote:
>> In article <PAy1b.4299$iW6.682@newssvr27.news.prodigy.com>,
>> Luriel <luriel@gfy.yahoo.com> wrote:
>>> Alan J. Flavell wrote:
>>>> On Fri, Aug 22, Matt Garrish inscribed on the eternal scroll:
>>>>> [...] One would
>>>>> assume that Perl programmers would probably be familiar with
>>>>> setting up the environment in which to run their scripts, and be
>>>>> willing to help.
[Matt was referring specifically to Apache/CGI here]
>>>>
>>>> That's where you'd be dead wrong, for many of the serious users of
>>>> Perl here.
>>>
>>> And you can speak for each_and_every person in this group? Do you
>>> really think no "serious" programmer would use it on a www
>>> platform???
>>
>> No, Alan is alluding to the fact that many serious Perl programmers
>> don't do CGI scripts. Perl existed for many years, and had a strong
>> following, even before it became popular for CGI scripts.
>
>WEll, the notion that "serious Perl programmers don't do CGI scripts" is
>just plain wrong.
He didn't say that. He (and many of the rest of us) are saying that
*many* serious Perl programmers don't do CGI scripts. It's not that we
don't feel Perl is suitable for CGI scripts, it's just that we don't do
CGI scripts. It isn't our field. The field of Perl programming is much
bigger than just CGI scripts.
And many of the problems that face CGI programmers who use Perl don't
depend on the fact that they're using Perl, but instead on server
configuration, understanding the CGI protocol, etc. People who write CGI
programs in C or C++ or other languages have those problems, too. That's
why there's a group for CGI programming that isn't tied to a specific
language. People who write CGI programs can help each other out there,
with problems that don't depend on the language they're using.
--
Jon Bell <jtbellap8@presby.edu> Presbyterian College
Dept. of Physics and Computer Science Clinton, South Carolina USA
------------------------------
Date: 23 Aug 2003 00:00:25 -0700
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <slrnbke49d.66a.tim@vegeta.ath.cx>
Luriel graced us by uttering:
> WEll, the notion that "serious Perl programmers don't do CGI
> scripts" is just plain wrong.
I agree, but I never saw that in the thread. In fact, Randal
wrote several CGI-related articles last year... :)
> Hell, what are cgi script but shell based scripts that send
> output to the browser instead of a tty.
You're partly right, but I have half a dozen shell scripts in my
crontab that never write to a tty. And whether they're
shell-based, Perl-based, C-based, or COBOL-based doesn't matter,
so long as they stick to CGI protocol:
The information pathways for CGI are: process environment, stdin,
stdout, and stderr. POST data is sent through stdin; GET data is
sent through environment variables; output is written to stdout;
and errors can be sent to stderr.
There can be a tty attached to any, all, or none of those three
filehandles, but that usually only happens in debug mode if at
all; I can't think of a case where an http server would use a tty
to communicate with a child CGI process.
Tim Hammerquist
--
Almost every culture in the world is more polite than global geek culture.
-- Ethan Zuckerman, "Linux Journal" Issue 111
------------------------------
Date: 23 Aug 2003 00:03:41 -0700
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: What ever happened to comp.lang.perl ?
Message-Id: <slrnbke4fh.66a.tim@vegeta.ath.cx>
Tad McClellan graced us by uttering:
> Sam Holden <sholden@flexal.cs.usyd.edu.au> wrote:
> > Should I ask here for help on vi commands?
>
> How do I get this durn thing out of "beep mode"?
<Esc>:help
:)
Tim Hammerquist
--
When the gods wish to punish us, they answer our prayers.
-- Oscar Wilde, "An Ideal Husband"
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 V10 Issue 5413
***************************************
