[22303] in Perl-Users-Digest
Perl-Users Digest, Issue: 4524 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Feb 6 18:13:22 2003
Date: Thu, 6 Feb 2003 15:12:30 -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, 6 Feb 2003 Volume: 10 Number: 4524
Today's topics:
Select Box (Jum)
Re: Select Box <glex_nospam@qwest.net>
Re: Select Box <flavell@mail.cern.ch>
sharing variables <cyberjeff@sprintmail.com>
Simple regexp gots me stuck... (OJ)
Re: Simple regexp gots me stuck... <mthunter@students.uiuc.edu>
Re: Simple regexp gots me stuck... (Anno Siegel)
Re: Some embedded Perl (ala libperl.a) questions... <goldbb2@earthlink.net>
Re: Splitting lines from a temporary buffer <goldbb2@earthlink.net>
Re: Splitting lines from a temporary buffer <knewman00@earthlink.net>
Re: Splitting lines from a temporary buffer <goldbb2@earthlink.net>
Re: Splitting lines from a temporary buffer <uri@stemsystems.com>
Re: strange localtime return Andrew Lee
Re: string in datei <comesefosse@ntani.firenze.linux.it>
Re: Too many greps <goldbb2@earthlink.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 6 Feb 2003 12:58:13 -0800
From: anjum_merchant@yahoo.com (Jum)
Subject: Select Box
Message-Id: <29228da5.0302061258.37320c6f@posting.google.com>
Greetings All,
I have a question regarding using a select box. What I hope to
accomplish is to use the select to capture the value the user has
selected.
<select name='$usersChoice'>
<option value='value1'>value1</option>
<option value='value2'>value2</option>
<option value='value3'>value3</option>
</select>
The problem is that, I believe the form has to be refreshed in order
to capture what the user has selected. However upon doing so, the
values are flushed and I lose my selected value. Does anyone know how
to get around this problem?
Thanks,
--jum
------------------------------
Date: Thu, 06 Feb 2003 15:13:54 -0600
From: Jeff D Gleixner <glex_nospam@qwest.net>
Subject: Re: Select Box
Message-Id: <wcA0a.58$yr3.50749@news.uswest.net>
Jum wrote:
> Greetings All,
> I have a question regarding using a select box. What I hope to
> accomplish is to use the select to capture the value the user has
> selected.
>
> <select name='$usersChoice'>
> <option value='value1'>value1</option>
> <option value='value2'>value2</option>
> <option value='value3'>value3</option>
> </select>
>
> The problem is that, I believe the form has to be refreshed in order
> to capture what the user has selected. However upon doing so, the
> values are flushed and I lose my selected value. Does anyone know how
> to get around this problem?
Use the CGI.pm module, available on your nearest CPAN.
perldoc CGI
------------------------------
Date: Thu, 6 Feb 2003 22:32:44 +0100
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: Select Box
Message-Id: <Pine.LNX.4.53.0302062220560.10202@lxplus086.cern.ch>
On Feb 6, Jum inscribed on the eternal scroll:
> I have a question regarding using a select box.
You don't appear to have a Perl question.
> What I hope to accomplish is to use the select to capture the value
> the user has selected.
Elementary use of CGI. Take a look at some of the examples in the
CGI.pm documentation.
> <select name='$usersChoice'>
> <option value='value1'>value1</option>
> <option value='value2'>value2</option>
> <option value='value3'>value3</option>
> </select>
OK so far...
> The problem is that, I believe the form has to be refreshed in order
> to capture what the user has selected.
I don't understand what you're getting at here, and the crystal ball
is cloudy.
> Does anyone know how to get around this problem?
I don't yet know what you think the problem is. But I suspect you're
trying to achieve something that you haven't yet revealed - you've
somehow got onto a side-track, and now you're stuck, but we don't
quite know where.
Still, this would be more appropriate as a question on a CGI-specific
group, like comp.infosystems.www.authoring.cgi (check its
automoderation instructions before posting). I'd suggest describing
your actual requirement (rather than your partially worked out and
apparently problematical solution) there.
good luck
------------------------------
Date: Thu, 06 Feb 2003 22:13:13 GMT
From: Jeff Thies <cyberjeff@sprintmail.com>
Subject: sharing variables
Message-Id: <3E42DE80.4DB04C4F@sprintmail.com>
I have a configuration file with site variables in it, I call it from
my script:
require 'variables.var';
# I also have a module that also needs these variables
use someModule;
package someModule; # works without this line
# someModule has this line:
require 'variables.var';
Now, my script can no longer access those variables in variables.var
Why is that? How do I set this up so my script can use variables.var and
someModule can also use variables.var? How do I share namespaces?
Jeff
------------------------------
Date: 6 Feb 2003 12:30:00 -0800
From: orljustin@aol.com (OJ)
Subject: Simple regexp gots me stuck...
Message-Id: <77d3a68b.0302061229.6cf27900@posting.google.com>
Heya,
Can't figure out why this does not return the image path only in $1. Any clue?
#!/usr/local/bin/perl
$t = "img SRC=\"/Images/tmp.gif\" ALT=\"avast ye scurvy dogs\"";
$t=~/src.*?=.*?"(.*)[^ ]?"/i;
print "\n $1 \n";
result:
/Images/tmp.gif" ALT="avast ye scurvy dogs
Thanks for your patience....
oj
------------------------------
Date: Thu, 06 Feb 2003 20:32:43 GMT
From: Mike Hunter <mthunter@students.uiuc.edu>
Subject: Re: Simple regexp gots me stuck...
Message-Id: <slrnb45hp2.3r6.mthunter@ux8.cso.uiuc.edu>
On 6 Feb 2003 12:30:00 -0800, OJ wrote:
> Heya,
>
> Can't figure out why this does not return the image path only in $1. Any clue?
>
> #!/usr/local/bin/perl
>
> $t = "img SRC=\"/Images/tmp.gif\" ALT=\"avast ye scurvy dogs\"";
> $t=~/src.*?=.*?"(.*)[^ ]?"/i;
> print "\n $1 \n";
>
>
> result:
> /Images/tmp.gif" ALT="avast ye scurvy dogs
>
> Thanks for your patience....
Read the regular expression from right to left. Then design it from
right to left :)
------------------------------
Date: 6 Feb 2003 20:58:27 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Simple regexp gots me stuck...
Message-Id: <b1ui9j$bbg$3@mamenchi.zrz.TU-Berlin.DE>
OJ <orljustin@aol.com> wrote in comp.lang.perl.misc:
> Heya,
>
> Can't figure out why this does not return the image path only in $1. Any clue?
>
> #!/usr/local/bin/perl
>
> $t = "img SRC=\"/Images/tmp.gif\" ALT=\"avast ye scurvy dogs\"";
> $t=~/src.*?=.*?"(.*)[^ ]?"/i;
^^^^
The underlined part captures everything after '"' up to the last '"' in
a greedy way, since the following "[^ ]?" is optional.
> print "\n $1 \n";
>
>
> result:
> /Images/tmp.gif" ALT="avast ye scurvy dogs
...as it should. This should work, and is in line with the use of
non-greedy matching elsewhere:
$t=~/src.*?=.*?"(.*)?"/i;
Not that it's anything like robust...
Anno
------------------------------
Date: Thu, 06 Feb 2003 14:30:19 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Some embedded Perl (ala libperl.a) questions...
Message-Id: <3E42B7CB.E11AC884@earthlink.net>
Asfand yar Qazi wrote:
>
> Benjamin Goldberg wrote:
> > Asfand yar Qazi wrote:
> >
> >>I am using embedded Perl inside a game I'm developing (love that
> >>Class::Classless...)
> >>
> >>I currently evaluate perl expressions inside a 'temporary' package
> >>to avoid namespace pollution. Which is good. Problem is that when
> >>I evaluate 'exit', my program exits! How do I stop this behaviour?
> >
> > Either define a sub CORE::GLOBAL::exit, and make sure that your
> > *actual* exit is called as CORE::exit, or define an exit sub in your
> > temporary package, else use Safe.pm and evaluate the code inside a
> > safe compartment which has the exit opcode disabled.
>
> Safe.pm, huh? I think I'll use that... many thanks.
>
> > Where are these perl expressions coming from, anyway?
>
> A 'console' (ala Quake '~' key)
How trustworthy is the person typing on the console?
Running the typed-in-code in a Safe compartment prevents such stuff as:
$Some::Package::my_score = 10000;
Which is *probably* all you need, assuming that the only goal is to
prevent the user from cheating... *but* there may be other things to
worry about, such as the stuff described in the "Some Safety Issues"
part of the Safe.pm documentation.
--
"So, who beat the clueless idiot today?"
"Well, we flipped for it, but when Kuno
landed, he wasn't in any shape to fight."
"Next time, try flipping a *coin.*"
------------------------------
Date: Thu, 06 Feb 2003 14:58:59 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Splitting lines from a temporary buffer
Message-Id: <3E42BE83.B00DC968@earthlink.net>
Kevin Newman wrote:
>
> Hi all,
>
> I'm trying to split lines from a temporary buffer. The steps are:
> 1. Read in a chunk of data to a buffer from a file
Actually, step 1 is "try to read a chunk of data, if it fails, goto step
4"
> 2. Split to some terminator
Nope -- step two is "match and capture data up to and including the
terminator, and remove it; if no match is made, goto step 1" The
match-capture-and-remove is done as a single step, with s/// and
capturing parens.
> 3. Then substitute nothing(?) using the value assigned from step 2
That's done as part of step 2.
Step 3 is "process the data, then go back to step 2"
> 4. Refill the buffer with more data (code not shown)
Step 4 is process any data left in the buffer, then go on to any other
tasks your program has.
[snip code]
Try this:
open( FH, "<", $filename ) or die "Couldn't open $filename: $!";
local $_ = ""; # makes the code simpler than using $buffer.
while( sysread FH, $_, 4096, length ) {
while( s/^(.*?)(?:\015\012|[\000\012]|\015(?!\z))/s ) {
print "[$1]\n";
}
}
if( s/\015\z// ) {
print "[$_]\n";
} elsif( length ) {
warn "Incomplete last line";
print "[$_]\n";
}
__END__
[untested]
--
"So, who beat the clueless idiot today?"
"Well, we flipped for it, but when Kuno
landed, he wasn't in any shape to fight."
"Next time, try flipping a *coin.*"
------------------------------
Date: Thu, 06 Feb 2003 20:18:58 GMT
From: Kevin Newman <knewman00@earthlink.net>
Subject: Re: Splitting lines from a temporary buffer
Message-Id: <3E42CCCC.3080006@earthlink.net>
Anno Siegel wrote:
> Kevin Newman <knewman00@earthlink.net> wrote in comp.lang.perl.misc:
>
>>Hi all,
>>
>>I'm trying to split lines from a temporary buffer. The steps are:
>
>
> First off, why do you want to do this? Perl's line input does exactly
> that, and it's far more efficient and robust than anything programmed
> in Perl.
>
I’m working with very large files with questionable line terminators.
>
>>1. Read in a chunk of data to a buffer from a file
>>2. Split to some terminator
>>3. Then substitute nothing(?) using the value assigned from step 2
>>4. Refill the buffer with more data (code not shown)
>
>
> That's no way to deal with a buffer. You re-fill it for every line,
> which is wasteful and contrary to its purpose. You want to deliver
> all complete lines that are in the buffer, then move the incomplete
> line to the beginning and re-fill from that point.
>
> You have a problem when a line is too long to fit in the buffer.
>
Didn't think that far...
>
>>But, when I try these steps the first line is split from the buffer then
>>the program loops until I hit control-C (see code below). My questions
>>are why does this not work and is there a better approach to creating a
>>"refillable" buffer. Any suggestions?
>
>
> [...]
>
>
>>use strict;
>>my $filename = $ARGV[0];
>>my $terminator = qr/\015\012|[\015\012\000]/;
>
>
> Ah, you want to allow multiple line-terminators. Multi-byte ones too.
> That's going to be hard. What if the last byte of a buffer is "\015"
> from a "\015\012" combination? Your regex would get that wrong.
> (Apart from the fact that you don't use it later on.)
Yep.
>
> There is usually a better way of dealing with multiple line terminators,
> taking into account that a single file usually comes with only one type.
> Look into IO-layers (or -disciplines, as they used to be called).
>
>
>>open (DATAFILE, "$filename") || die "Could not open file $filename $!\n";
>>my $bytes_read = read( DATAFILE, my $buffer , 5000 );
>>while (1)
>
>
> Well, this is an endless loop. How did you expect to escape it?
> It would make more sense to say "while ( $buffer )".
>
>
>>{
>> my ($line) = split (/\n/,$buffer);
That explains why my @line = split (/\n/,$buffer); works
>
>
> This assigns to $line the first line in $buffer (if there is one). The
> other lines are thrown away.
>
>
>> $buffer =~ s/\Q$line//;
>
>
> Yikes. This is a weird way of shortening a string. The common way would
> use substr() in one way or other.
>
> substr( $buffer, 0, length $line) = '';
>
> (This being clpm, someone will now benchmark this and find that s/// is
> faster.)
<g> I started with substr , but this "looked" intresting.
>
>
>> print "$buffer";
>>}
>
>
> [data lines snipped]
>
> I don't think it's worth while to do this in Perl. If you really need
> a regex as a line-terminator, I bet there's a module on CPAN.
>
> Anno
I have a conventional way of dealing with these variations, but I was
trying a new approach to the problem to make my code easier to
understand and maintained. I think I'll sleep on this one for a month
or two and come up with yet another approach. In the meantime I'll also
have a look on CPAN to see if there is something that already exists.
Thanks,
kln
------------------------------
Date: Thu, 06 Feb 2003 16:17:31 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Splitting lines from a temporary buffer
Message-Id: <3E42D0EB.B1EB6A20@earthlink.net>
Anno Siegel wrote:
>
> Kevin Newman <knewman00@earthlink.net> wrote in comp.lang.perl.misc:
> > Hi all,
> >
> > I'm trying to split lines from a temporary buffer. The steps are:
>
> First off, why do you want to do this? Perl's line input does exactly
> that, and it's far more efficient and robust than anything programmed
> in Perl.
>
> > 1. Read in a chunk of data to a buffer from a file
> > 2. Split to some terminator
> > 3. Then substitute nothing(?) using the value assigned from step 2
> > 4. Refill the buffer with more data (code not shown)
>
> That's no way to deal with a buffer. You re-fill it for every line,
> which is wasteful and contrary to its purpose. You want to deliver
> all complete lines that are in the buffer, then move the incomplete
> line to the beginning and re-fill from that point.
Hmm... In my code, I perform a loop that goes:
while( sysread FF, $_, 4096, length ) {
while( s/^(.*?)(?:...terminators...)/s ) {
This removes complete lines, and fills the buffer starting after the
most recent incomplete line...
But... I seem to recall that perl internally keeps an extra pointer to
the beginning of the string, within a byte array, so that it can
efficiently remove bytes from the beginning, just by moving the pointer.
And AFAIK, sysread will grow the string at the end... Does those bytes
at the front of the string get lost?
> You have a problem when a line is too long to fit in the buffer.
>
> > But, when I try these steps the first line is split from the buffer
> > then the program loops until I hit control-C (see code below).
That's be cause you do while(1) and never exit the loop.
[snip]
> > $buffer =~ s/\Q$line//;
>
> Yikes. This is a weird way of shortening a string. The common way
> would use substr() in one way or other.
>
> substr( $buffer, 0, length $line) = '';
>
> (This being clpm, someone will now benchmark this and find that s///
> is faster.)
Actually, even better might be to assign to $buffer directly... E.g. I
could probably change my code to:
my $terminator = qr/\015\012|[\015\012\000]/;
my $buffer = "";
while( sysread FH, $buffer, 4096, length $buffer ) {
my @lines = split /$terminator(?!\z)/, $buffer, -1;
$buffer = pop @lines;
print "[$_]\n" for @lines;
}
if( length $buffer ) {
my @lines = split /$terminator/, $buffer, -1; # no (?!\z)
if( length $lines[-1] ) { warn "Incomplete last line" }
else { pop @lines }
print "[$_]\n" for @lines;
}
There's now no need to "remove" anything from $buffer.
Hmm, this code looks rather simpler, ne?
[snip]
> I don't think it's worth while to do this in Perl. If you really need
> a regex as a line-terminator, I bet there's a module on CPAN.
Actually, if you want a regex as a line-terminator, consider using awk,
rather than perl... awk has that as one of it's built-in features.
Hmm, or if you *really* need speed, consider 'lex' or 'flex'. :)
--
"So, who beat the clueless idiot today?"
"Well, we flipped for it, but when Kuno
landed, he wasn't in any shape to fight."
"Next time, try flipping a *coin.*"
------------------------------
Date: Thu, 06 Feb 2003 21:09:16 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Splitting lines from a temporary buffer
Message-Id: <x7fzr1i0as.fsf@mail.sysarch.com>
>>>>> "BG" == Benjamin Goldberg <goldbb2@earthlink.net> writes:
BG> Actually, even better might be to assign to $buffer directly... E.g. I
BG> could probably change my code to:
BG> my $terminator = qr/\015\012|[\015\012\000]/;
BG> my $buffer = "";
BG> while( sysread FH, $buffer, 4096, length $buffer ) {
BG> my @lines = split /$terminator(?!\z)/, $buffer, -1;
BG> $buffer = pop @lines;
BG> print "[$_]\n" for @lines;
BG> }
BG> if( length $buffer ) {
BG> my @lines = split /$terminator/, $buffer, -1; # no (?!\z)
BG> if( length $lines[-1] ) { warn "Incomplete last line" }
BG> else { pop @lines }
BG> print "[$_]\n" for @lines;
BG> }
BG> There's now no need to "remove" anything from $buffer.
BG> Hmm, this code looks rather simpler, ne?
that is similar to my code in file::readbackwards. it supports a regex
delim but the main diff is that is prepends the newly read block to the
buffer.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
Damian Conway Perl Classes - January 2003 -- http://www.stemsystems.com/class
------------------------------
Date: Thu, 06 Feb 2003 15:58:56 -0500
From: Andrew Lee
Subject: Re: strange localtime return
Message-Id: <ihi54v0q7jm038uqc16rb3o0f6fb58sadv@4ax.com>
On 5 Feb 2003 23:04:15 -0800, shadowfax@optonline.net (Shadowfax) wrote:
>Thanks all for the reply.
>
>I make some progress but stuck on below error again, it seems all the
>variable was initialized already.
>"Use of uninitialized value in addition (+) at E:\temp\rename.pl line
>29 "
>
>Thanks,
>Shadowfax
>
>use strict;
>use warnings;
>use Time::localtime;
>use File::stat;
>
>my %file_date=();
You don't have to init %file_date to an empty list.
>my $YYYYMMDD;
>my $org_file;
>my $mtime;
>my $new_filename;
>my %month_translate=("Jan","01","Feb","02","Mar","03","Apr","04","May","05","Jun","06","Jul","07","Aug","08","Sep","09","Oct","10","Nov","11","Dec","12");
>my $org_dir="E:/temp/v";
>
>opendir(DIR,$org_dir)||die "can't open original directory $org_dir" ;
>my @org_files=readdir(DIR) ;
>closedir(DIR) ;
>
>foreach $org_file(@org_files)
>{
> $mtime=ctime(stat("$org_dir/$org_file")->mtime);
> my ($wday,$mon,$mday,$min,$year)=split(/\s+/,$mtime);
> $YYYYMMDD = sprintf ("%4d%02d%02d", $year, $month_translate{$mon},
>$mday);
>
># print "$org_file\n";
># print "Modified Time: $YYYYMMDD\n";
> while (undef $file_date{$YYYYMMDD}) {
> $file_date{$YYYYMMDD}=0;
Why are you testing to see if $file_date is undefined? of course it is
... no need to set it to 0 ... it islready undefined! :-)
> }
> $file_date{$YYYYMMDD} = $file_date{$YYYYMMDD} + 1;
just say $file_date{$YYYYMMDD}++ .. less typing -- not sure why you are
getting an error here.
> $new_filename=$YYYYMMDD."_".$file_date{$YYYYMMDD};
So the sum of what you are doing is to take the old file name and set it
to $YYYYMMDD_1? Why do you need hashes to do that??
------------------------------
Date: Thu, 6 Feb 2003 20:09:01 +0100 (CET)
From: Tarapia Tapioco <comesefosse@ntani.firenze.linux.it>
Subject: Re: string in datei
Message-Id: <e7f458a40028fc9545cd5a41a5180dc1@firenze.linux.it>
Helgi Briem wrote:
> On 05 Feb 2003 20:08:36 GMT, Abigail <abigail@abigail.nl>
> wrote:
>
>>$$ ... only english here.
>
>>Huh? This isn't en.comp.lang.perl.misc. It would be unfair to ban
>>people to a regional group just because they don't master English.
>>I speak a different language than English. Should I monitor other
>>Perl groups as well (and hence have less time to answer questions
>>here), or are you implying that people who don't master English
>>have no right to hear my opinion about their questions?
>
> No, but if someone posts to an international forum
> in a language other than English, he will have to be
> philosophical about the fact that he is less likely to
> receive a useful answer.
I'm sure the OP realized that and was willing to take his chances anyway.
> I could post questions here in Icelandic all day
> long, but I am not optimistic about my chances
> of its effectiveness.
But that's your choice!
------------------------------
Date: Thu, 06 Feb 2003 15:31:35 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Too many greps
Message-Id: <3E42C627.29C3532E@earthlink.net>
Sherman Willden wrote:
>
> I created a perl script to loop through a list of SourceSafe projects
> and I am using the Windows Services for Unix grep command which
> probably masks perl's grep. When I execute the program the grep.exe
> process is using between 70% to 80% + cpu usage so I would like to get
> rid of the greps if possible. Below is the line I am exeucting within
> the code.
>
> $PROJECTS=`\"$SSPath\" dir -R \$/MyProj | grep \"[\\\$]\" | grep
> \"\/\" | grep -v \"^ \*\$\" | grep -v \"No items\" | grep -v grep`;
I would suggest you write this as:
open( PROJECTS, "-|", $SSPath, qw(dir -R $/MyProj) )
or die "Couldn't start $SSPath: $!";
my $PROJECTS = "";
while( <PROJECTS> ) {
next if
index($_, '$') < 0 or # must contain a '$'
index($_, '/') < 0 or # must contain a '/'
substr($_, 0, 3) eq ' *$' or # mustn't start with ' *$'
index($_, "No items") >= 0 or # mustn't contain 'no items'
index($_, "grep") >= 0; # mustn't contain 'grep'?
$PROJECTS .= $_; # or otherwise process the line here.
}
[snip]
Note that my code *does not* contain any backslashes, anywhere.
This makes it much easier to read.
--
"So, who beat the clueless idiot today?"
"Well, we flipped for it, but when Kuno
landed, he wasn't in any shape to fight."
"Next time, try flipping a *coin.*"
------------------------------
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 4524
***************************************
