[30070] in Perl-Users-Digest
Perl-Users Digest, Issue: 1313 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Feb 27 16:09:42 2008
Date: Wed, 27 Feb 2008 13:09:08 -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 Wed, 27 Feb 2008 Volume: 11 Number: 1313
Today's topics:
Re: a very simplistic example of a perl module <Benson.Hoi@googlemail.com>
Re: BEGIN not safe after errors--compilation aborted <zen13097@zen.co.uk>
Re: changing the date/time stamp <tadmc@seesig.invalid>
how to process each directory <rsarpi@gmail.com>
Re: how to process each directory <simon.chao@fmr.com>
Re: how to process each directory <rsarpi@gmail.com>
Re: how to process each directory <simon.chao@fmr.com>
Re: How to set file attributes <tzz@lifelogs.com>
Re: How to set file attributes <jimsgibson@gmail.com>
Re: How to set file attributes <rkb@i.frys.com>
Re: How to set file attributes <rkb@i.frys.com>
Re: How to set file attributes <glennj@ncf.ca>
Re: uc() and utf8 <check.sig@for.email.invalid>
using Crypt::Lite <cartercc@gmail.com>
Re: using Crypt::Lite <smallpond@juno.com>
Re: using Crypt::Lite <cartercc@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 27 Feb 2008 12:54:04 -0800 (PST)
From: BH <Benson.Hoi@googlemail.com>
Subject: Re: a very simplistic example of a perl module
Message-Id: <46a2c8c5-96b9-4950-9e1e-94fff1ee8b65@i29g2000prf.googlegroups.com>
Interesting! It's interesting someone actually thinks that any typical
school/university will teach Perl as a subject? ;)
On Feb 26, 7:51 pm, xhos...@gmail.com wrote:
> BH <Benson....@googlemail.com> wrote:
> > Thanks.
>
> > Can you add to the simple example another subroutine not to be
> > exported,
>
> No. Exporting is one of those details you didn't want to bother with.
> If you now want to bother with it, then go back to reading the docs
> you gave up on. I'm going to read them to you.
>
> > as well as 2 variables, one to exported and one not to be?
>
> Who will receive credit for your homework, me or you?
>
> Xho
>
> --
> --------------------http://NewsReader.Com/--------------------
> The costs of publication of this article were defrayed in part by the
> payment of page charges. This article must therefore be hereby marked
> advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
> this fact.
------------------------------
Date: 27 Feb 2008 08:10:21 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: BEGIN not safe after errors--compilation aborted
Message-Id: <47c51aed$0$21093$da0feed9@news.zen.co.uk>
> my $google_ua = LWP::UserAgent->new;
> my $google_ad_output = $google_ua->get($google_ad_url);
> if ($google_ad_output->is_success) {
> print $google_ad_output->content;
> }
If the get() call fails, your program outputs nothing, and
you will get a "500 internal server error", or similar.
Change that to:
if ($google_ad_output->is_success) {
print $google_ad_output->content;
}
else {
print "failed to fetch ad:\n"
. "URL = $google_ad_url\n"
. "status = " . $google_ad_output->status_line
. "\n";
}
Then run the script by hand from a command prompt:
perl googleperlcode.cgi
to see what output you get. I suspect there is a problem
fetching whatever URL it builds.
------------------------------
Date: Tue, 26 Feb 2008 19:16:33 -0600
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: changing the date/time stamp
Message-Id: <slrnfs9efh.a73.tadmc@tadmc30.sbcglobal.net>
monk <rsarpi@gmail.com> wrote:
> Is there a "perl way" of modifying the date/time stamp of a file? Is
> there a core function or core module I'm overlooking?
perldoc -f utime
> # from the shell, modify xfile creation date to year 2001 January day
^^^^^^^^^^^^^
> 30 time 13:50:26
> touch -t 200101301350.26 xfile
touch does NOT modify the creation date, because there is no
such thing on most *nix filesystems...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Wed, 27 Feb 2008 12:37:21 -0800 (PST)
From: monk <rsarpi@gmail.com>
Subject: how to process each directory
Message-Id: <193a0f19-c4ba-46a8-b295-21a43305edab@z17g2000hsg.googlegroups.com>
Hi all, I was wondering if you guys can help me figure this out.
This is what I'm trying to do:
read in a file containing paths to directories /home/foo/logs,
etc...all fine here.
I'd like to get into those directories and process the files inside.
Problem in this part.
This is what I have:
##slurp file into @directories_to_clean blah blah blah...
foreach (@directories_to_clean){
chomp;
print "$_\n"; #testing if I got the right directories and I do
ex: /home/foo/logs
#Here is the problem. It stops below claiming there's no file or
directory.
#same thing if I try to set a variable instead of default $_
# Isn't $_ equivalent to /home/foo/logs above ???
opendir (ARCHIVE, $_) or die "what the?...$!";
------------------------------
Date: Wed, 27 Feb 2008 12:40:56 -0800 (PST)
From: nolo contendere <simon.chao@fmr.com>
Subject: Re: how to process each directory
Message-Id: <0677feb8-54f0-423f-9b4f-0710acd15de6@q33g2000hsh.googlegroups.com>
On Feb 27, 3:37=A0pm, monk <rsa...@gmail.com> wrote:
> Hi all, =A0I was wondering if you guys can help me figure this out.
>
> This is what I'm trying to do:
>
> read in a file containing paths to directories =A0/home/foo/logs,
> etc...all fine here.
> I'd like to get into those directories and process the files inside.
> Problem in this part.
>
> This is what I have:
>
> ##slurp file into @directories_to_clean blah blah blah...
>
> foreach (@directories_to_clean){
> =A0 =A0 chomp;
> =A0 =A0 print "$_\n"; =A0 =A0#testing if I got the right directories and I=
do
> ex: /home/foo/logs
>
> =A0 =A0 =A0#Here is the problem. =A0It stops below claiming there's no fil=
e or
> directory.
> =A0 =A0 =A0#same thing if I try to set a variable instead of default $_
>
> =A0 =A0 =A0 # =A0 Isn't =A0 =A0$_ =A0 equivalent to /home/foo/logs above =
=A0 =A0???
>
> =A0 =A0 opendir (ARCHIVE, $_) or die "what the?...$!";
Can you post a workable piece of code, along with the actual message
returned by Perl, along with perhaps a copy/paste of you "ls'ing" to
one of those dirs successfully?
------------------------------
Date: Wed, 27 Feb 2008 12:48:53 -0800 (PST)
From: monk <rsarpi@gmail.com>
Subject: Re: how to process each directory
Message-Id: <82075e77-4653-453c-be39-9f7979101354@s13g2000prd.googlegroups.com>
> Can you post a workable piece of code, along with the actual message
> returned by Perl, along with perhaps a copy/paste of you "ls'ing" to
> one of those dirs successfully?
Here you go:
# read config file in
# add inside test.conf directories such as /home/foo/logs or whatever.
save the file.
open($log_file_handler,"<", "test.conf") or die "Can't open config file
\n";
DISTRIBUTION_CENTER:
while (<$log_file_handler>) {
chomp;
s/#.*//; # Remove comments
s/^ *//; #Remove leading spaces
s/ *$//; #Remove trailing spaces
next DISTRIBUTION_CENTER if /^(\s)*$/; # skip blank lines
push @directories_to_clean, $_; #add entries to an array
}
#it's supposed to go inside each directory
foreach (@directories_to_clean){
chomp;
print "$_\n"; #testing if I got the right directories and I do
ex: /home/foo/logs
opendir (ARCHIVE, $_) or die "what the?...$!";
chdir $_; #it doesn't get this far
}
ERROR: what the hell?...No such file or directory.
------------------------------
Date: Wed, 27 Feb 2008 13:02:36 -0800 (PST)
From: nolo contendere <simon.chao@fmr.com>
Subject: Re: how to process each directory
Message-Id: <a1a45160-6a98-4933-891a-b66f5a3b9a66@h25g2000hsf.googlegroups.com>
On Feb 27, 3:48=A0pm, monk <rsa...@gmail.com> wrote:
> > Can you post a workable piece of code, along with the actual message
> > returned by Perl, along with perhaps a copy/paste of you "ls'ing" to
> > one of those dirs successfully?
>
> Here you go:
>
> # read config file in
> # add inside test.conf directories such as /home/foo/logs or whatever.
> save the file.
> open($log_file_handler,"<", "test.conf") or die "Can't open config file
> \n";
>
> DISTRIBUTION_CENTER:
> while (<$log_file_handler>) {
> =A0 =A0 =A0 =A0 chomp;
> =A0 =A0 =A0 =A0 s/#.*//; # Remove comments
> =A0 =A0 =A0 =A0 s/^ *//; #Remove leading spaces
> =A0 =A0 =A0 =A0 s/ *$//; #Remove trailing spaces
> =A0 =A0 =A0 =A0 next DISTRIBUTION_CENTER if /^(\s)*$/; =A0# skip blank lin=
es
>
> =A0 =A0 =A0 =A0 push @directories_to_clean, $_; #add entries to an array
>
> }
>
> #it's supposed to go inside each directory
> foreach (@directories_to_clean){
> =A0 =A0 chomp;
> =A0 =A0 print "$_\n"; =A0 =A0#testing if I got the right directories and I=
do
> ex: /home/foo/logs
Here, try:
if ( -d $_ ) {
print "this is a directory\n";
else {
print ">>$_<< is not a directory.\n";
}
> =A0 =A0 opendir (ARCHIVE, $_) or die "what the?...$!";
> =A0 =A0 chdir $_; =A0#it doesn't get this far
>
> }
>
> ERROR: what the hell?...No such file or directory.
------------------------------
Date: Wed, 27 Feb 2008 09:00:40 -0600
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How to set file attributes
Message-Id: <86bq62tpev.fsf@lifelogs.com>
On Tue, 26 Feb 2008 22:25:45 +0200 John <John.Smith@invalid.com> wrote:
J> I have set up my own counter.pl on my web page.
J> The counter saves the visitation count to a text file called "count.txt".
J> How do I create the file (and later open) with file attributes that prevent
J> others reading the file, ie. going to www.johnsmith.com/count.txt (the www here
J> is not real).
Use the mail system to deliver an e-mail message to a special mailbox
for every hit. For a local mail spool, Maildir works best for
performance. Don't use a mbox file if you can help it.
Then you can just count the number of messages in the mailbox. This is
a really simple approach that works reliably on any system, and you can
even do it remotely with SMTP and IMAP. Your sysadmin will love it
because it's very secure.
Another approach I recommend highly is to do "grep -c" against the web
server logs and count the number of HTTP GETs. It gets a little slow
with older logs since you have to uncompress them, but at least you
don't have to worry about locking.
Probably the most robust, if slowest, approach is to read the Perl FAQ
on this topic, as others have suggested.
Ted
------------------------------
Date: Wed, 27 Feb 2008 09:48:56 -0800
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: How to set file attributes
Message-Id: <270220080948567195%jimsgibson@gmail.com>
In article <v20as35s7rbbmbdfbt4ki3hcga22ue08uc@4ax.com>, John
<John.Smith@invalid.com> wrote:
> Setting the files chmod 0600 count.txt seems to do what I want.
> The perl script creates a num conter file for every day. How do I create the new
> file so that it has 0600 attributes?
> $txtfi=open (MYCOUNT,"<"."count.txt");
You create the file by any means and then set the permissions using
chmod. Perl has a built-in chmod function ('perldoc -f chmod').
If you really insist on creating the file and setting the permissions
in one step, you can use the four-argument version of Perl's sysopen
function ( sysopen FILEHANDLE,FILENAME,MODE,PERMS )
but you are making your life more complicated ('perldoc -f sysopen').
From the command-line, you can control the permissions of new files
using the umask mask. Set it to 066 to create files with permissions of
0600. The umask is used to exclusive-or the default permissions of
0666, so each true bit in your umask sets the corresponding permission
bit to zero ('man csh' and search for 'umask' -- it is a shell
built-in).
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Wed, 27 Feb 2008 10:20:12 -0800 (PST)
From: Ron Bergin <rkb@i.frys.com>
Subject: Re: How to set file attributes
Message-Id: <e6d9e967-ae60-4bba-90f0-9ebed13228bd@i7g2000prf.googlegroups.com>
On Feb 26, 10:27 pm, John <John.Sm...@invalid.com> wrote:
> Jim Gibson <jimsgib...@gmail.com> wrote:
> >In article <38t8s3550b7tipdjlg66u2ddmv8683k...@4ax.com>, John
> ><John.Sm...@invalid.com> wrote:
>
> >> I have set up my own counter.pl on my web page.
>
> >> The counter saves the visitation count to a text file called "count.txt".
> >> How do I create the file (and later open) with file attributes that prevent
> >> others reading the file, ie. going towww.johnsmith.com/count.txt (the www
> >> here
> >> is not real).
>
> >It depends upon the operating system. Under Unix, you would create the
> >file with an editor, the cat command, or the touch command (see 'man
> >cat', etc.). File permissions are set with the chmod command. You want
> >to set the file so that it is readable and writable only by the owner:
>
> > chmod 0600 count.txt
>
> >The problem is that for this to work, the file needs to be owned by the
> >web server process, and that may not be your own user id. Some web
> >servers use the user 'nobody', for example. As a result, you sometimes
> >have to set data files to be world writable:
>
> > chmod 0666 count.txt
>
> >So it also depends upon your user id, the web server's id, and whether
> >or not you have root privilege.
>
> >If you do have root privilege, then you can set the owner of the file
> >as well as the file permissions (as above):
>
> > chown nobody:nobody count.txt
> > chmod 0600 count.txt
>
> >But this is for Unix, not necessarily other operating systems.
>
> Thanks for input. The web counter files should be seen my me only (I download the
> files every day).
>
> Setting the files chmod 0600 count.txt seems to do what I want.
> The perl script creates a num conter file for every day. How do I create the new
> file so that it has 0600 attributes?
> $txtfi=open (MYCOUNT,"<"."count.txt");
use File::CounterFile;
http://search.cpan.org/~gaas/File-CounterFile-1.04/CounterFile.pm
The module uses sysopen without specifying the perm (which defaults to
0666) so you'd probably what to adjust the code in the module.
change:
sysopen(F, $file, O_RDWR|O_CREAT) or croak("Can't open $file: $!");
to:
sysopen(F, $file, O_RDWR|O_CREAT, 0600) or croak("Can't open $file:
$!");
------------------------------
Date: Wed, 27 Feb 2008 10:20:45 -0800 (PST)
From: Ron Bergin <rkb@i.frys.com>
Subject: Re: How to set file attributes
Message-Id: <8a8b85f6-a22b-447f-8073-b2cac0dbbb24@d5g2000hsc.googlegroups.com>
On Feb 26, 10:27 pm, John <John.Sm...@invalid.com> wrote:
> Jim Gibson <jimsgib...@gmail.com> wrote:
> >In article <38t8s3550b7tipdjlg66u2ddmv8683k...@4ax.com>, John
> ><John.Sm...@invalid.com> wrote:
>
> >> I have set up my own counter.pl on my web page.
>
> >> The counter saves the visitation count to a text file called "count.txt".
> >> How do I create the file (and later open) with file attributes that prevent
> >> others reading the file, ie. going towww.johnsmith.com/count.txt (the www
> >> here
> >> is not real).
>
> >It depends upon the operating system. Under Unix, you would create the
> >file with an editor, the cat command, or the touch command (see 'man
> >cat', etc.). File permissions are set with the chmod command. You want
> >to set the file so that it is readable and writable only by the owner:
>
> > chmod 0600 count.txt
>
> >The problem is that for this to work, the file needs to be owned by the
> >web server process, and that may not be your own user id. Some web
> >servers use the user 'nobody', for example. As a result, you sometimes
> >have to set data files to be world writable:
>
> > chmod 0666 count.txt
>
> >So it also depends upon your user id, the web server's id, and whether
> >or not you have root privilege.
>
> >If you do have root privilege, then you can set the owner of the file
> >as well as the file permissions (as above):
>
> > chown nobody:nobody count.txt
> > chmod 0600 count.txt
>
> >But this is for Unix, not necessarily other operating systems.
>
> Thanks for input. The web counter files should be seen my me only (I download the
> files every day).
>
> Setting the files chmod 0600 count.txt seems to do what I want.
> The perl script creates a num conter file for every day. How do I create the new
> file so that it has 0600 attributes?
> $txtfi=open (MYCOUNT,"<"."count.txt");
use File::CounterFile;
http://search.cpan.org/~gaas/File-CounterFile-1.04/CounterFile.pm
The module uses sysopen without specifying the perm (which defaults to
0666) so you'd probably what to adjust the code in the module.
change:
sysopen(F, $file, O_RDWR|O_CREAT) or croak("Can't open $file: $!");
to:
sysopen(F, $file, O_RDWR|O_CREAT, 0600) or croak("Can't open $file:
$!");
------------------------------
Date: 27 Feb 2008 18:22:33 GMT
From: Glenn Jackman <glennj@ncf.ca>
Subject: Re: How to set file attributes
Message-Id: <slrnfsbaja.a99.glennj@smeagol.ncf.ca>
At 2008-02-27 12:48PM, "Jim Gibson" wrote:
> From the command-line, you can control the permissions of new files
> using the umask mask. Set it to 066 to create files with permissions of
> 0600. The umask is used to exclusive-or the default permissions of
> 0666, so each true bit in your umask sets the corresponding permission
> bit to zero ('man csh' and search for 'umask' -- it is a shell
> built-in).
or perldoc -f umask
--
Glenn Jackman
"You can only be young once. But you can always be immature." -- Dave Barry
------------------------------
Date: Wed, 27 Feb 2008 13:38:22 +0200
From: Alex <check.sig@for.email.invalid>
Subject: Re: uc() and utf8
Message-Id: <NYbxj.302836$mv7.294200@reader1.news.saunalahti.fi>
Ben Morrow wrote:
> Quoth Alex <check.sig@for.email.invalid>:
>>
>> I suggest you also look into, and play around with, the functions
>> is_utf8(), _utf8_on(), _utf8_off() and from_to(). This will give you a
>> good overall picture of how Perl does UTF-8, but you probably won't need
>> these here.
>
> No, don't touch any of the functions in the utf8:: namespace. They are
> part of the internals of perl's Unicode implementation, and shouldn't be
> used by ordinary Perl code; especially _utf8_{on,off}. Use the functions
> in Encode:: instead.
Those were the ones I was talking about. I thought it was clear from the
fact that Encode:: was the only namespace I mentioned.
Alex
--
localpart = alext
domain = iki dot fi
email = localpart at domain
------------------------------
Date: Wed, 27 Feb 2008 05:59:33 -0800 (PST)
From: ccc31807 <cartercc@gmail.com>
Subject: using Crypt::Lite
Message-Id: <9d813b6c-1187-49fc-94bd-afd182e35754@b1g2000hsg.googlegroups.com>
This might be a question no one knows the answer to.
We started using Crypt::Lite to encrypt the SSNs of files for
temporary storage, 7 or 8 days at the most. The files are CSV files
with lines like this:
IDENTIFIER,Bush,George,Walker,999887777,other,data,here
The output is like this for each line:
IDENTIFIER,Bush,George,Walker,WoPsW7/oWIDsXYPqWoTSCNTvX4bjWY/tX4e
+DNDiWIPjCNDuWNK+DoO4VdPjCdQ=,other,data,here
So far the encryption string has never contained a comma. If it did,
it would really screw things up, as this is run as an automated
process and we do not have human eyes checking the format of the
decrypted files. (A comma would right shift all remaining fields.)
!. Does Crypt::Lite ever use a comma as an encryption character?
2. If so, can you tell it NOT to use a comma?
Thanks, CC.
------------------------------
Date: Wed, 27 Feb 2008 07:04:12 -0800 (PST)
From: smallpond <smallpond@juno.com>
Subject: Re: using Crypt::Lite
Message-Id: <f5f2d892-2ffd-4220-9d1a-dc5f3beb65a7@34g2000hsz.googlegroups.com>
On Feb 27, 8:59 am, ccc31807 <carte...@gmail.com> wrote:
> This might be a question no one knows the answer to.
>
> We started using Crypt::Lite to encrypt the SSNs of files for
> temporary storage, 7 or 8 days at the most. The files are CSV files
> with lines like this:
>
> IDENTIFIER,Bush,George,Walker,999887777,other,data,here
>
> The output is like this for each line:
>
> IDENTIFIER,Bush,George,Walker,WoPsW7/oWIDsXYPqWoTSCNTvX4bjWY/tX4e
> +DNDiWIPjCNDuWNK+DoO4VdPjCdQ=,other,data,here
>
> So far the encryption string has never contained a comma. If it did,
> it would really screw things up, as this is run as an automated
> process and we do not have human eyes checking the format of the
> decrypted files. (A comma would right shift all remaining fields.)
>
> !. Does Crypt::Lite ever use a comma as an encryption character?
> 2. If so, can you tell it NOT to use a comma?
>
> Thanks, CC.
It uses MIME::Base64 in the encoding so you will only get
[A-Za-z0-9+/=]. You can also specify using hex8,
------------------------------
Date: Wed, 27 Feb 2008 07:28:21 -0800 (PST)
From: ccc31807 <cartercc@gmail.com>
Subject: Re: using Crypt::Lite
Message-Id: <c9789ae3-5427-4587-a50a-4538b1d587ec@o77g2000hsf.googlegroups.com>
On Feb 27, 10:04 am, smallpond <smallp...@juno.com> wrote:
> On Feb 27, 8:59 am, ccc31807 <carte...@gmail.com> wrote:
>
>
>
> > This might be a question no one knows the answer to.
>
> > We started using Crypt::Lite to encrypt the SSNs of files for
> > temporary storage, 7 or 8 days at the most. The files are CSV files
> > with lines like this:
>
> > IDENTIFIER,Bush,George,Walker,999887777,other,data,here
>
> > The output is like this for each line:
>
> > IDENTIFIER,Bush,George,Walker,WoPsW7/oWIDsXYPqWoTSCNTvX4bjWY/tX4e
> > +DNDiWIPjCNDuWNK+DoO4VdPjCdQ=,other,data,here
>
> > So far the encryption string has never contained a comma. If it did,
> > it would really screw things up, as this is run as an automated
> > process and we do not have human eyes checking the format of the
> > decrypted files. (A comma would right shift all remaining fields.)
>
> > !. Does Crypt::Lite ever use a comma as an encryption character?
> > 2. If so, can you tell it NOT to use a comma?
>
> > Thanks, CC.
>
> It uses MIME::Base64 in the encoding so you will only get
> [A-Za-z0-9+/=]. You can also specify using hex8,
Thanks, CC.
------------------------------
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 1313
***************************************
