[23749] in Perl-Users-Digest
Perl-Users Digest, Issue: 5953 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Dec 18 14:10:39 2003
Date: Thu, 18 Dec 2003 11:10:15 -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 Thu, 18 Dec 2003 Volume: 10 Number: 5953
Today's topics:
Re: Please critique this short script that scans a log <dwall@fastmail.fm>
Re: Please critique this short script that scans a log <perl@my-header.org>
Re: Please critique this short script that scans a log <nobull@mail.com>
Re: Please critique this short script that scans a log <uri@stemsystems.com>
Re: Please critique this short script that scans a log <perl@my-header.org>
Problems reading in "£" character from a file <stephen.adaam@ntlworld.com>
Re: Q about a module containing more than one class <bik.mido@tiscalinet.it>
Re: Q about a module containing more than one class <xxala_qumsiehxx@xxyahooxx.com>
Re: recursive closures? <lmai@mytum.de>
Reg hashes (sunil)
Re: Reg hashes <nobull@mail.com>
Re: RegExp check for nothing or pattern (Tad McClellan)
Re: RegExp check for nothing or pattern <abigail@abigail.nl>
Re: RegExp check for nothing or pattern <Eric@nowhere.com>
Signaling another machine (Palaniappan)
Re: Signaling another machine (Anno Siegel)
Re: Signaling another machine <uri@stemsystems.com>
Re: Signaling another machine <troc@pobox.com>
Re: Simple text file operation (Tad McClellan)
Re: Simple text file operation (logic1)
Re: Simple text file operation <1usa@llenroc.ude>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 18 Dec 2003 16:35:22 -0000
From: "David K. Wall" <dwall@fastmail.fm>
Subject: Re: Please critique this short script that scans a log file
Message-Id: <Xns945575E5361F6dkwwashere@216.168.3.30>
Uri Guttman <uri@stemsystems.com> wrote:
> and depending on the actual file format and its size, slurping it
> and matching/grabbing against the whole file can be the fastest
> approach. see my recent article on slurping on perl.com or read it
> inside the File::Slurp distribution (which is updated).
[On "the opposite of slurping"]
"Slurping" and "burping" remind me of BLoop and FLoop from Hofstadter's
G-E-B. "Spewing" doesn't have the advantage of rhyming, but it does
sound faster and greater in volume than "burp". Being a slang term for
vomiting helps "spew" be a better antonym for "slurp", although it's
mildly disgusting. I like it. :-)
--
David Wall
------------------------------
Date: Thu, 18 Dec 2003 18:38:19 +0100
From: Matija Papec <perl@my-header.org>
Subject: Re: Please critique this short script that scans a log file
Message-Id: <g0o3uvsomv851m7b8lv7ao8fqbn41cg452@4ax.com>
X-Ftn-To: Uri Guttman
Uri Guttman <uri@stemsystems.com> wrote:
> if( /bar/ ) {
> process bar line ;
> next ;
> }
>
>this is clean looking (no if/else tree) and still efficient (no testing
>all possible line types each time around).
On the other hand you can't use "next" outside of loops, but in appearance
it comes closer to standard switch thinking, so to preserve consistency,
for ($scalar) {
next if /foobar/;
next if ..
}
Btw, where do you use elsif's or you're generally avoiding its use?
--
Matija
------------------------------
Date: 18 Dec 2003 17:50:15 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Please critique this short script that scans a log file
Message-Id: <u98yla10dk.fsf@wcl-l.bham.ac.uk>
J.W. <jwngaa@att.net> writes:
> On 17 Dec 2003 18:18:14 +0000, Brian McCauley <nobull@mail.com> wrote:
>
> >J.W. <jwngaa@att.net> writes:
> >> $regex_ctime = qr/ (Sun|Mon|Tue|Wed|Thu|Fri|Sat)
> >> (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) ([ |0-3][0-9])
> >> ([0-2][0-9]):([0-5][0-9]):([0-5][0-9]) ([0-9][0-9][0-9][0-9])/o;
>
> >Never use the /o regex qualifier without understanding it. Since /o
> >does nothing in the line above I can reasonably assume you don't
> >understand it. :-)
>
> I read that the "/o" means compile-once.
It does.
> Since there was nothing "dynamic" about the regex and the regex is
> never redefined, it seemed like the "/o" was a good idea.
Since there was nothing dynamic there's no reason why perl would even
consider recompiling the regex and hense /o has no effect at all.
Getting into the habit of always putting /o in the 99% of situations
where has no effect is not only a waste of a keystroke but more
importantly means that it'll become a reflex and sooner or latter
you'll start putting in places where it has an unwanted effect.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Thu, 18 Dec 2003 18:04:59 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Please critique this short script that scans a log file
Message-Id: <x7iskec88p.fsf@mail.sysarch.com>
>>>>> "MP" == Matija Papec <perl@my-header.org> writes:
> Btw, where do you use elsif's or you're generally avoiding its use?
i used one the other day. it was not a loop and it was handling one of 3
mutually exclusive options where at least one was required. so that was
an if/elsif/else cascade. but i love return/next/last for flow control
and with statement modifiers too. the goal with this style is to reduce
the bracket count and indent levels. it makes for fewer lines of code
and less visual clutter. now it is important to know when it is going
too far so this is not a fast and absolute rule.
in over 8000 lines of stem code i have 15 elsif's. so it isn't something
i need to use often. long cascaded if/else/elsif's are a poor coding
construct IMO. there are usually better ways to do it.
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: Thu, 18 Dec 2003 20:03:36 +0100
From: Matija Papec <perl@my-header.org>
Subject: Re: Please critique this short script that scans a log file
Message-Id: <ecu3uv8r2j7jk9errukeqqvd7f7p49lih9@4ax.com>
X-Ftn-To: Uri Guttman
Uri Guttman <uri@stemsystems.com> wrote:
>>>>>> "MP" == Matija Papec <perl@my-header.org> writes:
>
> > Btw, where do you use elsif's or you're generally avoiding its use?
>
>i used one the other day. it was not a loop and it was handling one of 3
>mutually exclusive options where at least one was required. so that was
>an if/elsif/else cascade. but i love return/next/last for flow control
>and with statement modifiers too. the goal with this style is to reduce
>the bracket count and indent levels. it makes for fewer lines of code
>and less visual clutter. now it is important to know when it is going
I guess this partly depends on personal style, more important is that elsif
is shorter (this also reads "cleaner" if it isn't obfuscation) as you only
need "els" in front of "if" and with if/next you'll need "next;\n", which is
also an additional command while "elsif" isn't.
== if/next ==
if () {
..
next;
}
if () {
..
next;
}
..
next;
== if/elsif ==
if () {
..
}
elsif () {
..
}
else {
..
}
>in over 8000 lines of stem code i have 15 elsif's. so it isn't something
>i need to use often. long cascaded if/else/elsif's are a poor coding
>construct IMO. there are usually better ways to do it.
I did some reading on it, can it be used for automating tasks on remote
computers?(sorry if you already covered this in the docs)
--
Matija
------------------------------
Date: Thu, 18 Dec 2003 14:54:10 -0000
From: "Stephen Adam" <stephen.adaam@ntlworld.com>
Subject: Problems reading in "£" character from a file
Message-Id: <mcjEb.206$3L5.181@newsfep3-gui.server.ntli.net>
Hi there,
I'm having problems when reading in the "£" character from a file, they all
get converted into u's with an accent (?). Can anyone tell me why this is
happening and how to avoid it, its got me very confused.
Just run this program and make sure you place a file the same directory
called test.txt with some pound signs (£) in it, they keep getting
mytseriously turned into accented u's.
Thanks
Steve
PS - I'm running Perl on a Windows XP platform if thats any help.
#!C:/Perl/bin/perl.exe -w
# This program will read a file in the same directory called test.txt into
the "$whole" variable and
# then print it out
use strict;
&Datain();
exit(0);
sub Datain(){
our $FILEHANDLE = "./test.txt";
my $whole;
open("FILEHANDLE") or
die ("Unable to open file $FILEHANDLE\n Program Quiting\n");
while(my $line = <FILEHANDLE>){
chomp $line; # Get rid of new line char
$line .=" "; # Put blank space instead
$line =~ tr/[A-Z]/[a-z]/; # Put line variable into lowercase
$whole .= $line;
}
print "$whole";
}
------------------------------
Date: Fri, 19 Dec 2003 19:28:41 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Q about a module containing more than one class
Message-Id: <1mg6uv8d99jbbug3frh51l5r821c8cfnkk@4ax.com>
On Wed, 17 Dec 2003 18:01:37 GMT, "Ala Qumsieh"
<xxala_qumsiehxx@xxyahooxx.com> wrote:
>> Now I want to put all these classes in the same (separate) module so
^^^^
>> that only the "main" one is made (explicitly) available to the final
>I guess different people would do it differently. I would make is such that
>each module is in a separate file, and would name them such that each '::'
>$SOME_PATH/cool/module/foo.pm:
>$SOME_PATH/cool/module.pm:
>That will make it easier if you want to use cool::module::foo in some other
>class as well.
This is *not* what I want because I do *not* want to use
cool::module::foo in other classes.
It wouldn't be a *problem* to do it the way you suggest anyway, but I
*prefer* to hide (for this very weak meaning of "hide")
cool::module::foo in $SOME_PATH/cool/module.pm.
Michele
--
# This prints: Just another Perl hacker,
seek DATA,15,0 and print q... <DATA>;
__END__
------------------------------
Date: Thu, 18 Dec 2003 18:53:06 GMT
From: "Ala Qumsieh" <xxala_qumsiehxx@xxyahooxx.com>
Subject: Re: Q about a module containing more than one class
Message-Id: <lImEb.72641$hF4.42990@newssvr25.news.prodigy.com>
"Michele Dondi" <bik.mido@tiscalinet.it> wrote in message
news:1mg6uv8d99jbbug3frh51l5r821c8cfnkk@4ax.com...
> This is *not* what I want because I do *not* want to use
> cool::module::foo in other classes.
Ahh .. I misunderstood your question.
> It wouldn't be a *problem* to do it the way you suggest anyway, but I
> *prefer* to hide (for this very weak meaning of "hide")
> cool::module::foo in $SOME_PATH/cool/module.pm.
Since your foo module is exclusive for cool::module, I would stick with the
cool::module:: hierarchy. For me, this would make it clear that the two
modules are related, and it avoids polluting other namespaces as well.
--Ala
------------------------------
Date: Thu, 18 Dec 2003 15:34:48 +0000 (UTC)
From: Lukas Mai <lmai@mytum.de>
Subject: Re: recursive closures?
Message-Id: <brsheo$1cfl$1@sunsystem5.informatik.tu-muenchen.de>
Uri Guttman <uri@stemsystems.com> wrote:
>>>>>> "LM" == Lukas Mai <lmai@mytum.de> writes:
> > It's destroyed during global destruction, not upon exiting scope.
> interesting. and if you do assign something else to $fib DESTROY is
> called immediately.
Yes, because:
# (N) means a reference count of N
{
my $fib; # fib --> (1) undef
sub{... $fib ...} # fib --> (2) undef <-- (0) SUB
$fib = <---^ # fib --> (2) REF --> (1) SUB
# ^ |
# \-----------/
Now when exiting the scope, what's left is
(1) REF --> (1) SUB
^ |
\-----------/
i.e. a reference cycle.
But when assigning "foo" to $fib, we get
fib --> (2) "foo" (0) SUB
^ |
\-----------/
and then
fib --> (1) "foo".
At least I think that's what's happening here.
Lukas
------------------------------
Date: 18 Dec 2003 09:51:46 -0800
From: sunilsreenivas2001@yahoo.com (sunil)
Subject: Reg hashes
Message-Id: <d924fa71.0312180951.443abeb5@posting.google.com>
Hi!
I have two simple questions. I am using PERL version 5.005 and
hence I should be able to preallocate hashes using something like:
keys(%myhash)=50000. But is there any way to verify this? When I do
scalar(keys%myhash), it shows 0.
Second question is about collisions when using hashes. I am assuming
that perl takes care of collisions so that if two keys happen to map
to same bucket, the new element will be placed either in linked list
or at next available slot in hash bucket array. But do hash functions
take care of this? For example if I call exists ($myhash{"hello"}) and
lets assume hash has key called "hallo" but not "hello". If both keys
"hallo" and "hello" map to same hash index,does
exists($myhash("hello")) return 0 as we expect?
Thanks,
Sunil.
------------------------------
Date: 18 Dec 2003 18:21:29 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Reg hashes
Message-Id: <u94qvy0yxi.fsf@wcl-l.bham.ac.uk>
sunilsreenivas2001@yahoo.com (sunil) writes:
> I have two simple questions. I am using PERL version 5.005
> and hence I should...
... upgrade.
> ... be able to preallocate hashes using something like:
> keys(%myhash)=50000. But is there any way to verify this? When I do
> scalar(keys%myhash), it shows 0.
That is correct. scalar(keys(%myhash)) returns the number of keys not the
number of buckets.
scalar(%myhash) will return the bucket usage - but not if the hash is
empty. If the hash is empty then it returns '0' so that it is false
in a boolean context.
keys(%myhash) = 50000;
$myhash{dummy} = undef;
print scalar %myhash; # prints "1/65536"
This shows that %myhash is using 1/65536 buckets. (The number of
buckets is always a power of 2 AFAIK).
> Second question is about collisions when using hashes. I am assuming
> that perl takes care of collisions so that if two keys happen to map
> to same bucket, the new element will be placed either in linked list
> or at next available slot in hash bucket array.
Yes, of course.
> But do hash functions take care of this?
Yes, of course.
> For example if I call exists ($myhash{"hello"}) and
> lets assume hash has key called "hallo" but not "hello". If both keys
> "hallo" and "hello" map to same hash index,does
> exists($myhash("hello")) return 0 as we expect?
Yes, of course.
Just think Perl "hashes" as un-ordered associative arrays - don't
think about how they are implemented unless you really need to. It
is, I think, widely accepted that the choice of name "hash" for Perl's
associative array data type was bad because it causes people to think
about the implementation when really they shouldn't.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Thu, 18 Dec 2003 07:55:41 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: RegExp check for nothing or pattern
Message-Id: <slrnbu3cet.jc8.tadmc@magna.augustmail.com>
Eric <Eric@nowhere.com> wrote:
>>
>> I posted my answer to your other post entitled: "RegExp to match pattern
> or
>> BLANK?"
>>
>> Why did you post the same question twice with two different subject lines?
>>
>
> For the sole purpose of annoying you.
(and *thousands* of people around the world. Your selfishness is astounding)
Goodbye troll.
*plonk*
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 18 Dec 2003 17:30:50 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: RegExp check for nothing or pattern
Message-Id: <slrnbu3p2a.les.abigail@alexandra.abigail.nl>
Eric (Eric@nowhere.com) wrote on MMMDCCLXI September MCMXCIII in
<URL:news:brs1fb$rc6$1@news6.svr.pol.co.uk>:
;; >
;; > I posted my answer to your other post entitled: "RegExp to match pattern
;; or
;; > BLANK?"
;; >
;; > Why did you post the same question twice with two different subject lines?
;; >
;;
;; For the sole purpose of annoying you.
*PLONK*
Abigail
--
$_ = "\x3C\x3C\x45\x4F\x54"; s/<<EOT/<<EOT/e; print;
Just another Perl Hacker
EOT
------------------------------
Date: Thu, 18 Dec 2003 19:00:09 -0000
From: "Eric" <Eric@nowhere.com>
Subject: Re: RegExp check for nothing or pattern
Message-Id: <brstf8$5bv$1@news7.svr.pol.co.uk>
Jeez you guys take this so seriously don't you!
It wasn't _really_ to annoy him, it was a simple mistake. My comment was an
example of what's referred to as 'sarcasm'. Perhaps you've not come across
it.
Get a grip guys!
Eric
------------------------------
Date: 18 Dec 2003 07:55:07 -0800
From: palam_analog@yahoo.co.in (Palaniappan)
Subject: Signaling another machine
Message-Id: <a7b604a1.0312180755.5036f568@posting.google.com>
Hi all,
Is there any way to signal another machine?
My problem is...
I like to do run a sequence of perl scripts automatically in
different machines. They should be run one by one in different
machines in a sequence.
After completing a script in one machine, how to signal another
machine to start next script.
All machines are connected through LAN.
I know this group discusses mostly about perl coding. but i don't
have good knowledge about computer networks. so i am looking for
a perl solution directly, that's why i posted here.. :-)
-with regards
palam
------------------------------
Date: 18 Dec 2003 16:13:48 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Signaling another machine
Message-Id: <brsjns$ki3$1@mamenchi.zrz.TU-Berlin.DE>
Palaniappan <palam_analog@yahoo.co.in> wrote in comp.lang.perl.misc:
> Hi all,
>
> Is there any way to signal another machine?
>
> My problem is...
> I like to do run a sequence of perl scripts automatically in
> different machines. They should be run one by one in different
> machines in a sequence.
>
> After completing a script in one machine, how to signal another
> machine to start next script.
>
> All machines are connected through LAN.
>
> I know this group discusses mostly about perl coding. but i don't
> have good knowledge about computer networks. so i am looking for
> a perl solution directly, that's why i posted here.. :-)
That reminds me of the guy searching his car keys under a street light.
When asked if he had lost them there, he replies, "No, over there, but
there it's too dark to see".
Perl or no, you will still have to understand your network enough to be
able to start a process on one machine from another one. That procedure
depends entirely on your local network, Perl doesn't enter the equation.
Anno
------------------------------
Date: Thu, 18 Dec 2003 17:38:39 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Signaling another machine
Message-Id: <x7ptemc9gg.fsf@mail.sysarch.com>
>>>>> "P" == Palaniappan <palam_analog@yahoo.co.in> writes:
> Is there any way to signal another machine?
signals are machine local. perhaps you meant to say something else?
> I like to do run a sequence of perl scripts automatically in
> different machines. They should be run one by one in different
> machines in a sequence.
> After completing a script in one machine, how to signal another
> machine to start next script.
again, don't use the term signal there. trigger might be a better term.
take a look at stem (on cpan or at stemsystems.com). it can be easily
configured to have processes running on multiple machines. you can have
a main object send messages to other machines to trigger starting a
process. when the process is done, a message can be sent back and that
main object can trigger the next one. doing this on your own will be a
very complex project. even with stem (which will reduce your coding by
half or more) it will require some work on your part as you have to
write this main object and learn how to configure the process cell (stem
object) to run your process and send back a message. if you need any
help, feel free to contact me.
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: Thu, 18 Dec 2003 18:58:46 GMT
From: Rocco Caputo <troc@pobox.com>
Subject: Re: Signaling another machine
Message-Id: <slrnbu3uh1.21j0.troc@eyrie.homenet>
On 18 Dec 2003 07:55:07 -0800, Palaniappan wrote:
> I like to do run a sequence of perl scripts automatically in
> different machines. They should be run one by one in different
> machines in a sequence.
>
> After completing a script in one machine, how to signal another
> machine to start next script.
>
> All machines are connected through LAN.
Set up ssh so you can log into the other machines from a "master"
machine. If you decide it's safe, you can omit the ssh passphrase, and
the master machine can log into them without a password prompt.
For each script you want to run...
... determine the machine to run it on.
... use Expect.pm or something like it to SSH into the machine.
... execute the command out there.
... collect any output you're interested in.
... log out.
Repeat until you run out of scripts and/or machines. It's not very
hard.
--
Rocco Caputo - rcaputo@pobox.com - http://poe.perl.org/
------------------------------
Date: Thu, 18 Dec 2003 07:50:10 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Simple text file operation
Message-Id: <slrnbu3c4i.jc8.tadmc@magna.augustmail.com>
logic1 <logic1@esatclear.ie> wrote:
> I need this solution fairly
> quickly.
Consider hiring someone who already knows Perl to write it for you.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 18 Dec 2003 06:34:00 -0800
From: logic1@esatclear.ie (logic1)
Subject: Re: Simple text file operation
Message-Id: <6e20e34b.0312180633.5fcab93e@posting.google.com>
Anno,
Thank you for your reply. That script is most useful. Apologies for my
Perl usergroup faux pas'.
thanks again,
.logic.
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote in message news:<brrt0j$3kn$1@mamenchi.zrz.TU-Berlin.DE>...
> That's a shell script. This is a Perl group.
>
> > There's obviously numerous errors in there in syntax and language but
> > as I said my perl knowledge is limited and I need this solution fairly
> > quickly.
>
> Doesn't everybody...
>
> Here is a solution. See if you can use it.
>
> my $dir = '/tmp/aux';
> opendir my $d, $dir or die "Can't read directory $dir: $!";
>
> for my $file ( grep /\.blob$/, readdir( $d) ) {
> my ( $date, $ver, $n) = $file =~ /([^_]*)_([^_]*)_AT.*(\d+)/;
> my $f;
> unless ( open $f, "$dir/$file" ) {
> warn "Can't read $dir/$file: $!";
> next;
> }
> while ( <$f> ) {
> chomp;
> my ( $ref, $val) = split /\s*\|\s*/;
> print "$date | $ver | $ref | $val\n"
> }
> }
>
> Anno
------------------------------
Date: 18 Dec 2003 15:12:22 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Simple text file operation
Message-Id: <Xns945567D27641Aasu1cornelledu@132.236.56.8>
logic1@esatclear.ie (logic1) wrote in
news:6e20e34b.0312180633.5fcab93e@posting.google.com:
> Apologies for my Perl usergroup faux pas'.
Another faux pas is top posting.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
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 5953
***************************************
