[24608] in Perl-Users-Digest
Perl-Users Digest, Issue: 6784 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jul 9 18:05:42 2004
Date: Fri, 9 Jul 2004 15:05:06 -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 Fri, 9 Jul 2004 Volume: 10 Number: 6784
Today's topics:
aliased shell commands from perl script (Dmitry)
Re: double quotes vs. single quotes (was Re: hash as ar (Kevin Collins)
Re: double quotes vs. single quotes (was Re: hash as ar <nilram@hotpop.com>
Re: hash as argument (Kevin Collins)
Re: hash as argument (Anno Siegel)
Re: hash as argument <daedalus@videotron.ca>
Re: hash as argument (Anno Siegel)
Invalid Page Fault With Win32::GUI Under Win98 <rjkaes@flarenet.com>
Re: Negation of RegEx (Dan)
Re: Negation of RegEx <kkeller-usenet@wombat.san-francisco.ca.us>
Re: Newbie: How do I filter output to the screen and w (Mav)
Re: Problem with Archive::Tar <Joe.Smith@inwap.com>
Re: Problem with Archive::Tar <qa3653@email.mot.com>
Re: Problem with Archive::Tar <qa3653@email.mot.com>
Re: Regexp substitution problem - suggestions? <Joe.Smith@inwap.com>
Re: Regular expression to match surrounding parenthesis (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 9 Jul 2004 12:33:00 -0700
From: d_v_g@usa.net (Dmitry)
Subject: aliased shell commands from perl script
Message-Id: <e57e07f5.0407091133.2f2f058d@posting.google.com>
Hi All,
I has faced a problem of calling shell aliases from a perl script recently.
Web search gave me almost nothing, so I feel obliged to share my results
with community :-) The only way, which made perl script to execute my tcsh
aliases is below. I would very appreciate if anybody, who knows a better
method, posted it here.
Thanks in advance,
Dmitry
Example:
#! /bin/perl -w
# F.e. --- loopik.pl 'set aaa=`pwd`; cd dir1; nfail; cd $aaa; set aaa = ""' 2
# 'nfail' and 'cd' are aliases from ~/.aliases
use strict;
use Cwd;
use Env;
my( $n_args ) = 0;
my( $own_name ) = "";
my( $user_cmd ) = "";
my( $n_sec ) = 0;
my( $ali ) = "";
my( $kb ) = "";
$n_args = @ARGV;
$own_name = $0;
$own_name =~ s#.*/##; # Clear own name from full path info
if ( $n_args < 1 )
{
print( "\nUsage: $own_name <command> [interval in sec]\n" );
print( " Default interval is 3 sec.\n" );
print( " Type any key for stop. \n" );
exit();
}
$user_cmd = $ARGV[0];
if ( $n_args == 1 )
{
$n_sec = 3; # Default interval
}
else
{
$n_sec = $ARGV[1];
}
my( $tmp_fname ) = "KILLME.kill";
open( OUT, ">$tmp_fname" ) || die ( "Can't open file for writing: $!" );
print OUT "source ~/.aliases";
print OUT "\n";
print OUT $user_cmd;
print OUT "\n";
close( OUT );
use Term::ReadKey; # not a standard - should install CPAN ReadKey
my($char);
ReadMode('cbreak');
while ( !defined( $char = ReadKey(-1) ) )
{
system( "tcsh $tmp_fname" ); # execute commands from a file
sleep( $n_sec );
}
ReadMode('normal'); # restore normal tty settings
system( "rm $tmp_fname" );
------------------------------
Date: Fri, 09 Jul 2004 18:52:10 GMT
From: spamtotrash@toomuchfiction.com (Kevin Collins)
Subject: Re: double quotes vs. single quotes (was Re: hash as argument)
Message-Id: <slrncetqap.9l0.spamtotrash@doom.unix-guy.com>
In article <slrncetb3u.93h.tadmc@magna.augustmail.com>, Tad McClellan wrote:
> Joe Smith <Joe.Smith@inwap.com> wrote:
>> Sherm Pendley wrote:
>>> And don't use double-quotes on strings unless it's necessary.
>>
>> Has Larry Wall made a statement on this?
>
>
> Not that I know of, but I've heard both Randal Schwartz and
> Tom Christiansen say that they always use double quotes...
>
> I'm of the "use double quotes only if you _need_ double quotes" camp,
> because I'm just a Regular Guy and not a Genius Hacker.
>
> The rules are different between those demographics. :-)
>
> I need all the "brain cycles" available to solve the problem,
> I don't have excess that I can spend on checking for edge cases.
>
>
>
> The programmer's choice of quotes is a note to (him|her)self:
>
> "interpolation or backslash escapes are here!"
> or
> 'nothing special going on here'
Its funny, because my own mental rule is:
"normal string with interpolation if needed"
or
'definitely do not interpolate'
In other words, I typically ONLY use single-quotes when I want to make it clear
that there is some thing that I *don't* want interpolated, like:
my $var = 'this string contains a literal $var';
> Double quotes without interpolation or backslash escapes tricks
> the maintenance programmer into spending more debugging time on
> that string than is necessary.
>
> (assuming a string of more than just a few characters)
>
>
>> Using double quotes in a situation where single quotes could also
> ^^^^^^^^^^^
>> be used is not a programming error.
>
>
> But then you have to remember to analyse the situation everytime
> you want to quote a string.
>
> $re = "func\(\)";
> print "matched [$1]\n" if /($re)/; # matches "func" without parens
>
>
> Gets false matches with "", would have worked fine the 1st time with ''.
>
>
>> It is a matter of style.
>
>
> Yes, but that is what style choices are for.
>
> Either to make debugging easier, or to reduce the chances of
> inserting bugs in the first place.
>
> The above-mentioned "rule" does both.
Kevin
------------------------------
Date: 09 Jul 2004 14:40:49 -0500
From: Dale Henderson <nilram@hotpop.com>
Subject: Re: double quotes vs. single quotes (was Re: hash as argument)
Message-Id: <87pt75m0ji.fsf@camel.tamu-commerce.edu>
>>>>> "TM" == Tad McClellan <tadmc@augustmail.com> writes:
TM> Joe Smith <Joe.Smith@inwap.com> wrote:
TM> The programmer's choice of quotes is a note to (him|her)self:
TM> "interpolation or backslash escapes are here!"
TM> or
TM> 'nothing special going on here'
This makes me wonder if perhaps 'This is a string' is faster than
"This is a string" because in the first example the interpreter
can just use the string as is. But in the second the interpreter
must scan the string looking for interpolation or backslash
and construct a new string to use.
--
Dale Henderson
"Imaginary universes are so much more beautiful than this stupidly-
constructed 'real' one..." -- G. H. Hardy
------------------------------
Date: Fri, 09 Jul 2004 18:46:11 GMT
From: spamtotrash@toomuchfiction.com (Kevin Collins)
Subject: Re: hash as argument
Message-Id: <slrncetpvj.9l0.spamtotrash@doom.unix-guy.com>
In article <ccm3tf$9ra$1@mamenchi.zrz.TU-Berlin.DE>, Anno Siegel wrote:
[snip]
> Thus, a set of stylistic conventions gives a language a dimension of
> expressiveness it wouldn't have without it. That is a Good Thing.
> The preference of '' over "" and of sub() over &sub belong in this
> category.
Use of sub() and &sub is not "preference" - they have specifically different
behaviors.
>> Pointing to the fact that many people would not even look at the code
>> because they don't like the "prefer double-quote" style is fine, it's good
>> to know, but asking someone to fix something that is not broken is another.
>> It's not like the thing is an ancien obscur use like using $mains'var
>> instead of $main::var. "If it ain't broke don't fix it".
>
> It's not about "correct" or "broken", it's about clarity.
>
> Anno
Kevin
------------------------------
Date: 9 Jul 2004 19:31:36 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: hash as argument
Message-Id: <ccmrqo$ne8$2@mamenchi.zrz.TU-Berlin.DE>
Kevin Collins <spamtotrash@toomuchfiction.com> wrote in comp.lang.perl.misc:
> In article <ccm3tf$9ra$1@mamenchi.zrz.TU-Berlin.DE>, Anno Siegel wrote:
> [snip]
> > Thus, a set of stylistic conventions gives a language a dimension of
> > expressiveness it wouldn't have without it. That is a Good Thing.
> > The preference of '' over "" and of sub() over &sub belong in this
> > category.
>
> Use of sub() and &sub is not "preference" - they have specifically different
> behaviors.
...as do "" and ''. If it matters, there is no choice, and no room for
preference. But in many, many cases both choices have (provably) the
same result. It is in these cases, where the programmer has to make
a choice between equivalent notations, that a preference rule helps.
Anno
------------------------------
Date: Fri, 9 Jul 2004 15:54:46 -0400
From: "Daedalus" <daedalus@videotron.ca>
Subject: Re: hash as argument
Message-Id: <CHCHc.41111$_p5.997902@wagner.videotron.net>
> Some more examples of saying that "something special" is going
> on when nothing special is going on:
>
> m/RE/s; # when RE does not contain a dot
>
> m/RE/m; # when RE does not contain ^ or $ anchors
>
> printf "%s\n", 'Hello World'; # printf() w/same formatting as print()
It makes me think of one thing. Funny how the perl's default seems to be the
double-quotes-like style. qx//, qw//, m//, s///, qr//, <<EOF. And if you
need them to behave like single-quotes you have to specify: qx' ' or
<<'EOF'. May not be a coincidence if some poeple think as perl itself and
uses double-quotes unless singles are needed.
DAE
------------------------------
Date: 9 Jul 2004 21:25:52 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: hash as argument
Message-Id: <ccn2h0$rft$1@mamenchi.zrz.TU-Berlin.DE>
Daedalus <daedalus@videotron.ca> wrote in comp.lang.perl.misc:
> > Some more examples of saying that "something special" is going
> > on when nothing special is going on:
> >
> > m/RE/s; # when RE does not contain a dot
> >
> > m/RE/m; # when RE does not contain ^ or $ anchors
> >
> > printf "%s\n", 'Hello World'; # printf() w/same formatting as print()
>
>
> It makes me think of one thing. Funny how the perl's default seems to be the
> double-quotes-like style. qx//, qw//, m//, s///, qr//, <<EOF. And if you
> need them to behave like single-quotes you have to specify: qx' ' or
> <<'EOF'. May not be a coincidence if some poeple think as perl itself and
> uses double-quotes unless singles are needed.
You are right in observing that with Perl's operators the default is
double-quotish behavior. But that doesn't mean it's good style to
follow suit. Perl's defaults are geared to be useful in small, casual
programs, where style is of less concern than otherwise. Defaults
are there to keep small programs small.
A larger program can afford to override them, and often should. A
particularly notable case is that warnings and strictures are off by
default. Yet there is largely agreement that it is good style to
switch them on in anything substantial. A similar argument can be
made for the use of single quotes when they yield the same result
as doubles. Or for "sub()" over "&sub" when they are exchangeable.
Anno
------------------------------
Date: Fri, 09 Jul 2004 16:27:31 -0400
From: Robert James Kaes <rjkaes@flarenet.com>
Subject: Invalid Page Fault With Win32::GUI Under Win98
Message-Id: <pan.2004.07.09.20.27.26.686362@flarenet.com>
Hi All,
I'm trying to experiment with Win32::GUI using ActiveState Perl 5.8.4
(build 810) under Windows 98. I'm trying to follow the examples in the
Win32::GUI tutorial, but the first example in the tutorial is failing.
use Win32::GUI;
use strict;
use warnings;
my $main = Win32::GUI::Window->new(-name => "Main", -width => 110, -height => 100);
# This line is failing
$main->AddLabel(-text => "Hello, world");
$main->Show();
Win32::GUI::Dialog();
exit;
# terminate the message loop when the window is closed
sub Main_Terminate { -1 }
The AddLabel line is causing an illegal operation error with the
following message:
PERL caused an invalid page fault in
module MSVCRT.DLL at 0167:78002fc5.
I installed Win32::GUI using the PPM system. If I removed the AddLabel
line, the script runs and displays the empty window.
Has any one else experienced a problem like this? Is this a known
problem, with a known work-around? Does Win32::GUI just not work under
Windows 98? Thanks for any help you can provide.
-- Robert
--
Robert James Kaes --- Flarenet Inc. --- (519) 426-3782
http://www.flarenet.com/consulting/
* Putting the Service Back in Internet Service Provider *
------------------------------
Date: 9 Jul 2004 11:54:52 -0700
From: dan_yuan@trendmicro.com (Dan)
Subject: Re: Negation of RegEx
Message-Id: <4c135583.0407091054.260e4256@posting.google.com>
I will put regular expressions in a script. No sign "!~" or "=~" allowed in there.
Dan
Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote in message news:<v3lkcc.us3.ln@goaway.wombat.san-francisco.ca.us>...
> -----BEGIN xxx SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2004-07-08, Dan <dan_yuan@trendmicro.com> wrote:
> > But, I am not allowed to use "!~", I can only use "=~" for this
> > problem,
>
> Why are you not allowed to use !~? Sounds like homework to me.
>
> - --keith
>
> - --
> kkeller-usenet@wombat.san-francisco.ca.us
> (try just my userid to email me)
> AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
>
> -----BEGIN xxx SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFA7de+hVcNCxZ5ID8RAmYuAJ0SHm1aUirkhpKPU+WdMHoaZnxopwCggvpE
> 4krTCU8/idIytSlF109dDes=
> =NaGl
> -----END PGP SIGNATURE-----
------------------------------
Date: Fri, 9 Jul 2004 12:09:23 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: Negation of RegEx
Message-Id: <3hqmcc.i28.ln@goaway.wombat.san-francisco.ca.us>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
On 2004-07-09, Dan <dan_yuan@trendmicro.com> wrote:
[TOFU snipped]
> Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote in message news:<v3lkcc.us3.ln@goaway.wombat.san-francisco.ca.us>...
>> On 2004-07-08, Dan <dan_yuan@trendmicro.com> wrote:
>> > But, I am not allowed to use "!~", I can only use "=~" for this
>> > problem,
>>
>> Why are you not allowed to use !~? Sounds like homework to me.
> I will put regular expressions in a script. No sign "!~" or "=~"
> allowed in there.
Above you said you could use =~. Perhaps you can clarify your
needs more thoroughly?
- --keith
- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
-----BEGIN xxx SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFA7u1ghVcNCxZ5ID8RApzjAJ9bfWxhNnQXnvhuZ8i85rQ6HAKlZwCgi74k
I1Bk5YENJOfknoO4mObD9vE=
=3cj7
-----END PGP SIGNATURE-----
------------------------------
Date: 9 Jul 2004 14:56:37 -0700
From: mluvw47@yahoo.com (Mav)
Subject: Re: Newbie: How do I filter output to the screen and writing the orginal output to a file?
Message-Id: <dfaafecd.0407091356.656f4bf0@posting.google.com>
Cool, I think second will be better instead of just die.
'coz I don't want to kill the script that is calling.
Thanks a lot, Gunnar.
You answers are very helpful,
Mav
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in message news:<2l672aF9519nU1@uni-berlin.de>...
> Mav wrote:
> > Gunnar Hjalmarsson wrote:
> >> You can check the return value from close():
> >>
> >> close $proc or die "Build failed $! $?";
> >
> > I probably don't use die to since I need to get the Failed
> > ...
> > close BUILDLOG;
> > close $proc;
> > #Check Build Result
> > if ($? == 0) {
> > $buildResult = "Passed";
> > }
> > else {
> > $buildResult = "Failed";
> > }
> >
> > Do you think that is a better way?
>
> If you think it is, I have no reason to object. :)
>
> A closer equivalent to
>
> $buildResult = system(@args);
>
> would be to just do:
>
> close $proc;
> $buildResult = $?;
>
> What makes most sense probably depends on how you want to use
> $buildResult.
------------------------------
Date: Fri, 09 Jul 2004 18:05:53 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Problem with Archive::Tar
Message-Id: <58BHc.49824$%_6.31377@attbi_s01>
Glenn Jackman wrote:
> did you read in the Archive::Tar documentation the paragraph that reads:
>
> Although rich in features, it is known to not work on Win32
> platforms. On those platforms, Archive::Tar will silently
> and transparently fall back to the Archive::Tar::Win32
> manpage. Please refer to that manpage if you are on a Win32
> platform.
Which version of Archive::Tar are you using? I don't see that message
in http://search.cpan.org/~kane/Archive-Tar-1.10/lib/Archive/Tar.pm but I did
notice that http://search.cpan.org/src/KANE/Archive-Tar-1.10/README has this:
* important changes for version 0.071
It fixes a bunch of bugs, implements POSIX-style long pathnames and
adds a couple of useful methods. It has also been verified to work on
Win32.
-Joe
------------------------------
Date: Fri, 09 Jul 2004 15:19:17 -0500
From: Mark Newman <qa3653@email.mot.com>
Subject: Re: Problem with Archive::Tar
Message-Id: <ccmu33$nfl$2@avnika.corp.mot.com>
I was using 1.08, but just now upgraded to 1.10. The problem still
exists, unfortunately.
Joe Smith wrote:
> Glenn Jackman wrote:
>
>> did you read in the Archive::Tar documentation the paragraph that reads:
>>
>> Although rich in features, it is known to not work on Win32
>> platforms. On those platforms, Archive::Tar will silently
>> and transparently fall back to the Archive::Tar::Win32
>> manpage. Please refer to that manpage if you are on a Win32
>> platform.
>
>
> Which version of Archive::Tar are you using? I don't see that message
> in http://search.cpan.org/~kane/Archive-Tar-1.10/lib/Archive/Tar.pm
> but I did
> notice that http://search.cpan.org/src/KANE/Archive-Tar-1.10/README
> has this:
>
> * important changes for version 0.071
>
> It fixes a bunch of bugs, implements POSIX-style long pathnames and
> adds a couple of useful methods. It has also been verified to work on
> Win32.
>
> -Joe
------------------------------
Date: Fri, 09 Jul 2004 16:16:03 -0500
From: Mark Newman <qa3653@email.mot.com>
Subject: Re: Problem with Archive::Tar
Message-Id: <ccn1e0$o2a$1@avnika.corp.mot.com>
Sorry to reply to my own message, but after a lot of playing around, it
seems that the directory structure IS being maintained, it's some sort
of issue with using Winzip to look at the archive that is the problem.
If I use tar.exe to examin/extract the archive, I see the directory
structure that I desired.... Weird.
Thanks for everyone's help.
Mark Newman wrote:
> I was using 1.08, but just now upgraded to 1.10. The problem still
> exists, unfortunately.
>
> Joe Smith wrote:
>
>> Glenn Jackman wrote:
>>
>>> did you read in the Archive::Tar documentation the paragraph that
>>> reads:
>>>
>>> Although rich in features, it is known to not work on Win32
>>> platforms. On those platforms, Archive::Tar will silently
>>> and transparently fall back to the Archive::Tar::Win32
>>> manpage. Please refer to that manpage if you are on a Win32
>>> platform.
>>
>>
>>
>> Which version of Archive::Tar are you using? I don't see that message
>> in http://search.cpan.org/~kane/Archive-Tar-1.10/lib/Archive/Tar.pm
>> but I did
>> notice that http://search.cpan.org/src/KANE/Archive-Tar-1.10/README
>> has this:
>>
>> * important changes for version 0.071
>>
>> It fixes a bunch of bugs, implements POSIX-style long pathnames and
>> adds a couple of useful methods. It has also been verified to work on
>> Win32.
>>
>> -Joe
>
>
------------------------------
Date: Fri, 09 Jul 2004 18:27:18 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Regexp substitution problem - suggestions?
Message-Id: <asBHc.23693$WX.11118@attbi_s51>
JK wrote:
> my $parm1 = substr($_,$str,$len);
> $_ =~ s/$parm1/<a href="$parm1">$parm1<\/a>/ig; # This is the problem line
You don't need "=~" when working with $_.
Anytime you have a variable as the first part of s///, you should carefully
consider using \Q or \Q and \E around the variable.
s/\Q$parm1/<a href="$parm1">$parm1<\/a>/ig; # Quote specials in $parm1
-Joe
------------------------------
Date: 9 Jul 2004 19:21:18 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Regular expression to match surrounding parenthesis
Message-Id: <ccmr7e$ne8$1@mamenchi.zrz.TU-Berlin.DE>
Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote in comp.lang.perl.misc:
> [A complimentary Cc of this posting was sent to
> Anno Siegel
> <anno4000@lublin.zrz.tu-berlin.de>], who wrote in article
> <ccj6ne$f4b$1@mamenchi.zrz.TU-Berlin.DE>:
> > The mathematicians who work with regular expressions are just a club of
> > pedants?
>
> Can't answer this question; never saw a mathematician who works with
> regular expressions. 1/5 ;-)
Okay, but some work with grammars and like to distinguish regular grammars,
which are defined using regular expressions.
This is, BTW, the reason why the mathematical notion of regular expressions
was never amended with backreferences, the way computer implementations are.
In the theory of grammars and languages, it is the distinguishing property
of regularity that some constructs (like nested parentheses, but even
simpler ones) cannot be parsed. Extending the capabilities of regular
expressions would spoil the game.
> But in general, [with a few exceptions] mathematicians do not mind the
> same word having different meanings in different contexts. Too few
> words, too many things to work over....
Not at all. Mathematics has practiced operator overloading long before
it was named thus.
Nor do I have a problem with "regular expression" meaning two different
things in different disciplines. But the case is not quite like "index"
meaning two essentially unrelated things to a mathematician and a librarian.
The computer notion of "regex" was derived from the earlier mathematical
model and is essentially (down to the notation) the same thing.
Being practitioners, computer people soon invented shortcuts and extended
notations in their hackish ways. Many of these (like character classes,
or {m,n} quantifiers) are inessential and don't change the power of
what a regex can do, only the ease of expressing it. The introduction
of backreferences *does* change the expressive power of regexes, in a
way that was, and still is, deliberately excluded from the mathematical
definition. That can lead to contradictory statements about "regular
expressions", which, depending on who is speaking, are both correct.
This particular relationship deserves an explanation when it comes up.
Anno
------------------------------
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 V10 Issue 6784
***************************************
