[16748] in Perl-Users-Digest
Perl-Users Digest, Issue: 4160 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 29 00:10:27 2000
Date: Mon, 28 Aug 2000 21:10:13 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <967522213-v9-i4160@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Mon, 28 Aug 2000 Volume: 9 Number: 4160
Today's topics:
Re: processing files in a directory and stuff <yosikim@lgeds.lg.co.kr>
Re: processing files in a directory and stuff <gorbeast@SPAMSUCKS.subduction.org>
Re: processing files in a directory and stuff <timewarp@shentel.net>
Re: processing files in a directory and stuff (Eric Bohlman)
Re: processing files in a directory and stuff (Eric Bohlman)
Re: quickie obfuscation... (Abigail)
Re: regular expressions and urls. (Daniel Chetlin)
Re: rpm vs. compile on RH6.2? <sp00fD@yahoo.com>
Re: selling perl to management (Alan Barclay)
Re: selling perl to management (Abigail)
Re: The Hacker signature disciplin (Abigail)
Re: The Hacker signature disciplin (Abigail)
Re: The Hacker signature disciplin (Gwyn Judd)
Re: The Hacker signature disciplin (Tony L. Svanstrom)
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 29 Aug 2000 11:10:17 +0900
From: Yongsik Kim <yosikim@lgeds.lg.co.kr>
Subject: Re: processing files in a directory and stuff
Message-Id: <39AB1B89.B2D6BDB5@lgeds.lg.co.kr>
perldoc -f readdir()
Gorbeast wrote:
>
> Hello,
>
> I have a directory on a Win32 computer that has a large number of text
> files, all of which have content similar to this :
>
> 489384 44 34 foo bar 9458 5i4i 345485
> 483455 12 49 foo bar 9589 7t9k 458945
> 548899 87 09 foo bar 5988 9489 650966
>
> ... and so on. In other words, each line of each text file has the
> format of: zero or more whitespaces, a string of numbers, more
> whitespace, another string of numbers, yet more whitespace, another
> number, whitespace, etc.
>
> I am trying to figure out how the program can read each file of this
> directory and keep a tally of how many times a number of the _first_
> column occurs. It will only occur once each file, but it could be
> multiple files of this directory.
>
> If any one can help me out that would be very kind and I thank you.
>
> -G
------------------------------
Date: Mon, 28 Aug 2000 19:34:04 -0700
From: Gorbeast <gorbeast@SPAMSUCKS.subduction.org>
Subject: Re: processing files in a directory and stuff
Message-Id: <39AB211C.B3F29CA0@SPAMSUCKS.subduction.org>
Eric Bohlman wrote:
>
> Gorbeast (gorbeast@SPAMSUCKS.subduction.org) wrote:
> : I have a directory on a Win32 computer that has a large number of text
> : files, all of which have content similar to this :
> :
> : 489384 44 34 foo bar 9458 5i4i 345485
> : 483455 12 49 foo bar 9589 7t9k 458945
> : 548899 87 09 foo bar 5988 9489 650966
> :
> : ... and so on. In other words, each line of each text file has the
> : format of: zero or more whitespaces, a string of numbers, more
> : whitespace, another string of numbers, yet more whitespace, another
> : number, whitespace, etc.
> :
> : I am trying to figure out how the program can read each file of this
> : directory and keep a tally of how many times a number of the _first_
> : column occurs. It will only occur once each file, but it could be
> : multiple files of this directory.
>
> 1) Use opendir(), readdir(), etc. to find the filenames.
>
> 2) Use open() to open the files.
>
> 3) Use the "while (<FILE>)" syntax to read each line of each file.
>
> 4) Use a regex, the three-argument form of split(), or a combination of
> index() and substr() to extract the first number from each line.
>
Thanks for the pointers Eric -- I got steps 1-4 OK, but I am having
trouble with
> 5) Use a hash to keep count of how many times each number occurs.
I'd like to see my script output soemthing like this, where $fields[0]
is some string of numbers :
$fields[0] - 5
$fields[0] - 12
$fields[0] - 8
$fields[0] - 33
..and so on. Here is what I have so far:
-------Begin Script--------
use strict;
my $file;
my $line;
my @fields;
my %probes_found;
my $probe_id;
open (RESULTS, '>C:\Perl\bin\results.txt') || die "Couldn't open
results.txt: $!";
opendir(DIR, 'C:\Perl\bin\foo') or die "cant open directory
C:\\Perl\\bin\\foo: $!" ;
while (defined($file = readdir(DIR))) {
open(FILE, "C\:\\Perl\\bin\\foo\\$file") or warn "can't open $file: $!";
my @data = <FILE>;
foreach $line(@data) {
chomp;
$line =~ tr/ / /s;
@fields = split(/ /, $line);
print RESULTS "$fields[0]\n";
}
# }
closedir(DIR);
if (!(defined($probes_found{$fields[0]}))) {
$probes_found{$fields[0]} = 1;
}
else {
$probes_found{$fields[0]}++;
}
foreach $probe_id (keys %probes_found)
{
print "$probe_id - $probes_found{$probe_id}\n";
}
__END__
------------------------------
Date: Mon, 28 Aug 2000 22:59:04 -0400
From: Albert Dewey <timewarp@shentel.net>
Subject: Re: processing files in a directory and stuff
Message-Id: <39AB26F8.C756AFB0@shentel.net>
Gorbeast wrote:
> Hello,
>
> I have a directory on a Win32 computer that has a large number of text
> files, all of which have content similar to this :
>
> 489384 44 34 foo bar 9458 5i4i 345485
> 483455 12 49 foo bar 9589 7t9k 458945
> 548899 87 09 foo bar 5988 9489 650966
>
> ... and so on. In other words, each line of each text file has the
> format of: zero or more whitespaces, a string of numbers, more
> whitespace, another string of numbers, yet more whitespace, another
> number, whitespace, etc.
>
> I am trying to figure out how the program can read each file of this
> directory and keep a tally of how many times a number of the _first_
> column occurs. It will only occur once each file, but it could be
> multiple files of this directory.
>
> If any one can help me out that would be very kind and I thank you.
>
> -G
I think I know what you might be looking for here but could you please
clarify a bit your post - this is not a flame - just try to reword your
post a bit more clearly so I can understand it.
Albert Dewey
------------------------------
Date: 29 Aug 2000 03:34:51 GMT
From: ebohlman@netcom.com (Eric Bohlman)
Subject: Re: processing files in a directory and stuff
Message-Id: <8ofb0r$qms$1@slb1.atl.mindspring.net>
Gorbeast (gorbeast@SPAMSUCKS.subduction.org) wrote:
: Thanks for the pointers Eric -- I got steps 1-4 OK, but I am having
: trouble with
:
: > 5) Use a hash to keep count of how many times each number occurs.
:
: I'd like to see my script output soemthing like this, where $fields[0]
: is some string of numbers :
:
:
: $fields[0] - 5
: $fields[0] - 12
: $fields[0] - 8
: $fields[0] - 33
:
: ..and so on. Here is what I have so far:
:
: -------Begin Script--------
Some of my comments are going to be purely on matters of style.
: use strict;
: my $file;
: my $line;
: my @fields;
: my %probes_found;
: my $probe_id;
[style] it's usually best to declare variables where they're first used,
rather than all at the top.
: open (RESULTS, '>C:\Perl\bin\results.txt') || die "Couldn't open
: results.txt: $!";
: opendir(DIR, 'C:\Perl\bin\foo') or die "cant open directory
: C:\\Perl\\bin\\foo: $!" ;
:
: while (defined($file = readdir(DIR))) {
:
: open(FILE, "C\:\\Perl\\bin\\foo\\$file") or warn "can't open $file: $!";
:
: my @data = <FILE>;
:
: foreach $line(@data) {
No reason to read the entire file into memory. Replace the above two
statements with
while (<FILE>) {
and change the next two occurrences of $line to $_.
:
: chomp;
Which, among other things, will make this last statement actually work
(with no argument, chomp() chomps $_).
:
: $line =~ tr/ / /s;
:
: @fields = split(/ /, $line);
[style] Use the magic ' ' form of the first argument to split to avoid the
need to pre-collapse whitespace.
:
: print RESULTS "$fields[0]\n";
:
: }
:
: # }
:
: closedir(DIR);
This statement seems to be in the wrong place, but maybe you put it there
purely for debugging purposes.
:
: if (!(defined($probes_found{$fields[0]}))) {
: $probes_found{$fields[0]} = 1;
: }
: else {
: $probes_found{$fields[0]}++;
: }
This is Perl, not C. It will do the Right Thing if you try to increment
an uninitialized hash value; just use
$probes_found{$fileds[0]}++;
But this statement belongs *inside* the inner loop, whereas the next
statement belongs outside both loops.
: foreach $probe_id (keys %probes_found) :
: {
:
: print "$probe_id - $probes_found{$probe_id}\n";
:
:
: }
And that should probably be printing to RESULTS rather than STDOUT.
:
:
: __END__
[style] Your choice of indentation is what most Perl programmers would
regard as bizarre. See the perlstyle manpage for some less bizarre styles.
It looks like your main problem is improper loop nesting.
------------------------------
Date: 29 Aug 2000 03:41:41 GMT
From: ebohlman@netcom.com (Eric Bohlman)
Subject: Re: processing files in a directory and stuff
Message-Id: <8ofbdl$qms$2@slb1.atl.mindspring.net>
Eric Bohlman (ebohlman@netcom.com) wrote:
:
: This is Perl, not C. It will do the Right Thing if you try to increment
: an uninitialized hash value; just use
:
: $probes_found{$fileds[0]}++;
Of course, you'll spell "fields" correctly, unlike me.
------------------------------
Date: 29 Aug 2000 01:26:47 GMT
From: abigail@foad.org (Abigail)
Subject: Re: quickie obfuscation...
Message-Id: <slrn8qm497.bbg.abigail@alexandra.foad.org>
jason (elephant@squirrelgroup.com) wrote on MMDLV September MCMXCIII in
<URL:news:MPG.14159e8b164a86f5989717@localhost>:
|| Abigail <abigail@foad.org> wrote ..
|| >Marcel Grunauer (marcel@codewerk.com) wrote on MMDLIV September MCMXCIII
|| >in <URL:news:slrn8qlg28.efv.marcel@gandalf.local>:
|| >\\ On Mon, 28 Aug 2000 15:25:01 -0400, Aaron Spangler <aspangler@lucent.com>
|| >\\
|| >\\ >Why does
|| >\\ > print 1 and 0;
|| >\\ >return 1?
|| >\\ >
|| >\\ >What is perl actually performing here?
|| >\\
|| >\\ $ perl -MO=Deparse,-p -e 'print 1 and 0'
|| >\\ (print(1) and '???');
|| >\\ -e syntax OK
|| >\\
|| >\\ This is what perl sees. Does that help? Note the placement of the
|| >\\ parentheses for print().
|| >
|| >
|| >Well, that is certainly confusing.
|| >
|| >As far as I can tell, the result of "print 1 and 0" is false, but the
|| >result of "(print (1) and '???')" is true.
|| >
|| >Unless '???' suddenly became 0.
||
|| umm .. not sure if this explains it .. but the assignment operator binds
|| tighter than 'and' .. so
||
|| my $foo = print 1 and 0;
||
|| parses to
||
|| ( my $foo = print 1 ) and 0;
||
|| so .. that parsing makes sense in an assignment situation .. and for
|| some reason Perl does the same thing when evaluating the statement's
|| value in a non-assignment situation
||
|| which explains the ( print(1) and '???' )
Well, first of all, the "and 0" part are *not* part of the assignment,
as your own parenthesis show. Secondly, the "for some reason" doesn't
explain a single thing. What is this "some reason", and how does it
affect me.
If "print 1 and 0" is the final statement of a sub, there's a huge
difference between "print 1 and 0" and "print (1) and '???'". As
large as false and true.
|| and also the difference in your sub test {} example elsewhere in the
|| thread .. because there's no assignment assumed at the end of a sub ..
|| only a return wrapper .. and
||
|| return 1 and 0;
||
|| will evaluate the 'and' before passing the result to 'return'
||
|| [ line longer than 80 chars truncated ]
Huh? What line longer than 80 characters? I don't post lines longer than
80 characters, except for quoted text, but even then I usually clip.
Perhaps you think 79 > 80?
Abigail
--
perl -wleprint -eqq-@{[ -eqw+ -eJust -eanother -ePerl -eHacker -e+]}-
------------------------------
Date: Tue, 29 Aug 2000 03:31:28 GMT
From: daniel@chetlin.com (Daniel Chetlin)
Subject: Re: regular expressions and urls.
Message-Id: <k8Gq5.4285$D7.144337@news-west.usenetserver.com>
On 28 Aug 2000 22:14:08 GMT, Eli the Bearded <elijah@workspot.net> wrote:
>Look at my posts in 'Stumped by Reg Exp Problem - help??' thread,
>eg: <news:eli$0008251340@qz.little-neck.ny.us>, with the caveat
>that I only attempted to match HTTP/HTTPS scheme URLs rather than
>the whole of them, and that I assume a non-HTML context.
>
>If you have an HTML-context, you are better off using an HTML
>parser, eg HTML::Parser from your nearby CPAN mirror.
URI::Find and HTML::Parser should do the trick pretty much everywhere. Why
does HTML::Parser require an HTML context? If it's _possible_ that there will
be an HTML context, it should be used (assuming different things are done to
found URIs depending on whether they're within <a></a>. It doesn't mess up
plaintext if you do it right.
And I'm afraid of suggesting any self-rolled REx when something like URI::Find
is out there. There's too many things to watch out for.
-dlc
------------------------------
Date: Tue, 29 Aug 2000 01:49:18 GMT
From: sp00fD <sp00fD@yahoo.com>
Subject: Re: rpm vs. compile on RH6.2?
Message-Id: <8of4qp$o9f$1@nnrp1.deja.com>
In article <8F9EC0C2Ebakkinavacocom@207.126.101.100>,
bakki@navaco.com (Bakki Kudva) wrote:
> I need some one to enlighten me on the intricacies of rpm vs. compile
from
> source on RedHat Linux? I have several questions in this regard.
>
> 1. Since the perl-5.xx.rpm on RedHat Linux systems seem to install in
non
> standard ways (/usr/lib vs. /usr/local) what is the effect of
installing
> from .tar.gz sources?
>
Not quite following what you're looking for here, but it's quite
possible to run multiple version of perl.
> 2. Uninstalling the perl rpm breaks so many dependencies that it is
scary
> to do so. On the othe hand if I install the traditional way will I
end up
> with multiple, incompatible libraries?
I think that you'd be fairly safe to remove it and place a link in the
perl binaries place, i.e.
ln -s /usr/local/bin/perl /usr/lib/(perl5/5.0..?)/perl
but it's not necessary and who knows, maybe it could break something.
>
> 3. RedHat seems to be always a bit lagging in releasing the current
stable
> version of perl as an rpm. I did find a 5.6.0 rpm at
http://www.sjc.com/
> but this wouldn't install because gnorpm complains that it is older
than
> the installed version though the build dates in the rpm say otherwise.
>
I would say this is caused by bad version testing on the packager's
part. Try using the --force option.
> 4. I have experienced that if you try to build Apache, mod_perl etc
with
> the rpm version of perl there are some times side effects which cause
the
> make or make test to fail.
Yes, I've had lots of problems in the past trying to compile many
things using libs that were installed as rpm's.
>
> 5. So the ultimate question then is, which is the preferred way of
> installing perl on RH? If the answer is to compile from .tar.gz, then
what
> is the safe way to yank the rpm out and do a build?
I'd say, try to find the rpm from RedHat's site (or on your cdrom)
(just to be sure that you have it) that fits your distro, then remove
the version that's installed and replace perl with a link. If things
get hairy, just install the rpm you downloaded from RedHat (or from
your cdrom) to get back to where you started from.
>
> I would really appreciate some help on this becuase I have not found
> anything on the subject at RH or other perl sites.
>
> bakki
>
> Bakk Kudva
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: 29 Aug 2000 02:36:26 GMT
From: gorilla@elaine.furryape.com (Alan Barclay)
Subject: Re: selling perl to management
Message-Id: <967516584.917639@elaine.furryape.com>
In article <H5uq5.20881$K5.359601@typhoon.austin.rr.com>,
Mike Stok <mike@stok.co.uk> wrote:
>One crucial difference between C and Perl is that the installation of a
>new C compiler with new behaviour doesn't break all of the compiled code
>on a machine - it's only at compile time that you suffer the pain. In
>general use you compile C once then the binary is what's executed , but
>perl usually compiles every time a script is run.
Put "/usr/local/bin/perl5.005003" as the #! line, changing the number
to the version you want, and of course the correct path. Then, when
you install a new version of perl, that script will continue to use
the old perl.
------------------------------
Date: 29 Aug 2000 03:04:16 GMT
From: abigail@foad.org (Abigail)
Subject: Re: selling perl to management
Message-Id: <slrn8qm9vv.bbg.abigail@alexandra.foad.org>
Alan Barclay (gorilla@elaine.furryape.com) wrote on MMDLV September
MCMXCIII in <URL:news:967516584.917639@elaine.furryape.com>:
{} In article <H5uq5.20881$K5.359601@typhoon.austin.rr.com>,
{} Mike Stok <mike@stok.co.uk> wrote:
{} >One crucial difference between C and Perl is that the installation of a
{} >new C compiler with new behaviour doesn't break all of the compiled code
{} >on a machine - it's only at compile time that you suffer the pain. In
{} >general use you compile C once then the binary is what's executed , but
{} >perl usually compiles every time a script is run.
{}
{} Put "/usr/local/bin/perl5.005003" as the #! line, changing the number
{} to the version you want, and of course the correct path. Then, when
{} you install a new version of perl, that script will continue to use
{} the old perl.
Untill you run CPAN.pm with UNINSTALL and install a new version of own
of the modules you are using, and suddenly, older version of Perl no
longer find the module.
Abigail
--
sub f{sprintf'%c%s',$_[0],$_[1]}print f(74,f(117,f(115,f(116,f(32,f(97,
f(110,f(111,f(116,f(104,f(0x65,f(114,f(32,f(80,f(101,f(114,f(0x6c,f(32,
f(0x48,f(97,f(99,f(107,f(101,f(114,f(10,q ff)))))))))))))))))))))))))
------------------------------
Date: 29 Aug 2000 01:09:24 GMT
From: abigail@foad.org (Abigail)
Subject: Re: The Hacker signature disciplin
Message-Id: <slrn8qm38k.bbg.abigail@alexandra.foad.org>
Jakob Schmidt (sumus@aut.dk) wrote on MMDLIV September MCMXCIII in
<URL:news:1eg3nmp.17nqhqm1lkr7ggN@[192.168.88.117]>:
!!
!! I find myself wondering if there are some written or unwritten rules
!! about the "Just another Perl Hacker" sig that some posters use?
From my JAPH talks:
<LI>There are no formal rules on what is a JAPH and what isn't.
<LI>But we can derive some de facto rules.
<LI>Short: preferably fit in 4 x 80 characters.
<LI>Prints "Just another Perl Hacker".
<LI>Obscure or surprising syntax.
Abigail
--
perl -wle '$, = " "; sub AUTOLOAD {($AUTOLOAD =~ /::(.*)/) [0];}
print+Just (), another (), Perl (), Hacker ();'
------------------------------
Date: 29 Aug 2000 01:13:07 GMT
From: abigail@foad.org (Abigail)
Subject: Re: The Hacker signature disciplin
Message-Id: <slrn8qm3fj.bbg.abigail@alexandra.foad.org>
Eli the Bearded (elijah@workspot.net) wrote on MMDLIV September MCMXCIII
in <URL:news:eli$0008281836@qz.little-neck.ny.us>:
// In comp.lang.perl.misc, Jakob Schmidt <sumus@aut.dk> wrote:
// > I find myself wondering if there are some written or unwritten rules
// > about the "Just another Perl Hacker" sig that some posters use?
//
// The general rules as I understand them are:
//
// Works on more than just your version of perl (including other
// platforms: Abigail's abuse of rand() violates that).
I've never heard someone stating that rule. One of my favourite ones
works only on perl5.004 - by design. (One variant only works on perl5.004,
and not even on perl5.00401; again, by design).
// Works in a clever way: print unpack('u*',...) is not very clever.
// This is suject to various peoples personal opinions.
//
// I'm also a bit hesitant about the use of specifically undocumented
// features, eg I find Abigail's use of %^H rather dubious.
Obscure undocument features make for the best JAPHs. "Dubious" is a
complement. And besides, %^H is documented in perlvar.
Abigail
--
perl5.004 -wMMath::BigInt -e'$^V=Math::BigInt->new(qq]$^F$^W783$[$%9889$^F47]
.qq]$|88768$^W596577669$%$^W5$^F3364$[$^W$^F$|838747$[8889739$%$|$^F673$%$^W]
.qq]98$^F76777$=56]);$^U=substr($]=>$|=>5)*(q.25..($^W=@^V))=>do{print+chr$^V
%$^U;$^V/=$^U}while$^V!=$^W'
------------------------------
Date: Tue, 29 Aug 2000 02:17:53 GMT
From: tjla@guvfybir.qlaqaf.bet (Gwyn Judd)
Subject: Re: The Hacker signature disciplin
Message-Id: <slrn8qm7ae.2nf.tjla@thislove.dyndns.org>
I was shocked! How could Jakob Schmidt <sumus@aut.dk>
say such a terrible thing:
>Hi
>
>I find myself wondering if there are some written or unwritten rules
>about the "Just another Perl Hacker" sig that some posters use?
>
>Of course I had to make a couple myself but I'm worried that I may be
>breaking some rules (like for instance maybe you have to be a _real_
>Perl Hacker) and making a fool of myself if I use them.
The only ones I can think of are unwritten type rules...it should be
interesting, fun, surprising and obviously it should print out "Just
another Perl Hacker".
This is, I think, officially the worst JAPH I've ever seen...It seems to
work on my computer, although it may not on yours.
$,=" "; @x{qw(Just Another PERL Hacker)}='';
print map(ucfirst lc, reverse %x)
--
Gwyn Judd (print `echo 'tjla@guvfybir.qlaqaf.bet' | rot13`)
Children aren't happy without something to ignore, and that's what
parents were created for.
-- Ogden Nash
------------------------------
Date: Tue, 29 Aug 2000 05:34:35 +0200
From: tony@svanstrom.com (Tony L. Svanstrom)
Subject: Re: The Hacker signature disciplin
Message-Id: <1eg423m.dghq4n1f5ivziN%tony@svanstrom.com>
jason <elephant@squirrelgroup.com> wrote:
> Jakob Schmidt <sumus@aut.dk> wrote ..
> >I find myself wondering if there are some written or unwritten rules
> >about the "Just another Perl Hacker" sig that some posters use?
> >
> >Of course I had to make a couple myself but I'm worried that I may be
> >breaking some rules (like for instance maybe you have to be a _real_
> >Perl Hacker) and making a fool of myself if I use them.
>
> I think the only rule that I'm aware of is that if you have to ask -
> then you shouldn't use it *8^)
I can't but agree. *L*
/Tony
--
print 'Just Another Nervous Wreck';
------------------------------
Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 16 Sep 99)
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: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.
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 V9 Issue 4160
**************************************
