[28058] in Perl-Users-Digest
Perl-Users Digest, Issue: 9422 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jul 4 06:05:39 2006
Date: Tue, 4 Jul 2006 03:05:04 -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 Tue, 4 Jul 2006 Volume: 10 Number: 9422
Today's topics:
'Undifined commands' on FTP Server, when using FTP 'put <asafsi@radware.com>
Archive::Zip problem - bytes being added/changed by zip <usenet.10@spam.stopper.scottsonline.org.uk>
Re: Archive::Zip problem - bytes being added/changed by <flavell@physics.gla.ac.uk>
Re: Archive::Zip problem - bytes being added/changed by <mumia.w.18.spam+nospam.usenet@earthlink.net>
caller() in XS <bol@adv.magwien.gv.at>
Re: caller() in XS anno4000@zrz.tu-berlin.de
Crimson Editor query <VSRawat@Invalid.none>
Re: languages with full unicode support <jo@durchholz.org>
Learning Typeglobs, Symbol Tables and the More Obscure <vtatila@mail.student.oulu.fi>
new CPAN modules on Tue Jul 4 2006 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
ReadKey/ ReadLine query <VSRawat@Invalid.none>
Re: ReadKey/ ReadLine query <VSRawat@Invalid.none>
Re: ReadKey/ ReadLine query <someone@example.com>
Re: ReadKey/ ReadLine query anno4000@zrz.tu-berlin.de
Re: ReadKey/ ReadLine query <jurgenex@hotmail.com>
Re: scope trouble <zen13097@zen.co.uk>
Re: What is Expressiveness in a Computer Language <jo@durchholz.org>
Re: Which is the perl questions ng for beginners <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 4 Jul 2006 02:22:52 -0700
From: "Asaf Sinai" <asafsi@radware.com>
Subject: 'Undifined commands' on FTP Server, when using FTP 'put' and 'quit' in Client
Message-Id: <1152004972.184799.211520@v61g2000cwv.googlegroups.com>
Hi,
I use WFTPD as an FTP Server on WIN XP.
I wrote the following perl program:
#!/usr/bin/perl -w
use strict;
use Net::FTP;
my $ftp_site = "1.100.100.10";
my $username = "test";
my $password = "test";
my $local_dir = "T:\\temp";
my $local_file = "ftp_test_file";
my $remote_dir = "C:\\temp";
my $remote_file = "remote_ftp_test_file";
# Change to local directory
chdir $local_dir
or die "\nFailed to cd to '$local_dir': $! $@\n";
# Start FTP: connect, login and go to target directory
print "\nConnecting to target at '$ftp_site'...\n";
my $ftp = Net::FTP->new($ftp_site, Debug => 0)
or die "\nFailed to connect to '$ftp_site': $! $@";
print "\nLogin to target...\n";
$ftp->login($username, $password)
or die "\nFailed to login with username-$username and
password-$password:\n FTP: ",
$ftp->message, " $! $@";
$ftp->cwd($remote_dir)
or die "\nFailed to cd to '$remote_dir' on target:\n FTP: ",
$ftp->message, " $! $@";
# Transfer file
print "\nUploading file...\n";
$ftp->put($local_file, $remote_file)
or die "\nFailed to put '$local_file' to '$remote_file' on target:\n
FTP: ",
$ftp->message, " $! $@";
# Close connection
print "\nClosing connection...\n";
$ftp->quit;
On the FTP Server I got the following:
[L 4423] 07/04/06 12:13:00 Connection accepted from 1.100.100.10
[C 4423] 07/04/06 12:13:00 Command "user test" received
[C 4423] 07/04/06 12:13:00 PASSword accepted
[L 4423] 07/04/06 12:13:00 User test logged in.
[C 4423] 07/04/06 12:13:00 Command "CWD C:\temp" received
[C 4423] 07/04/06 12:13:00 CWD C:\temp successful
[! 4423] 07/04/06 12:13:00 Unidentified command ALLO 7150209
[C 4423] 07/04/06 12:13:00 Command "PASV" received
[C 4423] 07/04/06 12:13:00 Entering Passive Mode (1,100,100,10,12,92)
[C 4423] 07/04/06 12:13:00 Command "STOR remote_ftp_test_file" received
[P 4423] 07/04/06 12:13:00 STORe started on file remote_ftp_test_file
[C 4423] 07/04/06 12:13:01 Transfer finished
[P 4423] 07/04/06 12:13:01 Put file C:\temp\remote_ftp_test_file
successfully
[! -001] 07/04/06 12:13:01 Received data signal FD_READ on socket 508
which I can't find
[C 4423] 07/04/06 12:13:01 Command "QUIT" received
[C 4423] 07/04/06 12:13:01 QUIT or close - user test logged out
[! -001] 07/04/06 12:13:01 Received a command on socket 408 which I
can't find
As you can see, when the 'put' command was performed, the FTP Server
did not recognize command ALLO (is it allocate space?).
Also after transfer finished successfully, an data signal was received
???
Also after 'quit' command, unknown command was received ???
When I performed the FTP session from the command line:
ftp 1.100.100.10
Connected to 1.100.100.10.
220-
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (1.100.100.10:(none)): test
331 Give me your password, please
Password:
230 Logged in successfully
ftp> cd c:\temp
250 "C:\temp" is current directory
ftp> put ftp_test_file remote_ftp_test_file
200 PORT command okay
150 "C:\temp\remote_ftp_test_file" file ready to receive in ASCII mode
226 Transfer finished successfully.
ftp: 7150209 bytes sent in 0.33Seconds 21733.16Kbytes/sec.
ftp> quit
221-
221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
Everything was OK, as follows:
[L 4425] 07/04/06 12:19:15 Connection accepted from 1.100.100.10
[C 4425] 07/04/06 12:19:18 Command "USER test" received
[C 4425] 07/04/06 12:19:19 PASSword accepted
[L 4425] 07/04/06 12:19:19 User test logged in.
[C 4425] 07/04/06 12:19:27 Command "CWD c:\temp" received
[C 4425] 07/04/06 12:19:27 CWD C:\temp successful
[C 4425] 07/04/06 12:19:32 Command "PORT 1,100,100,10,12,104" received
[C 4425] 07/04/06 12:19:32 PORT set to 1.100.100.10 - 3176 (12,104)
[C 4425] 07/04/06 12:19:32 Command "STOR remote_ftp_test_file" received
[P 4425] 07/04/06 12:19:32 STORe started on file remote_ftp_test_file
[C 4425] 07/04/06 12:19:33 Transfer finished
[P 4425] 07/04/06 12:19:33 Put file C:\temp\remote_ftp_test_file
successfully
[C 4425] 07/04/06 12:19:35 Command "QUIT" received
[C 4425] 07/04/06 12:19:35 QUIT or close - user test logged out
As you can see, instead of command 'PASV' there is command 'PORT', and
no undifined commands/signals.
Does anyone know why this happens, and what's wrong in the perl program
?
Regards,
Asaf
------------------------------
Date: Tue, 04 Jul 2006 08:17:45 GMT
From: Mike Scott <usenet.10@spam.stopper.scottsonline.org.uk>
Subject: Archive::Zip problem - bytes being added/changed by zip->contents()
Message-Id: <Jupqg.69347$lQ.58901@newsfe3-gui.ntli.net>
[reposted from comp.lang.perl.modules, as no-one there has replied, and
this problem is hurting :-( ]
Maybe I've misunderstood something. But when calling $zip->contents() I
keep getting characters added and/or replaced within the returned string.
EG the following code snippet:
$content = 'content.txt';
my $zip = Archive::Zip->new('test.zip');
my ($contentstring, $status) = $zip->contents($content);
print "after reading contents: +++", $contentstring, "+++\n";
The member content.txt contains, simply,
XXXchar="dot"XXX
However the returned string, in this case, is prefixed with extra weird
characters:
%od -ab ~/xxxx
0000000 a f t e r sp r e a d i n g sp c o
141 146 164 145 162 040 162 145 141 144 151 156 147 040 143 157
0000020 n t e n t s : sp + + + ef bb bf X X
156 164 145 156 164 163 072 040 053 053 053 357 273 277 130 130
0000040 X c h a r = " d o t " X X X + +
130 143 150 141 162 075 042 144 157 164 042 130 130 130 053 053
0000060 + cr nl
053 015 012
0000063
(Note the hex ef, bb, bf inserted.)
In general, at least some non-ascii bytes are changed too - I'm trying
to work with OpenOffice files, and for example the 'bullet' character is
extracted wrongly.
Oddly though, if I use extractTree() to make a file copy of content.txt,
that appears to be accurate, a least in this test case.
The same problem occurs on XP and freebsd installations, both using 1.16
of archive::zip.
Can anyone clue me into what's going on here please?
--
Please use the corrected version of the address below for replies.
Replies to the header address will be junked, as will mail from
various domains listed at www.scottsonline.org.uk
Mike Scott Harlow Essex England.(unet -a-t- scottsonline.org.uk)
------------------------------
Date: Tue, 4 Jul 2006 09:55:00 +0100
From: "Alan J. Flavell" <flavell@physics.gla.ac.uk>
Subject: Re: Archive::Zip problem - bytes being added/changed by zip->contents()
Message-Id: <Pine.LNX.4.64.0607040949240.7990@ppepc87.ph.gla.ac.uk>
On Tue, 4 Jul 2006, Mike Scott wrote:
> However the returned string, in this case, is prefixed with extra weird
> characters:
>
> %od -ab ~/xxxx
> 0000000 a f t e r sp r e a d i n g sp c o
> 141 146 164 145 162 040 162 145 141 144 151 156 147 040 143 157
> 0000020 n t e n t s : sp + + + ef bb bf X X
> 156 164 145 156 164 163 072 040 053 053 053 357 273 277 130 130
> 0000040 X c h a r = " d o t " X X X + +
[...]
> (Note the hex ef, bb, bf inserted.)
It's worth memorising the values of the Unicode BOM so that you
recognise them when they appear:
http://www.unicode.org/faq/utf_bom.html#25
I don't know why you're getting one - I can only go as far as telling
you that something has decided you're using UTF-8 and has given you an
"appropriate" BOM.
Perhaps if you were to decode the whole thing as utf-8, it would start
to make more sense, but I haven't tried this.
------------------------------
Date: Tue, 04 Jul 2006 09:31:36 GMT
From: "Mumia W." <mumia.w.18.spam+nospam.usenet@earthlink.net>
Subject: Re: Archive::Zip problem - bytes being added/changed by zip->contents()
Message-Id: <Yzqqg.2683$cd3.1142@newsread3.news.pas.earthlink.net>
Mike Scott wrote:
> [reposted from comp.lang.perl.modules, as no-one there has replied, and
> this problem is hurting :-( ]
>
> Maybe I've misunderstood something. But when calling $zip->contents() I
> keep getting characters added and/or replaced within the returned string.
>
> EG the following code snippet:
>
> $content = 'content.txt';
> my $zip = Archive::Zip->new('test.zip');
> my ($contentstring, $status) = $zip->contents($content);
> print "after reading contents: +++", $contentstring, "+++\n";
>
> The member content.txt contains, simply,
> XXXchar="dot"XXX
>
> However the returned string, in this case, is prefixed with extra weird
> characters:
>
> %od -ab ~/xxxx
> 0000000 a f t e r sp r e a d i n g sp c o
> 141 146 164 145 162 040 162 145 141 144 151 156 147 040 143 157
> 0000020 n t e n t s : sp + + + ef bb bf X X
> 156 164 145 156 164 163 072 040 053 053 053 357 273 277 130 130
> 0000040 X c h a r = " d o t " X X X + +
> 130 143 150 141 162 075 042 144 157 164 042 130 130 130 053 053
> 0000060 + cr nl
> 053 015 012
> 0000063
>
> (Note the hex ef, bb, bf inserted.)
> [...]
I was unable to reproduce your problem on Debian 3.1 using Perl 5.8.4
and Archive::Zip 1.14:
$ od -ab o
0000000 a f t e r sp r e a d i n g sp c o
141 146 164 145 162 040 162 145 141 144 151 156 147 040 143 157
0000020 n t e n t s : sp + + + X X X c h
156 164 145 156 164 163 072 040 053 053 053 130 130 130 143 150
0000040 a r = " d o t " X X X nl + + + nl
141 162 075 042 144 157 164 042 130 130 130 012 053 053 053 012
0000060
I think it's your locale. The spurious sequence \x{eb}\x{bb}\x{bf} seems
to be some sort of unicode (UTF-8) mark. I appended the spurious
sequence to content.txt, and both the Debian 'file' command and 'vim'
recognize the modified file as UTF-8 whereas the original was recognized
as ASCII.
HTH
------------------------------
Date: Tue, 4 Jul 2006 10:56:07 +0200
From: "Ferry Bolhar" <bol@adv.magwien.gv.at>
Subject: caller() in XS
Message-Id: <1152003367.730440@proxy.dienste.wien.at>
Hi,
is there a way to determine, whether XS code is running as part
of a BEGIN or INIT block, or in the main program?
Or, more generally: where the information returned by the caller()
function is stored? Is it available from XS code?
MTIA & kind greetings,
Ferry
--
Ing. Ferry Bolhar
Municipality of Vienna, Department 14
A-1010 Vienna / AUSTRIA
E-mail: bol@adv.magwien.gv.at
------------------------------
Date: 4 Jul 2006 09:48:14 GMT
From: anno4000@zrz.tu-berlin.de
Subject: Re: caller() in XS
Message-Id: <4gurquF1pleg5U1@news.dfncis.de>
Ferry Bolhar <bol@adv.magwien.gv.at> wrote in comp.lang.perl.misc:
> Hi,
>
> is there a way to determine, whether XS code is running as part
> of a BEGIN or INIT block, or in the main program?
>
> Or, more generally: where the information returned by the caller()
> function is stored? Is it available from XS code?
Apparently there isn't an XS-callable equivalent to caller(). The
caller() builtin is defined in pp_ctl.c (look for "pp_caller").
Anno
------------------------------
Date: Tue, 4 Jul 2006 06:46:32 +0000 (UTC)
From: "V S Rawat" <VSRawat@Invalid.none>
Subject: Crimson Editor query
Message-Id: <xn0eobr6u7e7dc002@nntp.aioe.org>
Anyone using Crimson Editor for working in Perl?
I have set it up and defined perl interpreter in its tools. It is duly
compiling and executing the program (from within crimson editor). I
have given "capture output" and it is showing the progress in the lower
pane.
However, as soon as it encounters some ReadKey/ReadLine command,
instead of waiting for me to input something, it exits with
> Terminated with exit code 2.
For this reason I have to open a separate dos window to execute the
program.
Any method of making Crimson Editor accept input from me?
Thanks.
--
Rawat
------------------------------
Date: Tue, 04 Jul 2006 09:22:01 +0200
From: Joachim Durchholz <jo@durchholz.org>
Subject: Re: languages with full unicode support
Message-Id: <e8d4u9$sdf$1@online.de>
Oliver Bandel schrieb:
> Matthias Blume wrote:
>
>> Tin Gherdanarra <tinman31337@gmail.com> writes:
>>
>>
>>> Oliver Bandel wrote:
>>>
>>>> こんいちわ Xah-Lee san ;-)
>>>
>>> Uhm, I'd guess that Xah is Chinese. Be careful
>>> with such things in real life; Koreans might
>>> beat you up for this. Stay alive!
>>
>>
>> And the Japanese might beat him up, too. For butchering their
>> language. :-)
>
> OK, back to ISO-8859-1 :) no one needs so much symbols,
> this is enough: äöüÄÖÜß :)
If you want äöüÄÖÜß, anybody else will want their local characters, too,
and nothing below full Unicode will work.
Just for laughs, here's a list of non-ASCII Latin-based letters in
Unicode (not verified for completeness):
ÀÁÂÃÄÅÆàáâãäåæĀāĂ㥹ǺǻǼǽ
ÇçĆćĈĉĊċČč
ĎďĐđ
ÈÉÊËèéêëĒēĔĕĖėĘęĚě
ĜĝĞğĠġĢģ
ĤĥĦħ
ÌÍÎÏìíîïĨĩĪīĬĭĮįİıIJij
Ĵĵ
Ķķĸ
ĹĺĻļĽĿŀŁł
Ðð
ÑñŃńŅņŇňʼnŊŋ
ÒÓÔÕØòóôöõŌōŎŏÖŐőŒœǾǿ
ŔŕŖŗŘř
ŚśŜŝŞşŠšß
ŢţŤťŦŧ
ÜÙÚÛüùúûŨũŪūŭŮůŰűŲų
Ŵŵ
ÝýÿŶŷŸ
Þþ
ŹźŻżŽž
ƒſ
ISO 8859-1 covers just a fraction of these, so Unicode would indeed be
necessary to allow a program written in one country to compile in
another one.
Regards,
Jo
------------------------------
Date: Tue, 4 Jul 2006 09:09:45 +0300
From: "Veli-Pekka Ttil" <vtatila@mail.student.oulu.fi>
Subject: Learning Typeglobs, Symbol Tables and the More Obscure Features?
Message-Id: <e8d0nq$fo$1@news.oulu.fi>
Hi,
I'd like to learn more about the various ways to access and use type globs
and how to deal with symbol table entries. Having started out with Perl 5.8,
I try to generaly stick to modern solutions such as references, exporter and
lexical file handles. Yet both type globs and symbol tables seem to pop up
in interesting places and appear somewhat related because symbol tables hold
globs and even some of the glob syntax looks like dereferencing to me. As
for usage, aliasing variable names like English does, creating truely
"weird" classses based on type globs, implementing callbacks using the
caller's package variables such as those in List::Util and installing new
subroutines (Memoize) or applying reflection come to mind.
Most books only briefly mention type globs and symbol tables, and even
Programming Perl has the information scattered in various places. Advanced
Perl Programming appears to have a whole chapter on the topic, number 3 that
is, but even so not all of the syntax such as *foo{thing} is covered, as far
as I can tell.
Frankly speaking I'm not happy with Perldoc's approach either. I've done
some digging and found bits and pieces here and there such as in perlmod,
perldata, perlref and perlsub. There's partial overlap in those docs and I
would describe the tone as: oh yeah, there are type globs, but I'm not sure
if you'll ever need them, and even if you do, we'll just quickly mention
them here to get to the more important stuff.
So are there any good books, tutorials or references that would fully cover
symbol tables and type globs, in particular, their usage in Perl 5? I'd
prefer on-line sources. Now that I'm here I'll also slip in another
question, howabout docs on the rest of the more obscure features that make
Perl perl such as formats and symbolic references under use strict 'vars'.
While not often needed, I'd like to read up more on those, too, and have a
feeling that I might have to maintain someone else's ancient Perl code some
day. Learning Perl doesn't cover formats any more, and most books deal with
symbolic references vaguely if at all.
PS: Is it a type glob or a typeglob or are both forms OK?
--
With kind regards Veli-Pekka Ttil (vtatila@mail.student.oulu.fi)
Accessibility, game music, synthesizers and programming:
http://www.student.oulu.fi/~vtatila/
------------------------------
Date: Tue, 4 Jul 2006 04:42:06 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Jul 4 2006
Message-Id: <J1v3q6.229I@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-MetaSyntactic-0.81
http://search.cpan.org/~book/Acme-MetaSyntactic-0.81/
Themed metasyntactic variables names
----
Acme-Phlegethoth-1.00
http://search.cpan.org/~rcaputo/Acme-Phlegethoth-1.00/
Improve your code's readability, if you're an Ancient One
----
Acme-Phlegethoth-1.01
http://search.cpan.org/~rcaputo/Acme-Phlegethoth-1.01/
Improve your code's readability, if you're an Ancient One
----
Alvis-Pipeline-0.08
http://search.cpan.org/~mirk/Alvis-Pipeline-0.08/
Perl extension for passing XML documents along the Alvis pipeline
----
Bio-Das-ProServer-2.01
http://search.cpan.org/~rpettett/Bio-Das-ProServer-2.01/
----
Business-PayPal-API-0.32
http://search.cpan.org/~scottw/Business-PayPal-API-0.32/
PayPal API
----
CGI-Application-Dispatch-2.00
http://search.cpan.org/~wonko/CGI-Application-Dispatch-2.00/
Dispatch requests to CGI::Application based objects
----
Catalyst-Log-Log4perl-0.4
http://search.cpan.org/~holoway/Catalyst-Log-Log4perl-0.4/
Log::Log4perl logging for Catalyst
----
Catalyst-Plugin-Authentication-Credential-HTTP-0.02
http://search.cpan.org/~esskar/Catalyst-Plugin-Authentication-Credential-HTTP-0.02/
HTTP Basic authentication for Catlayst.
----
Catalyst-Plugin-Authentication-Credential-HTTP-0.03
http://search.cpan.org/~esskar/Catalyst-Plugin-Authentication-Credential-HTTP-0.03/
HTTP Basic authentication for Catlayst.
----
Compile-Generators-0.10
http://search.cpan.org/~ingy/Compile-Generators-0.10/
Write Python-like generators in Perl
----
Compile-Generators-0.11
http://search.cpan.org/~ingy/Compile-Generators-0.11/
Python-like generator subroutines for Perl
----
Data-Hive-0.03
http://search.cpan.org/~hdp/Data-Hive-0.03/
convenient access to hierarchical data
----
Deco-0.06
http://search.cpan.org/~narked/Deco-0.06/
Module for simulating body tissue during a scuba dive
----
Devel-PPPort-3.08_07
http://search.cpan.org/~mhx/Devel-PPPort-3.08_07/
Perl/Pollution/Portability
----
Directory-Scratch-0.02
http://search.cpan.org/~jrockway/Directory-Scratch-0.02/
Easy-to-use self-cleaning scratch space.
----
EekBoek-0.91
http://search.cpan.org/~jv/EekBoek-0.91/
Bookkeeping software for small and medium-size businesses
----
Email-Send-2.10
http://search.cpan.org/~rjbs/Email-Send-2.10/
Simply Sending Email
----
Encode-BOCU1-0.01
http://search.cpan.org/~naoyat/Encode-BOCU1-0.01/
encodes / decodes BOCU-1 string, works as part of Encode.pm
----
Encode-BOCU1-0.02
http://search.cpan.org/~naoyat/Encode-BOCU1-0.02/
encodes / decodes BOCU-1 string, works as part of Encode.pm
----
Encode-BOCU1-0.03
http://search.cpan.org/~naoyat/Encode-BOCU1-0.03/
encodes / decodes BOCU-1 string, works as part of Encode.pm
----
Encode-BOCU1-XS-0.01
http://search.cpan.org/~naoyat/Encode-BOCU1-XS-0.01/
Perl extension for encoding / decoding BOCU-1 string. Works as part of Encode.pm
----
Encode-BOCU1-XS-0.02
http://search.cpan.org/~naoyat/Encode-BOCU1-XS-0.02/
Perl extension for encoding / decoding BOCU-1 string. Works as part of Encode.pm
----
File-Attributes-0.01
http://search.cpan.org/~jrockway/File-Attributes-0.01/
Manipulate file metadata
----
File-Attributes-Recursive-0.01
http://search.cpan.org/~jrockway/File-Attributes-Recursive-0.01/
Inherit file attributes from parent directories.
----
File-Copy-Recursive-0.25
http://search.cpan.org/~dmuey/File-Copy-Recursive-0.25/
Perl extension for recursively copying files and directories
----
Froody-42.010
http://search.cpan.org/~fotango/Froody-42.010/
Yet another XML web API framework
----
Games-Sudoku-General-0.006
http://search.cpan.org/~wyant/Games-Sudoku-General-0.006/
Solve sudoku-like puzzles.
----
IO-Toolkit-1.005
http://search.cpan.org/~linmar/IO-Toolkit-1.005/
----
JavaScript-XRay-1.1
http://search.cpan.org/~jbisbee/JavaScript-XRay-1.1/
See What JavaScript is Doing
----
Language-l33t-0.03
http://search.cpan.org/~yanick/Language-l33t-0.03/
a l33t interpreter
----
Module-Compile-0.17
http://search.cpan.org/~ingy/Module-Compile-0.17/
Perl Module Compilation
----
MusicBrainz-Client-0.11
http://search.cpan.org/~svanzoest/MusicBrainz-Client-0.11/
MusicBrainz Client API
----
MusicBrainz-Queries-0.10
http://search.cpan.org/~svanzoest/MusicBrainz-Queries-0.10/
MusicBrainz RDF Query Constants
----
Parse-RecDescent-Topiary-0.04
http://search.cpan.org/~ivorw/Parse-RecDescent-Topiary-0.04/
tree surgery for Parse::RecDescent autotrees
----
Perl-Tags-0.2
http://search.cpan.org/~osfameron/Perl-Tags-0.2/
Generate (possibly exuberant) Ctags style tags for Perl sourcecode
----
RPC-Simple-1.002
http://search.cpan.org/~cedwards/RPC-Simple-1.002/
Perl classes to handle simple asynchronous RPC calls with call-back
----
SWISH-Filter-0.03
http://search.cpan.org/~karman/SWISH-Filter-0.03/
filter documents for indexing with Swish-e
----
String-Gsub-0.01
http://search.cpan.org/~hio/String-Gsub-0.01/
regex on string object
----
String-String-0.01
http://search.cpan.org/~hio/String-String-0.01/
make values string
----
Tie-STDOUT-1.0
http://search.cpan.org/~dcantrell/Tie-STDOUT-1.0/
intercept writes to STDOUT and apply user-defined functions to them.
----
Tie-STDOUT-1.01
http://search.cpan.org/~dcantrell/Tie-STDOUT-1.01/
intercept writes to STDOUT and apply user-defined functions to them.
----
Win32-Security-EFS-0.07
http://search.cpan.org/~esskar/Win32-Security-EFS-0.07/
Perl interface to functions that assist in working with EFS (Encrypted File System) under Windows plattforms.
----
Win32-Security-EFS-0.08
http://search.cpan.org/~esskar/Win32-Security-EFS-0.08/
Perl interface to functions that assist in working with EFS (Encrypted File System) under Windows plattforms.
----
YAML-0.62
http://search.cpan.org/~ingy/YAML-0.62/
YAML Ain't Markup Language (tm)
----
Yahoo-Music-Ratings-2.00
http://search.cpan.org/~smolarek/Yahoo-Music-Ratings-2.00/
A method for retrieving a Yahoo! Music members song ratings.
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: 04 Jul 2006 07:22:05 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
Message-Id: <44aa171c$0$57736$ae4e5890@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 4 Jul 2006 06:40:20 +0000 (UTC)
From: "V S Rawat" <VSRawat@Invalid.none>
Subject: ReadKey/ ReadLine query
Message-Id: <xn0eobr1976784000@nntp.aioe.org>
1. I am currently doing it like this:
--------------
do {
print "Font Name (1: Arjun, 2: Shree709, 3: Shusha, 0: Exit)? \n";
use Term::ReadKey;
ReadMode 4; # Turn off controls keys
while (not defined ($C1_map_opt = ReadKey(-1))) { # No key yet
}
if ( $Debug_flag == 1 ) { # $Debug_flag has already been defined
print "Get key $C1_map_opt\n";
}
ReadMode 0; # Reset tty mode before exiting
} until ( $C1_map_opt >= 0 && $C1_map_opt <= 3 );
--------------
Is there any method of giving a prompt (e.g. "Font Name (1: Arjun, 2:
Shree709, 3: Shusha, 0: Exit)? \n") with ReadKey? I mean, the way we
can do with ReadLine as in:
---------
my $prompt = "Input file name (0: Exit)? ";
$term->readline($prompt)
-------------------
That would avoid me writing a separate line some three lines before the
actual readkey command.
---------------------------------------------
2. The following is not reaching "entered file name: " line, nor is
exiting at 0.
----------------
use Term::ReadLine;
my $term = new Term::ReadLine 'Simple Perl calc';
my $prompt = "Input file name (0: Exit)? ";
my $OUT = $term->OUT || \*STDOUT;
while ( defined ($_ = $term->readline($prompt)) ) {
$InFile = eval($_);
warn $@ if $@;
print $OUT $InFile, "\n" unless $@;
$term->addhistory($_) if /\S/;
}
if ($InFile == "0") {
exit;
}
print "entered file name: ", $InFile, "\n";
----------------
What did I do wrongly?
TIA.
--
Rawat
------------------------------
Date: Tue, 4 Jul 2006 06:43:01 +0000 (UTC)
From: "V S Rawat" <VSRawat@Invalid.none>
Subject: Re: ReadKey/ ReadLine query
Message-Id: <xn0eobr3o79orc001@nntp.aioe.org>
V S Rawat wrote:
> if ($InFile == "0") {
> exit;
> }
Oops! It should be
if ($InFile eq "0") {
because it is a string.
But, it is not working with eq either.
--
Rawat
------------------------------
Date: Tue, 04 Jul 2006 07:02:13 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: ReadKey/ ReadLine query
Message-Id: <Vnoqg.117375$S61.33664@edtnps90>
V S Rawat wrote:
> V S Rawat wrote:
>
>> if ($InFile == "0") {
>> exit;
>> }
>
> Oops! It should be
> if ($InFile eq "0") {
> because it is a string.
No, it should be:
if ($InFile == 0) {
exit;
}
because 0 is a number even when it is written as "0".
John
--
use Perl;
program
fulfillment
------------------------------
Date: 4 Jul 2006 07:31:08 GMT
From: anno4000@zrz.tu-berlin.de
Subject: Re: ReadKey/ ReadLine query
Message-Id: <4gujpsF1p13q7U1@news.dfncis.de>
V S Rawat <VSRawat@Invalid.none> wrote in comp.lang.perl.misc:
> 1. I am currently doing it like this:
>
> --------------
> do {
> print "Font Name (1: Arjun, 2: Shree709, 3: Shusha, 0: Exit)? \n";
> use Term::ReadKey;
> ReadMode 4; # Turn off controls keys
> while (not defined ($C1_map_opt = ReadKey(-1))) { # No key yet
> }
> if ( $Debug_flag == 1 ) { # $Debug_flag has already been defined
> print "Get key $C1_map_opt\n";
> }
> ReadMode 0; # Reset tty mode before exiting
> } until ( $C1_map_opt >= 0 && $C1_map_opt <= 3 );
> --------------
>
> Is there any method of giving a prompt (e.g. "Font Name (1: Arjun, 2:
> Shree709, 3: Shusha, 0: Exit)? \n") with ReadKey? I mean, the way we
> can do with ReadLine as in:
> ---------
> my $prompt = "Input file name (0: Exit)? ";
> $term->readline($prompt)
> -------------------
>
> That would avoid me writing a separate line some three lines before the
> actual readkey command.
There is only one way to find out: read the doc. Why should anyone
do that for you?
> ---------------------------------------------
>
> 2. The following is not reaching "entered file name: " line, nor is
> exiting at 0.
> ----------------
> use Term::ReadLine;
> my $term = new Term::ReadLine 'Simple Perl calc';
> my $prompt = "Input file name (0: Exit)? ";
> my $OUT = $term->OUT || \*STDOUT;
> while ( defined ($_ = $term->readline($prompt)) ) {
> $InFile = eval($_);
> warn $@ if $@;
> print $OUT $InFile, "\n" unless $@;
> $term->addhistory($_) if /\S/;
> }
>
> if ($InFile == "0") {
> exit;
> }
> print "entered file name: ", $InFile, "\n";
Your while loop won't end except when you enter an EOF (^D under Unix).
So the subsequent statements are never reached.
Put the query for the loop end inside the loop.
Anno
------------------------------
Date: Tue, 04 Jul 2006 07:36:26 GMT
From: "Jrgen Exner" <jurgenex@hotmail.com>
Subject: Re: ReadKey/ ReadLine query
Message-Id: <_Toqg.13304$5i3.8902@trnddc01>
John W. Krahn wrote:
> V S Rawat wrote:
>> V S Rawat wrote:
>>
>>> if ($InFile == "0") {
>>> exit;
>>> }
>>
>> Oops! It should be
>> if ($InFile eq "0") {
>> because it is a string.
>
> No, it should be:
>
> if ($InFile == 0) {
> exit;
> }
>
> because 0 is a number even when it is written as "0".
But what about "00" or "000"? If those are considered as equal, then yes,
the OP should use numerical comparison. If they are different then the OP
should use textual comparison.
jue
------------------------------
Date: 04 Jul 2006 07:33:37 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: scope trouble
Message-Id: <44aa19d1$0$4376$da0feed9@news.zen.co.uk>
Sherm Pendley <sherm@Sherm-Pendleys-Computer.local> wrote:
> Shane <shane@weasel.is-a-geek.net> writes:
>
>
> > for ($counter=0;$counter <=8;$counter++){
> > if (defined $puzzle->{$element}[$counter]){$element_counter++}
..................................................^..................^
> > }
>
> There's no opening bracket on that if(). The other errors are likely to be the
> result of failed error recovery after the first error.
Yes there is. But the horrible code layout obscured it.
------------------------------
Date: Tue, 04 Jul 2006 10:19:21 +0200
From: Joachim Durchholz <jo@durchholz.org>
Subject: Re: What is Expressiveness in a Computer Language
Message-Id: <e8d89p$29d$1@online.de>
Andreas Rossberg schrieb:
> AFAICT, ADT describes a type whose values can only be accessed by a
> certain fixed set of operations. Classes qualify for that, as long as
> they provide proper encapsulation.
The first sentence is true if you associate a semantics (i.e. axioms)
with the operations. Most OO languages don't have a place for expressing
axioms (except via comments and handwaving), so they still don't fully
qualify.
Regards,
jo
------------------------------
Date: Tue, 4 Jul 2006 00:49:12 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Which is the perl questions ng for beginners
Message-Id: <slrneak0ao.7pp.tadmc@magna.augustmail.com>
Ben Bullock <benkasminbullock@gmail.com> wrote:
>
> "Sherm Pendley" <sherm@Sherm-Pendleys-Computer.local> wrote in message
> news:m23bdiun8o.fsf@Sherm-Pendleys-Computer.local...
>> "V S Rawat" <VSRawat@Invalid.none> writes:
>>
>>> 1. Which ng to sub to ask my beginner level queries without disturbing
>>> the veterans.
>>
>> This group is appropriate for all levels. The best way to avoid stepping
>> on
>> anyone's toes is to read *and follow* the posting guidelines which are
>> posted
>> here twice weekly.
>
>
> Unfortunately there are a lot of people here who seem to hope that someone
> will step on their toes so that they'll get an excuse to harass yet another
> newbie poster. I've never seen such a newsgroup for picking on and flaming
> newbies as this one.
A great cause of the consternation stems from exactly this sort
of comment. Newbie at *what*? Newbie at Perl or Newbie at Usenet?
I hardly every see Perl newbies picked on and flamed.
I very often see Usenet newbies picked on and flamed.
An unqualified "newbie" is a useless (and harmful) use of the term.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
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 9422
***************************************
