[24587] in Perl-Users-Digest
Perl-Users Digest, Issue: 6763 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jul 3 14:05:41 2004
Date: Sat, 3 Jul 2004 11:05:05 -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 Sat, 3 Jul 2004 Volume: 10 Number: 6763
Today's topics:
ANNOUNCE: XUL-Node 0.02 <eilara.at.cpan@news.bezeqint.net>
Insecure dependency in open while running with -T switc <arthur0421@163.com>
Re: Insecure dependency in open while running with -T s <mritty@gmail.com>
Re: Insecure dependency in open while running with -T s <arthur0421@163.com>
Re: Logfile name hack <1usa@llenroc.ude>
Re: My 1st question about locking (and other related is <bik.mido@tiscalinet.it>
perl vs Unix grep <abelden@comcast.net>
Re: Q: re the kind of reference to be bless()ed in OO p <bik.mido@tiscalinet.it>
Re: Q: re the kind of reference to be bless()ed in OO p <bik.mido@tiscalinet.it>
Re: Request for comments on a JPEG metadata Perl module <lv@aol.com>
sending docs attached with Perl (Deen)
Re: sending docs attached with Perl <mbudash@sonic.net>
Re: sending docs attached with Perl <noreply@gunnar.cc>
Re: Totally stuck <bik.mido@tiscalinet.it>
Re: which book to learn Perl (krakle)
Re: win32::job window attributes <MrReallyVeryNice.NOVIRUS@NoSpam.yahoo.com>
Re: win32::job window attributes (Cameron)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 1 Jul 2004 04:42:12 GMT
From: "Ran Eilam" <eilara.at.cpan@news.bezeqint.net>
Subject: ANNOUNCE: XUL-Node 0.02
Message-Id: <I0A3E1.wGv@zorch.sf-bay.org>
NAME
XUL-Node - server-side XUL for Perl
SYNOPSIS
package XUL::Node::Application::HelloWorld; # XUL-Node Hello World
use XUL::Node;
use base 'XUL::Node::Application';
sub start { Window(Label(value => 'Hello World!')) }
1;
DESCRIPTION
XUL-Node is a rich user interface framework for server-based Perl
applications. It includes a server, a UI framework, and a Javascript
XUL client for the Firefox web browser. Perl applications run inside
a POE server, and are displayed in a remote web browser.
The XUL::Node POD has more information.
FEATURES
* Develop user interfaces as you would using frameworks such as Tk or
WxPerl, then deploy to Firefox web clients with no special security
permissions or downloads
* Support for almost all of the XUL, see TODO for unsupported features
* Client-server communication is done through HTTP
* Page never reloads, only UI deltas are sent over the wire
* Almost a 1-1 correspondence with the XUL DOM API, with minimal Perl
syntactic sugar- if you you know XUL, and you know Perl, you can
program in XUL-Node
* 14 examples, including the XUL Periodic Table of Elements,
demonstrating the usage of every widget, attribute, and event
* Unicode and BiDi support
AVAILABILITY
XUL-Node has been uploaded to the CPAN.
AUTHOR
Ran Eilam <eilara@cpan.org>. Please mail me bugs and suggestions.
------------------------------
Date: Sat, 03 Jul 2004 19:21:38 +0800
From: kskkaf <arthur0421@163.com>
Subject: Insecure dependency in open while running with -T switch
Message-Id: <cc64sg$ttt$1@mail.cn99.com>
In an upload subroutine I have the following code:
open (OUTFILE, "> $root/$docfolder/$fpage") or die "Can't open output
file for write: $!";
But the error message as show in the title keeps coming up. Now that I
insist keeping the -T switch, how can I avoid the error message? Thanks
for any clue.
--
kskkaf
------------------------------
Date: Sat, 03 Jul 2004 11:28:41 GMT
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: Insecure dependency in open while running with -T switch
Message-Id: <JLwFc.261$yd5.235@twister.nyroc.rr.com>
"kskkaf" <arthur0421@163.com> wrote in message
news:cc64sg$ttt$1@mail.cn99.com...
> Subject: Insecure dependency in open while running with -T switch
> In an upload subroutine I have the following code:
>
> open (OUTFILE, "> $root/$docfolder/$fpage") or die "Can't open output
> file for write: $!";
>
> But the error message as show in the title keeps coming up. Now that I
> insist keeping the -T switch, how can I avoid the error message? Thanks
> for any clue.
It's telling you that one or more of $root, $docfolder, or $fpage are
tainted. That is, they came from user input or another insecure method.
You must untaint this data before using it to open a file. Untainting means
to verify, via regular expressions, that the data is what it's allowed to
be. Read
perldoc perlsec
for more information and examples.
Paul Lalli
------------------------------
Date: Sat, 03 Jul 2004 21:12:18 +0800
From: kskkaf <arthur0421@163.com>
Subject: Re: Insecure dependency in open while running with -T switch
Message-Id: <cc6bbp$vq7$1@mail.cn99.com>
Paul Lalli wrote:
>
> It's telling you that one or more of $root, $docfolder, or $fpage are
> tainted. That is, they came from user input or another insecure method.
> You must untaint this data before using it to open a file. Untainting means
> to verify, via regular expressions, that the data is what it's allowed to
> be. Read
> perldoc perlsec
> for more information and examples.
>
> Paul Lalli
>
Thanks Paul!
--
kskkaf
------------------------------
Date: 3 Jul 2004 15:48:00 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: Logfile name hack
Message-Id: <Xns951B780B1ABA5asu1cornelledu@132.236.56.8>
jl_post@hotmail.com (J. Romano) wrote in
news:b893f5d4.0407021134.102d3ef2@posting.google.com:
> magoo <magoo@hal-pc.org> wrote in message
> news:<MPG.1b4f3310d3e0384a989684@news.hal-pc.org>...
>> Just got through writing a program which wrote some output to a
>> logfile.
>>
>> Not wanting to overwrite a previous log file, I threw this together:
> <code snipped>
>>
>> This creates a series of logfiles named:
>> logfile_v1.log
>> logfile_v2.log
>> etc
>>
>> I would be interested in hearing any input concerning creating,
>> using, logfiles that anyone might want to share.
>
> That's a cool hack, but you can shorten it (to basically one line)
> with the following:
>
> # Specify logfile name:
> $logfile = "logfile_v1.log";
>
> # Loop until we find a log file name that is not used yet:
> $logfile =~ s/(\d+)/$1+1/e while (-e $logfile);
>
> # Open log file:
> open(LOGFILE, "> $logfile") or die "Cannot open $logfile: $!";
>
> Anyway, thanks for sharing your hack, magoo.
Given the race condition here, it would probably be a good idea to use
sysopen with O_EXCL.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
Date: Sat, 03 Jul 2004 11:44:37 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: My 1st question about locking (and other related issues)
Message-Id: <0pvce0ptr71v87u464g63sqmpdl17d0eat@4ax.com>
On 01 Jul 2004 21:26:25 -0500, Dale Henderson <nilram@hotpop.com>
wrote:
> Another approach would be to write the pid into the
> "lockfile". This would allow for the possibility of checking for
> stale lock files although I do not know of any good way to check
> for a process given a pid or verify it's the correct
> process (i.e. not another process that just happens to have
> inherited your pid).
As a wild guess I'd say that this approach would tend to be more
complicated than that suggested before, but indeed I've seen something
along these lines...
> This also allows for a "kill" script in the .bash_logout that
> would open the "lockfile" and send an appropriate signal to the
> specified pid. Of course this is problematic for it would kill
> your sigfile "daemon" when the first shell exited. I presume you
> would want the "daemon" to continue until the last shell exited.
Well, I think that *if* I have a duplicate processes prevention
mechanism *and* if it continues until the shell it was started from is
exited, *then* that shell will be "the last to be exited".
> What would be ideal (I think) is something like Debian's
> start-stop-daemon but this is not portable. You might look into
> your systems /etc/init.d/ scripts to see how daemons are started
> and stopped.
My distro (here at home, at University we/they use Gentoo) is very
KISS-oriented (CRUX, available at <http://crux.nu>). As an example the
gpm daemon script (which I wrote myself modelling it after the ones
shipped with the distro) is as follows:
#!/bin/sh
#
# /etc/rc.d/gpm: start/stop gpm daemon
#
case $1 in
start)
modprobe -q psmouse
/usr/sbin/gpm -m /dev/misc/psaux -t ps2
;;
stop)
/usr/sbin/gpm -k || killall -q /usr/sbin/gpm
;;
restart)
$0 stop
sleep 2
$0 start
;;
*)
echo "usage: $0 [start|stop|restart]"
;;
esac
# End of file
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Sat, 3 Jul 2004 11:58:44 -0400
From: "Al Belden" <abelden@comcast.net>
Subject: perl vs Unix grep
Message-Id: <utmdnRvfc6h2RXvd4p2dnA@comcast.com>
Hi all,
I've been working on a problem that I thought might be of interest: I'm
trying to replace some korn shell scripts that search source code files with
perl scripts to gain certain features such as:
More powerful regular expressions available in perl
Ability to print out lines before and after matches (gnu grep supports this
but is not availble on our Digital Unix and AIX platforms)
Make searches case insensitive by default (yes, I know this can be done with
grep but the shell scripts that use
grep don't do this)
We're talking about approx. 5000 files spread over 15 directories. To date
it has proven quite difficult (for me) to match the performance of the Korn
shell scripts using perl scripts and still obtain the line number and
context information needed. The crux of the problem is that I have seen the
best performance from perl when I match with the /g option on a string that
represents the current slurped file:
local $/;
my $curStr = <FH>;
my $compiledRegex = qr/$srchStr/;
while ($curStr =~ /$compiledRegex/g)
{
# write matches to file for eventual paging
}
This works well except that when each match is found I need the line number
the match has been found in. As far as I can tell from reading and research
there is no variable that holds this information as I am not reading from
the file at this point. I can get the information in other ways such as:
1. Reading each file a line at a time, testing for a match and keeping a
line counter or using $NR or $..
2. Reading the file into an array and processing a line at a time
3. Creating index files for the source files that store line offsets and
using them with the slurp method in the paragraph above
4. Creating an in-memory index for each file that contains a match and using
it for subsequent matches in that file
1, 2 and 4 above suffer performance degradation relative to unix grep. #3
provides good performance and is the method I am currently using but it
requires creating and maintaining index files. I was wondering if I could
tie a scalar to a file and use the slurping loop above. Then perhaps $NR and
$. would contain the current line number as the file would be read as the
loop is traversed. Any other ideas would be welcome
------------------------------
Date: Sat, 03 Jul 2004 11:44:43 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Q: re the kind of reference to be bless()ed in OO perl
Message-Id: <fltce01fj9qgr9cmjtpoo07f9d49r8sbal@4ax.com>
On Thu, 01 Jul 2004 22:46:57 GMT, Ala Qumsieh <notvalid@email.com>
wrote:
>> I've also seen bless()ing something like an empty {array,hash}ref to
>> be used "solely" as an index into a package/class global hash to
>> enforce some degree of encapsulation.
>
>I'm not sure what you mean there. Can you show a code snippet please?
Sorry, I must have been not particularly clear. What I've seen at
times is along these lines:
{
package Foo;
use warnings;
use strict;
my %attribs;
sub new {
my $class=shift;
my $self=bless [], $class;
$attribs{$self}={ bar => undef };
$self;
}
sub DESTROY {
my $self=shift;
delete $attribs{$self};
}
sub set_bar {
my $self=shift;
$attribs{$self}{bar}=shift if @_;
}
sub get_bar {
my $self=shift;
$attribs{$self}{bar};
}
}
>Note that bless() returns the blessed reference, so it can be used as
>the last statement of the constructor to return the object (blessed
>reference).
I knew that... So what?!? (No offense intended)
>> Now I wonder if there are common/cool/smart/witty cases in which it is
>> natural to use a reference to some other kind of object, like e.g. a
>> sub, or filehandle, etc.
>
>I believe Damian Conway has a few examples in his Object-Oriented Perl
>book. Personally, I have written many Perl classes, and can only recall
>one that didn't use a hashref for the object representation (I used an
>arrayref, to be precise, since the data structure I was after was easily
>representable as a matrix).
I see... well, I can think of rather "artificial" examples as follows:
package Adder;
use warnings;
use strict;
sub new {
my ($class,$n)=@_;
bless sub {
$n+shift;
}, $class;
}
sub doit {
shift->(pop);
}
but I was asking exactly if there are known cases in which using e.g.
a subref brings some real advantage or is quite a natural approach for
the problem being tackled.
TIA,
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Sat, 03 Jul 2004 11:44:49 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Q: re the kind of reference to be bless()ed in OO perl
Message-Id: <mduce0l3c5ctvvnv3auesk0lo5msg7as9v@4ax.com>
On Fri, 02 Jul 2004 04:52:04 GMT, Andrew Lee <spamtrap@nowhere.com>
wrote:
>>Now I wonder if there are common/cool/smart/witty cases in which it is
>>natural to use a reference to some other kind of object, like e.g. a
>>sub, or filehandle, etc.
>
>Certainly ... though I don't know how smart, cool or witty.
[snip]
>my $action = {
> Default => \&Default,
> PrintThis => \&PrintThis,
> DumpENV => \&DumpENV
>};
[snip]
>Naturally you can bless $action ... which just means it can be used in another
>Perl program like a static class member as $Foo::action
Thank you for the example. But this is not exactly what I was asking
(it may well be that the question was not well posed). $action is
still a hashref...
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Sat, 03 Jul 2004 12:06:54 -0500
From: l v <lv@aol.com>
Subject: Re: Request for comments on a JPEG metadata Perl module
Message-Id: <40e6e7af$1_7@corp.newsgroups.com>
Stefano Bettelli wrote:
> Hi,
>
> Il giorno Thu, 01 Jul 2004 06:34:25 -0700, GreenLight scrisse:
>
>>I have been wanting to create a catalog of my photos
>>for quite some time.
>
>
> this is exactly my problem :-). I believe that in order to
> manage a catalogue with little complication, one should be
> able to enter his comments/additional info directly into the
> image, and then use a perl script to generate dynamic web
> pages with the required fields.
>
> For the first task, I think that a winning combination is a
> specialised library capable of parsing/modifying the JPEG
> structure together with a GUI program allowing you to interact
> with your photos more easily. Maybe you could have a look at
> the following program:
>
> http://herrmanns-stern.de/software/mapivi/mapivi.shtml
>
> Bye,
> Stefano
>
The closest I could get was using the Image::IPTCInfo module's
SetAttribute, AddKeyword, and Keywords functions to build my catalog.
Although I would much rather save the information in EXIF vs IPTC. I
then use jhead ( http://www.sentex.net/~mwandel/jhead ) to autorotate
the image which automatically updates the EXIF orientation flag for me.
ImageMagick is also used to create my thumbnails (convert) and a
contact sheet (montage)
Len
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
------------------------------
Date: 3 Jul 2004 08:44:43 -0700
From: yne_fr@yahoo.fr (Deen)
Subject: sending docs attached with Perl
Message-Id: <84012c5f.0407030744.38f3363e@posting.google.com>
Hi!
I'm desperately seeking for a Perl script to send a message
with attached documents.
Thanks for help.
------------------------------
Date: Sat, 03 Jul 2004 15:59:16 GMT
From: Michael Budash <mbudash@sonic.net>
Subject: Re: sending docs attached with Perl
Message-Id: <mbudash-53C09D.08593903072004@typhoon.sonic.net>
In article <84012c5f.0407030744.38f3363e@posting.google.com>,
yne_fr@yahoo.fr (Deen) wrote:
> Hi!
>
> I'm desperately seeking for a Perl script to send a message
> with attached documents.
>
> Thanks for help.
if by 'message' you mean 'email message', use the MIME::Lite perl
module, available at your local neighborhood CPAN. it rocks.
http://www.cpan.org/modules/by-module/MIME/
--
Michael Budash
------------------------------
Date: Sat, 03 Jul 2004 16:57:37 GMT
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: sending docs attached with Perl
Message-Id: <5ABFc.4153$dx3.33114@newsb.telia.net>
Deen wrote:
> I'm desperately seeking for a Perl script to send a message with
> attached documents.
My favorite Perl module for sending email messages is Mail::Sender.
Even if I only use it for plain text messages, it was designed
explicitly for sending mails with attachments.
http://search.cpan.org/perldoc?Mail%3A%3ASender
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Sat, 03 Jul 2004 11:44:31 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Totally stuck
Message-Id: <lvuce0dll2lp3r0pd41fv203lh8daivdif@4ax.com>
On Thu, 01 Jul 2004 23:50:44 GMT, "Paul Lalli" <mritty@gmail.com>
wrote:
>Okay. I think I understand. So you're saying
>perl -lne 'print, next unless /foo/'
>is equivalent to
>perl -lne 'do {print; next;} unless /foo/'
>
>Is that correct? If so, then I guess my question to the original poster of
I would say so.
>that code is what's the point of the 'next' at all? Wouldn't simply '
>print unless /foo/ ' do the same thing? (that is, it would do the same
>thing in the simple example posted where the line ' print, next unless
>/foo/ ' is the only line in a program run with the -ln options). As 'next'
>would be the last thing evaluated in the loop block, it would seem to serve
>no purpose.
Indeed!
>Am I missing something obvious?
Well, I can't remember at which point the above cmd line example
popped out. But in the script that I originally posted C<next> was
*not* the last thing evaluated in the loop. So it *did* make sense...
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: 3 Jul 2004 10:23:16 -0700
From: krakle@visto.com (krakle)
Subject: Re: which book to learn Perl
Message-Id: <237aaff8.0407030923.2cba6159@posting.google.com>
Paul Lalli <mritty@yahoo.com> wrote in message news:<20040701144336.X16568@barbara.cs.rpi.edu>...
> On Thu, 1 Jul 2004, danny_isr wrote:
>
> > Hi i'm new to Perl.
> > someone gave me the "Learning Perl" book from O`reilly.
> > but i will have to get my own soon.
> > i saw that there is another book (with the camel)"Programming Perl" . what
> > the difference between them ?
> > which is better for a beginner and beyond.
> > i saw there the cook book as well ...
> >
> > or maybe there are other out there ?
>
>
> You have a good friend there.
>
> Learning Perl, by Randal Schwartz,
Randal Schwartz blah..
------------------------------
Date: Sat, 3 Jul 2004 00:16:55 -0700
From: "MrReallyVeryNice" <MrReallyVeryNice.NOVIRUS@NoSpam.yahoo.com>
Subject: Re: win32::job window attributes
Message-Id: <SvmdnUJlQrf1wHvd4p2dnA@comcast.com>
Hello Cameron,
Using your syntax, I was able to reproduce your problem. Of course, I don't
have a D:\Link32\Link32.exe on my computer so I used Notepad.exe. Notepad
would start but it would not be hidden or minimized. By the same token,
output.txt and error.txt were not created. I went back to the documentation
for Win32::Job and used the exact syntax. Here is a little sample that
worked for me on W2K:
==== Beginning script sample =====
use strict;
use warnings;
use Win32::Job;
my $job = Win32::Job->new();
my %opts=( window_attr=>'hidden',
stdout => 'output.txt',
stderr => 'error.txt');
$job->spawn(q{c:\winnt\system32\notepad.exe}, q{notepad "d:\temp\temp.txt"},
\%opts);
$job->run(10);
==== End script sample =====
As you noticed, the main difference with your script is that I defined the
hash %opts. I was then able to successfully minimize or hide the window. Of
course, output.txt and error.txt were also created successfully.
You might want to give it a try and see if the syntax documented for
Win32::Job does not fix your problem as well.
I would be great if you could report your future failure/success. :-)
Additional questions are of course always welcome.
MrReallyVeryNice
------------------------------
Date: 3 Jul 2004 08:06:26 -0700
From: cam@ntwk.net (Cameron)
Subject: Re: win32::job window attributes
Message-Id: <e4dad21a.0407030706.279bda92@posting.google.com>
"MrReallyVeryNice" <MrReallyVeryNice.NOVIRUS@NoSpam.yahoo.com> wrote in message news:<SvmdnUJlQrf1wHvd4p2dnA@comcast.com>...
> Hello Cameron,
>
> Using your syntax, I was able to reproduce your problem. Of course, I don't
> have a D:\Link32\Link32.exe on my computer so I used Notepad.exe. Notepad
> would start but it would not be hidden or minimized. By the same token,
> output.txt and error.txt were not created. I went back to the documentation
> for Win32::Job and used the exact syntax. Here is a little sample that
> worked for me on W2K:
>
> ==== Beginning script sample =====
> use strict;
> use warnings;
> use Win32::Job;
>
> my $job = Win32::Job->new();
> my %opts=( window_attr=>'hidden',
> stdout => 'output.txt',
> stderr => 'error.txt');
> $job->spawn(q{c:\winnt\system32\notepad.exe}, q{notepad "d:\temp\temp.txt"},
> \%opts);
> $job->run(10);
>
> ==== End script sample =====
>
> As you noticed, the main difference with your script is that I defined the
> hash %opts. I was then able to successfully minimize or hide the window. Of
> course, output.txt and error.txt were also created successfully.
>
> You might want to give it a try and see if the syntax documented for
> Win32::Job does not fix your problem as well.
>
> I would be great if you could report your future failure/success. :-)
> Additional questions are of course always welcome.
>
> MrReallyVeryNice
Hey Nice --
No go ..... I was able to reproduce your results with notepad as well,
but the application (a bastardized copy of wIntegrate used by car
dealers to access an old PICK system from Reynolds & Reynolds) still
refuses to open in a minimised window. Thanks for your input!
Cameron
------------------------------
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 6763
***************************************
