[31097] in Perl-Users-Digest
Perl-Users Digest, Issue: 2342 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Apr 15 21:09:40 2009
Date: Wed, 15 Apr 2009 18: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 Wed, 15 Apr 2009 Volume: 11 Number: 2342
Today's topics:
Re: (newbie) need help understanding a few lines of cod (Tim McDaniel)
Re: (newbie) need help understanding a few lines of cod <ben@morrow.me.uk>
Re: (newbie) need help understanding a few lines of cod (Tim McDaniel)
Re: F<utf8.pm> is evil (was: XML::LibXML UTF-8 toString <hjp-usenet2@hjp.at>
Re: out of memory <hirenshah.05@gmail.com>
Re: out of memory derykus@gmail.com
Re: out of memory <tzz@lifelogs.com>
Re: Pipe Between Programs <cwilbur@chromatico.net>
Re: Regex question. Oh I so cannot do regular expressio sln@netherlands.com
using SSH without modules <rodbass63@gmail.com>
Re: using SSH without modules <tadmc@seesig.invalid>
Re: using SSH without modules <rodbass63@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 15 Apr 2009 20:58:23 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Re: (newbie) need help understanding a few lines of code
Message-Id: <gs5hpf$b6b$1@reader1.panix.com>
In article <74f6nfF11ceb1U1@mid.individual.net>,
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote:
>Ben wrote:
>> [stuff]
>Personally I find the coding style somewhat obfuscated. I would
>probably have said something like:
>
> my $noHires = $@;
I now know the rules on what's considered "true", but personally, if I
use a variable in a boolean context, I prefer it to be a clear
boolean, such as the result of a boolean operator, if for no other
reason than documentation. So I'd do
my $hasHires = ($@ eq '');
>> $|++;
>
>Sets $| to a true value (adds 1). See "perldoc perlvar" about the
>meaning of $|.
Turning on autoflush with an increment is ridiculous, when they could
just as easily do
$| = 1;
and have it actually work in all cases (assuming autoflush is
implemented at all). It makes me want to start the program with
$| = -1; # sets $| to a true value, so it should autoflush
just to show how bad an increment is.
--
Tim McDaniel, tmcd@panix.com
------------------------------
Date: Wed, 15 Apr 2009 22:38:34 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: (newbie) need help understanding a few lines of code
Message-Id: <qn0ib6-f181.ln1@osiris.mauzo.dyndns.org>
Quoth tmcd@panix.com:
> In article <74f6nfF11ceb1U1@mid.individual.net>,
> Gunnar Hjalmarsson <noreply@gunnar.cc> wrote:
> >Ben wrote:
[not me :)]
> >> [stuff]
> >Personally I find the coding style somewhat obfuscated. I would
> >probably have said something like:
> >
> > my $noHires = $@;
>
> I now know the rules on what's considered "true", but personally, if I
> use a variable in a boolean context, I prefer it to be a clear
> boolean, such as the result of a boolean operator, if for no other
> reason than documentation. So I'd do
> my $hasHires = ($@ eq '');
...whereas someone who is familiar with Perl would find that confusing.
To me it immediately raises the question 'what is he expecting $@ to
contain that prohibits using it as a simple boolean?'.
> >> $|++;
> >
> >Sets $| to a true value (adds 1). See "perldoc perlvar" about the
> >meaning of $|.
>
> Turning on autoflush with an increment is ridiculous, when they could
> just as easily do
> $| = 1;
> and have it actually work in all cases (assuming autoflush is
> implemented at all). It makes me want to start the program with
> $| = -1; # sets $| to a true value, so it should autoflush
> just to show how bad an increment is.
Oh, but it *does* work in all cases. $| is magical, remember.
~% perl -le'$| = -1; print $|'
1
~% perl -le'$| = 1; $|++; print $|'
1
~% perl -le'$| = -1; $|++; print $|'
1
~%
Whether your find this amusing or obscene probably depends on your sense
of humour :).
(I don't understand what you mean by 'assuming autoflush is implemented
at all'. AFAIK autoflush is always implemented...)
Ben
------------------------------
Date: Wed, 15 Apr 2009 23:23:58 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Re: (newbie) need help understanding a few lines of code
Message-Id: <gs5qae$g33$1@reader1.panix.com>
In article <qn0ib6-f181.ln1@osiris.mauzo.dyndns.org>,
Ben Morrow <ben@morrow.me.uk> wrote:
>
>Quoth tmcd@panix.com:
>> Turning on autoflush with an increment is ridiculous, when they
>> could just as easily do
>> $| = 1;
>> and have it actually work in all cases (assuming autoflush is
>> implemented at all). It makes me want to start the program with
>> $| = -1; # sets $| to a true value, so it should autoflush
>> just to show how bad an increment is.
>
>Oh, but it *does* work in all cases. $| is magical, remember.
>
> ~% perl -le'$| = -1; print $|'
> 1
> ~% perl -le'$| = 1; $|++; print $|'
> 1
> ~% perl -le'$| = -1; $|++; print $|'
> 1
You. MUST. Be. Shitting. Me.
[checking]
It does just that under Perl 5.00502 and 5.010000. Gahhh ...
>Whether your find this amusing or obscene probably depends on your
>sense of humour
Obscene, highly counter-intuitive, and undocumented:
$| If set to nonzero, forces a flush right away and after every
write or print on the currently selected output channel.
Default is 0 (regardless of whether the channel is really
buffered by the system or not; $| tells you only whether you've
asked Perl explicitly to flush after each write). ...
>(I don't understand what you mean by 'assuming autoflush is implemented
>at all'. AFAIK autoflush is always implemented...)
Weasel-wording: I was afraid that, if I left it out, someone would
mock my ignorance of the fact that the port to Irish Business Machines
System/42 did nothing with $|.
--
Tim McDaniel, tmcd@panix.com
------------------------------
Date: Wed, 15 Apr 2009 22:28:37 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: F<utf8.pm> is evil (was: XML::LibXML UTF-8 toString() -vs- nodeValue())
Message-Id: <slrngucgrm.vg9.hjp-usenet2@hrunkner.hjp.at>
On 2009-04-14 23:45, Eric Pozharski <whynot@pozharski.name> wrote:
> On 2009-04-12, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>> On 2009-04-12 14:14, Eric Pozharski <whynot@pozharski.name> wrote:
> *SKIP*
>>> On 2009-04-11, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>>>> On 2009-04-11 11:59, Eric Pozharski <whynot@pozharski.name> wrote:
>
> I've thought a lot. I should admit, whenever I see C<use 'utf8';>
> instead of C<use encoding 'utf8';> I'm going nuts.
I'm going nuts when I see "use encoding". It does way too many magic
things and most of them only half-baked. Here be dragons! Don't use that
stuff, if you value your sanity.
> And with C<use encoding 'utf8';> you'll get the same character string,
> and lots of other useful stuff.
Correction: Lots of stuff which looks useful at first glance but which
works in subly different ways than you expect (and some stuff which you
simply don't expect). "use utf8" OTOH does only one thing, and it does
it well.
> (I just can't get why anyone would need
> implicit upgrade of scalars into characters and yet then maintain wide
> IO.) But my point isn't that F<encoding.pm> outperforms F<utf8.pm>.
> I'm scared. I consider F<utf8.pm> kind of Pandora box. Read this, if
> you can
>
> проц запросить {
> мое ($имяфайла) = @_;
[...]
> }
>
> I admit, it's imposible to write this with F<utf8.pm> alone
Right. "sub" still is "sub", not "проц", and "my" is still "my", not
"мое". Your example is more like a Russian(?) equivalent to
Lingua::Romana::Perligata.
And frankly, "проц запросить" is only marginable less readable to me
than "sub zaprosit". I need a dictionary for both, and "запросить" at
least has the advantage that I can actually find it in a Russian
dictionary :-). If you want your software to be maintainable by authors
from other countries, stick to English and write "sub request". If you
want to use Russian names you might as well go all the way and use
cyrillic letters instead of a transliteration into latin letters which
neither those who speak Russian nor those who don't speak Russian
understand easily.
> I bet you've seen this before,
I've seen German versions of BASIC in the 1980's. They weren't a huge
success, to put it mildly. About the only successful localization of a
programming language i can think of is MS-Excel (and I guess it's
debatable if this is even a programming language (without VBA) - is it
turing-complete?).
> Someone could say "Who the heck would need that stupidity?" Idiots. It
> still surprises me how many idiots are around. They would scream:
> "Look! What a cool stuff! I have to learn nothing!"
Idiots indeed, if they think learning a few dozen keywords is the
hardest part in learning a programming language. In fact I think the
main reason why localized programming languages are so unpopular is that
people figure out that it doesn't make any difference whether you
declare a lexical variable with "my", "мое", or "mein": You have to
learn the keyword anyway and you have to learn what it means and how to
use it.
>>>>> In case there would be C<use utf8> or C<use encoding 'utf8'>,
>>>>
>>>> then the compiler would complain about a malformed UTF-8 character if
>>>> the source file was actually in ISO-8859-7.
>>>
>>> But it didn't.
>>
>> It does for me. If I change "use encoding 'ISO-8859-7'" to "use utf8"
>> in my ISO-8859-7 encoded file, I get a lot of warnings.
>
> Yes, it does. Since I've typed examples on command-line I'd gone with
> those hex-escapes. They don't warn.
Of course not. They are just US-ASCII, which is a subset of UTF-8 and
ISO-8859-x.
> If B<perl> finds *bytes* with high bit set (so they aren't valid utf8)
> while being in any way utf8 encoding mode then it really complains
> (and complains a lot).
Yup.
>>> Do not use this pragma for anything else than telling Perl that your
>>> script is written in UTF-8. The utility functions described below
>>> are directly usable without "use utf8;".
>>
>> I believe I already said that once or twice in this thread.
>>
>>
>>> My understanding of "script" is a program text outside of any quotes in
>>> it.
>>
>> Bullshit. A script is the complete program text, including any string
>> constants, numeric constants, comments, the __DATA__ stream, if any.
>> Why would a string constant in a script not be part of it?
>
> Yes, I should agree that "script" in general means this. That's my
> understanding of what was said (or meant) here by this word.
I don't see how you get that understanding. Clearly string constants in
a script *are* interpreted as utf8 if you use "use utf8".
>> You mean:
>>
>> {3415:30} [0:0]$ perl -Mencoding=ucs2 -wle 'print "\x{4404}\x{4b04}\x{3204}\x{3004}"'
>> Can't locate object method "cat_decode" via package "Encode::Unicode" at
>> -e line 1.
>>
>> That doesn't fix the endianness, and it behaves completely differently.
>> "perl -Mencoding=ucs2" can't work, as I already explained to sln.
>
> This fixes endianness?
>
> {56061:37} [0:0]$ perl -Mencoding=ucs2 -wle 'print "\x{0444}\x{044b}\x{0432}\x{0430}"'
> Can't locate object method "cat_decode" via package "Encode::Unicode" at
> -e line 1.
Yes, that fixes the endianness.
> However, since I don't understand why it "can't work",
It can't work because -Mencoding=ucs2 says that the source code is
encoded in ucs2. So your script would have to begin with the byte
sequence
FE FF 00 70 00 72 00 69 00 6e 00 74 00 20 ...
to be interpreted as "print ...". But it doesn't (and it can't because
you cannot pass arguments with embedded null bytes in Unix).
It begins with
70 72 69 6e 74 20
which doesn't seem to be anything useful in UCS2 (U+2074 is SUPERSCRIPT
FOUR, but the rest is unassigned in both big and little endian).
It becomes worse if you use "use encoding 'ucs2';" inside a script:
You would have to start the script in US-ASCII so that "use encoding
'ucs2';" is recognized and then switch to UCS2: So you need to mix two
different incompatible encodings in the same script: Good luck finding
an editor which supports this. And you don't have to, anyway, because if
you want to encode your scripts in UTF-16, you can just do it and perl
will notice it automatically (but Unix won't recognize the hashbang any
more, so you don't want to do this on Unix - you might on windows,
though).
hp
------------------------------
Date: Wed, 15 Apr 2009 11:11:02 -0700 (PDT)
From: "friend.05@gmail.com" <hirenshah.05@gmail.com>
Subject: Re: out of memory
Message-Id: <85596447-f025-4c76-af2a-7bd5589c0842@37g2000yqp.googlegroups.com>
On Apr 15, 11:46=A0am, J=FCrgen Exner <jurge...@hotmail.com> wrote:
> "friend...@gmail.com" <hirenshah...@gmail.com> wrote:
> >I am dealing with large data.
>
> >I am creating one hash table for my data.
>
> >But when I try to access the value in hash table it is giving me out
> >of memory.
>
> >can anyone suggest what can be problem and how can I slove it.
>
> Problem: Your program is using more memory than ulimit allows.
> Solution: either reduce the memory footprint of your program or increase
> your ulimit.
>
> There is also the off-chance that you found a bug in Perl, but you will
> need very strong evidence to support that theory.
>
> jue
I am using fork and processing the data simultanously. I also ouput
file for each process.
So my final result is combination of these files. In end try to read
files and create hash table and then use tht hash for final output.
here it is giving me out of memory error.
but if write another script for reading those different files which
were created my child processes in my previous script and create hash.
so if separate script for final oupput file it is not giving me error.
------------------------------
Date: Wed, 15 Apr 2009 11:20:34 -0700 (PDT)
From: derykus@gmail.com
Subject: Re: out of memory
Message-Id: <56aa69df-7eb1-4bc6-ada4-85a10189ebba@w35g2000prg.googlegroups.com>
On Apr 15, 8:10=A0am, "friend...@gmail.com" <hirenshah...@gmail.com>
wrote:
> I am dealing with large data.
>
> I am creating one hash table for my data.
>
> But when I try to access the value in hash table it is giving me out
> of memory.
>
> can anyone suggest what can be problem and how can I slove it.
You could try a DBM to reduce memory footprint, eg. DB_File,
DBM::Deep, etc.
--
Charles DeRykus
------------------------------
Date: Wed, 15 Apr 2009 13:58:36 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: out of memory
Message-Id: <861vrtlp5v.fsf@lifelogs.com>
On Wed, 15 Apr 2009 11:00:49 -0700 (PDT) "friend.05@gmail.com" <hirenshah.05@gmail.com> wrote:
f0c> but when I am creating tht hash table there is no error.
f0c> it gives error when I try to access tht hash array.
It's like the old story (copied someone else's version, too lazy to tell
it properly)
Moshe prays and prays to Hashem to win the lottery...week after
week....he tell Hashem how he will help the poor...another week he tells
Hashem he will build a new Shul...another week he tells Hashem he will
build a new school...this goes on week after week...yet nothing happens.
Moshe gets so frustrated that he cries to Hashem "Why won't you answer
my prayers? All I want to do is good things and make Kiddush Hashem"
The clouds part and a booming voice comes from the Shamayim.....
"Moshe....
......meet me halfway.....
......BUY A TICKET"
So friend.05 / hirenshah.05, meet us halfway...SHOW YOUR SOURCE CODE.
Ted
------------------------------
Date: Wed, 15 Apr 2009 16:53:09 -0400
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: Pipe Between Programs
Message-Id: <86iql5myfe.fsf@mithril.chromatico.net>
>>>>> "EDG" == E D G <edgrsprj@ix.netcom.com> writes:
EDG> With many Newsgroups and in particular this one, people can be
EDG> strongly criticized for submitting "dumb" questions that waste
EDG> the time of the experts.
The experts here criticize people not for asking dumb questions, but for
asking questions in ways that cannot be usefully answered. The Posting
Guidelines explain very clearly how to ask a question in a way that can
maximizes the chances that the querent will get real help.
Playing 20 questions with someone who has come here for help, because
that someone can't include an actual working example of the problem and
because that someone didn't include the actual error message wastes
*everyone's* time.
EDG> With another Newsgroup people could post dumb questions without
EDG> having someone tell them to stop. If they were given
EDG> inaccurate information for their program questions then their
EDG> programs would simply not work.
So start such a newsgroup! I believe there are several websites set up
where such behavior is not only tolerated, but encouraged.
EDG> The theory that this would somehow destroy the Perl language is
EDG> I believe unfounded. It might eventually work even better
EDG> because more people around the world would be willing to use
EDG> it. At the moment many people probably choose other languages
EDG> in part because they are afraid to post "dumb" questions to
EDG> this Newsgroup.
You know, if people are unwilling to ask for *free* help in a way that
increases their chances of actually getting that help, I really don't
care whether or not they're willing to use Perl. Let them use Visual
Basic; let them use Python; let them use Ruby. The same dynamics
between lazy querents and annoyed experts obtain everywhere except where
the lazy querents need to pay for help -- at which point they suddenly
stop being lazy, because suddenly it's costing them.
EDG> Is Perl intended only for the use of experts? I thought that
EDG> one of the original goals was to create a highly versatile and
EDG> powerful language that anyone could use.
Perl is intended for the use of anyone with the wit to actually learn to
use it. It *is* a highly versatile and powerful language that anyone
can use. It's extremely well documented, and there are a host of books
that you can use in your attempts to become competent in it.
But what you're doing here is not expecting to use Perl, but expecting
experts in Perl to write your program for you. At the root of it all,
you have two options: you can learn to program in Perl, or you can hire
a programmer. You may notice that "harangue Perl experts into writing
your program for you" is not included among those options; so if you
simply must have the program written, and you are not willing to invest
the effort to master Perl yourself, then I advise you to pull out your
checkbook.
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: Wed, 15 Apr 2009 12:29:47 -0700
From: sln@netherlands.com
Subject: Re: Regex question. Oh I so cannot do regular expression matching.
Message-Id: <ecbcu49o8sf0m7do4n8j0n5gi3qf16cu0b@4ax.com>
On Tue, 14 Apr 2009 09:08:37 -0700 (PDT), grocery_stocker <cdalten@gmail.com> wrote:
>I can't seem to get perl to match both the words 'chad' AND 'party'
>in the string "chad ttyp0 party". Below is what I attempted.
>
>[cdalten@localhost oakland]$ more match.pl
>#!/usr/bin/perl
>use warnings;
>
>#$string = `w | grep cdalten | grep telnet`;
>
>$test = "chad ttyp0 party";
>
>if ("$test" =~/(\bchad\b)(\bparty\b)/) {
> print "true \n";
>}
>[cdalten@localhost oakland]$ ./match.pl
>[cdalten@localhost oakland]$
>
>What am I doing wrong>
Since you didn't mention an order of appearence, the below
will cover the AND like operator in regexp, on two objects
in ANY order. Otherwise "$test" =~/(\bchad\b).*(\bparty\b)/
would work as many have said on this thread.
It can be done in a single regular expression using a
zero-width negative look-ahead assertion and the two objects.
The basic logic is below. However I think this can be generalized
for AND on sets of 3 or more items using some form of s///eg and/or
a more complex backreferencing scheme, recursion, or other extended
regular expression methods.
-sln
------------------------------------------------------------
## Rx_And.pl
## --
use strict;
use warnings;
my @ar = (
'chad ttyp0 party',
'chad ttyp0 chad',
'party ttyp0 chad',
'party ttyp0 party',
'chad party party ttyp0 chad',
);
for (@ar)
{
# print " Found $1 AND $2\n"
# if ( / (\b chad | party \b) .* (?!\1) (\b chad | party \b) /x );
# Or, for a closer (non-greedy) global examination ..
my $cnt = 1;
print "\n'$_'\n";
while ( / (\b chad | party \b) (.*?) (?!\1) (\b chad | party \b) /xsg ) {
print " Found[",$cnt++,"]: $1 ($2) AND $3\n"
}
}
__END__
'chad ttyp0 party'
Found[1]: chad ( ttyp0 ) AND party
'chad ttyp0 chad'
'party ttyp0 chad'
Found[1]: party ( ttyp0 ) AND chad
'party ttyp0 party'
'chad party party ttyp0 chad'
Found[1]: chad ( ) AND party
Found[2]: party ( ttyp0 ) AND chad
------------------------------
Date: Wed, 15 Apr 2009 11:22:19 -0700 (PDT)
From: Nene <rodbass63@gmail.com>
Subject: using SSH without modules
Message-Id: <971fc5da-35e0-4845-bebc-3471f474c976@e23g2000vbe.googlegroups.com>
Hello,
My object is to do a few things without the use of modules, I only
know how to use
open(SSH, "$ssh $command |") || die "ssh: $!";
But I want to cd into a directory and search through multiple files.
My example below opens a single file. Is it possble to do what I
want?
###
#!/usr/bin/perl -w
use strict;
use warnings;
my $misc = '192.168.xxx.xxx.';
my $MAX = '100';
foreach my $x (1..$MAX) {
{
my $ssh = "ssh user\@$misc";
my $command = "perl -ne 'print' /root/file/log.txt";
open(SSH, "$ssh $command |") || die "ssh: $!";
print "connected to $misc$x\n";
while (my $current_line = <SSH>) {
my $QUERY = 'regex1_example';
my $QUERY_1 = 'regex2_example';
if ( $current_line =~ /COMPLETE: (?:$QUERY|$QUERY_1) .* from \S+
complete in (?:[3-9]{5}|[1-9]{6,9}) msecs/ ) {
print LOG "$current_line\n";
------------------------------
Date: Wed, 15 Apr 2009 16:14:42 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: using SSH without modules
Message-Id: <slrngucji2.j5u.tadmc@tadmc30.sbcglobal.net>
Nene <rodbass63@gmail.com> wrote:
> My object is to do a few things without the use of modules,
What is wrong with modules?
> my $command = "perl -ne 'print' /root/file/log.txt";
my $command = 'cat /root/file/log.txt';
or if wheel reinvention really is required for some odd reason:
my $command = 'perl -pe1 /root/file/log.txt';
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Wed, 15 Apr 2009 16:46:28 -0700 (PDT)
From: Nene <rodbass63@gmail.com>
Subject: Re: using SSH without modules
Message-Id: <f6e07d86-7f7b-451f-8507-05cd29529258@q16g2000yqg.googlegroups.com>
On Apr 15, 5:14=A0pm, Tad J McClellan <ta...@seesig.invalid> wrote:
> Nene <rodbas...@gmail.com> wrote:
> > My object is to do a few things without the use of modules,
>
> What is wrong with modules?
I, personally, love modules. But my manager doesn't.
>
> > my $command =3D "perl -ne 'print' /root/file/log.txt";
>
> =A0 =A0 my $command =3D 'cat /root/file/log.txt';
>
> or if wheel reinvention really is required for some odd reason:
>
> =A0 =A0 my $command =3D 'perl -pe1 /root/file/log.txt';
>
> --
> Tad McClellan
> email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
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 2342
***************************************
