[29273] in Perl-Users-Digest
Perl-Users Digest, Issue: 517 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 15 09:10:25 2007
Date: Fri, 15 Jun 2007 06:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 15 Jun 2007 Volume: 11 Number: 517
Today's topics:
Re: Depending on perl version <purlgurl@purlgurl.net>
Re: Depending on perl version anno4000@radom.zrz.tu-berlin.de
Re: Interesting PERL anamoly - confirmation and/or expl <zen13097@zen.co.uk>
Re: Passing literal with reference? <baxter.brad@gmail.com>
Re: Passing literal with reference? <wahab-mail@gmx.net>
Re: Perl Bug??? krakle@visto.com
Re: Perl Bug??? <mritty@gmail.com>
Re: Perl system call fails under windows 2003 server <scobloke2@infotop.co.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 15 Jun 2007 05:49:27 -0700
From: Purl Gurl <purlgurl@purlgurl.net>
Subject: Re: Depending on perl version
Message-Id: <zP2dndOhOsRAF-_bnZ2dnUVZ_vWtnZ2d@giganews.com>
Joe Smith wrote:
> Purl Gurl wrote:
>> if ($] < 5.008)
>> {
>> print "true";
>> unshift (@INC, 'C:/test/path/to/module');
>> }
> You forgot to put that inside a BEGIN{} block.
> If the change to @INC is not done inside a BEGIN{} block,
> the 'use' statements that depend on it will fail.
You are correct. I neglected to consider " . " being automagically
included in @INC during my module testing from that local directory.
Upon creating a new directory "fubar" outside my local " . " testing
directory for my bozo.pm module, and upon copy of my bozo.pm into my
"fubar" directory and deleting my bozo.pm from my local " . " directory,
I verified a BEGIN {} block is needed to incorporate a valid lib path
through unshift of @INC for a lib path not already included.
Interesting a lib path will display in printing @INC but is not valid
for a "use" statement unless wrapped in a BEGIN {} block.
___
bozo.pm
our (@ISA, @EXPORT);
require Exporter;
@ISA=('Exporter');
@EXPORT=qw(Bozo);
sub Bozo
{ print "Hello Bozo! I am located in c:/apache/users/fubar directory"; }
___
test.pl
#!perl
BEGIN { unshift (@INC, "c:/apache/users/fubar"); }
use bozo;
Bozo;
___
PRINTED RESULTS:
Hello Bozo! I am located in c:/apache/users/fubar directory
--
Purl Gurl
--
"Then again what can you expect from a fat-assed, champagne swilling,
half-breed just off the Rez?"
- Joe Kline
------------------------------
Date: 15 Jun 2007 13:03:43 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Depending on perl version
Message-Id: <5dfh1fF3584fbU1@mid.dfncis.de>
Purl Gurl <purlgurl@purlgurl.net> wrote in comp.lang.perl.misc:
[...]
> Interesting a lib path will display in printing @INC but is not valid
> for a "use" statement unless wrapped in a BEGIN {} block.
That's easy to explain. "use()" happens at compile time while an
unadorned "push @INC, 'something'" happens later, at run time. So
"use" doesn't see the effect of "push ...", even if "push ..." appears
in the file before "use". Wrapping a "BEGIN" block around "push ..."
forces it to happen at compile time (that's the meaning of "BEGIN"),
thus it's in time for "use".
Printing "@INC" also happens at run time (unless you wrap it in
a BEGIN block too, try it), so the effect of "push ..." will be
visible.
Anno
------------------------------
Date: 15 Jun 2007 08:24:43 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: Interesting PERL anamoly - confirmation and/or explanations welcomed
Message-Id: <46724ccb$0$5865$da0feed9@news.zen.co.uk>
xyz88888@aol.com <xyz88888@aol.com> wrote:
>
> $csm = "f";
> } elsif ($csm eq "t") {
> $line = "\n$1: $2";
>
> } elsif ($csm eq "f") {
> $line = "$2";
> }
Unrelated to your problem, but I hate the use of strings to represent boolean
values.
Whilst Perl doesn't have built-in 'true'/'false' constants, it does recognise
boolean values, so using one of the natural representations of boolean values
can make your code more readable and less error prone.
For example, the string "f" is actually true in a boolean context, which can be
confusing:
my $csm = "f";
print "true" if $csm;
__END__
true
I like to use a sensibly named variable for my booleans, usually including "is"
or "can", and use the values 1 (true) and 0 (false), e.g.
use constant TRUE => 1;
use constant FALSE => 0;
my $can_sing = FALSE;
my $is_readable = TRUE;
if ( $moon_is_full and $wolf->can_howl() ) { ... }
wich is, IMO, much more readable than:
if ( $full_moon eq "t" and $wolf->howl() eq "t" ) { ... }
------------------------------
Date: Fri, 15 Jun 2007 12:58:02 -0000
From: Brad Baxter <baxter.brad@gmail.com>
Subject: Re: Passing literal with reference?
Message-Id: <1181912282.851623.129660@n2g2000hse.googlegroups.com>
On Jun 11, 3:37 pm, dorno <d...@whitehouse.com> wrote:
> Anyway, if I can make my request somewhat more clear.
>
> Passing \$var, \@array and \%hash keeps the entire batch from being
> flattened.
No, passing references keeps hashes and arrays from being flattened.
A scalar, be it a reference or not, will not be "flattened" any
further.
So just pass the darn scalar. :-)
show_me( "Hello", [ "cruel" ], { 'world' => '.' } );
sub show_me {
my( $scalar, $aref, $href ) = @_;
print "$scalar, $aref->[0] ", %$href, "\n";
}
> The other problem is that if I code the subroutine to handle a referenced
> set of parameters, a flattening of the parameters blows the code Unless I
> test and handle both (or three, or four...) cases in which case the
> handling routine usually would become more complex than the subroutine
> itself.
You're trying too hard. :-)
--
Brad
------------------------------
Date: Fri, 15 Jun 2007 15:06:03 +0200
From: Mirco Wahab <wahab-mail@gmx.net>
Subject: Re: Passing literal with reference?
Message-Id: <f4u36s$n1l$1@mlucom4.urz.uni-halle.de>
Brad Baxter wrote:
> On Jun 11, 3:37 pm, dorno <d...@whitehouse.com> wrote:
>> Anyway, if I can make my request somewhat more clear.
>>
>> Passing \$var, \@array and \%hash keeps the entire batch from being
>> flattened.
>
> No, passing references keeps hashes and arrays from being flattened.
> A scalar, be it a reference or not, will not be "flattened" any
> further.
> So just pass the darn scalar. :-)
What if the "scalar" is, say 316,21 MB in size?
Would you still send it down to subroutines 'as it is'?
Regards
M.
------------------------------
Date: Fri, 15 Jun 2007 00:38:11 -0700
From: krakle@visto.com
Subject: Re: Perl Bug???
Message-Id: <1181893091.227621.7500@u2g2000hsc.googlegroups.com>
On Jun 14, 3:45 pm, Paul Lalli <mri...@gmail.com> wrote:
> On Jun 14, 4:21 pm, kra...@visto.com wrote:
>
> > On Jun 13, 2:11 pm, Paul Lalli <mri...@gmail.com> wrote:
>
> > > Whenever you find yourself wanting to type something like that, you
> > > should really count to 10 and ask yourself what's more likely - that
> > > there's a new and undiscovered bug in the language that's been used
> > > worldwide for 20 years that you just happened to find, or that you
> > > either did something wrong or don't understand the results you're
> > > seeing.
>
> > There's bugs in every Perl release. Your message implies that the
> > language hasn't changed or evolved since 1987.
>
> I implied nothing of the sort. Read my message again.
Maybe you should.
"that there's a new and undiscovered bug in the language that's been
used worldwide for 20 years that you just happened to find". The same
version hasn't been used worldwide for 20 years. So obviously it's
VERY possible to stumble upon NEW bugs that didn't even exist before
the previous release (with in a year).
>
> > A
> > better point is... it's less than likely that someone who isn't
> > Perl savvy enough to 'use strict' will find a bug with the
> > language.
>
> That is exactly what my message said. Read my message again.
>
> Paul Lalli
Maybe you should read it. You didn't write that buddy.
------------------------------
Date: Fri, 15 Jun 2007 05:32:06 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: Perl Bug???
Message-Id: <1181910726.267372.210420@o61g2000hsh.googlegroups.com>
On Jun 15, 3:38 am, kra...@visto.com wrote:
> On Jun 14, 3:45 pm, Paul Lalli <mri...@gmail.com> wrote:
> > On Jun 14, 4:21 pm, kra...@visto.com wrote:
> > > On Jun 13, 2:11 pm, Paul Lalli <mri...@gmail.com> wrote:
> > > > Whenever you find yourself wanting to type something
> > > > like that, you should really count to 10 and ask
> > > > yourself what's more likely - that there's a new and
> > > > undiscovered bug in the language that's been used
> > > > worldwide for 20 years that you just happened to find,
> > > > or that you either did something wrong or don't
> > > > understand the results you're seeing.
>
> > > There's bugs in every Perl release. Your message implies
> > > that the language hasn't changed or evolved since 1987.
> > I implied nothing of the sort. Read my message again.
>
> Maybe you should.
> "that there's a new and undiscovered bug in the language that's
> been used worldwide for 20 years that you just happened to
> find". The same version hasn't been used worldwide for 20
> years. So obviously it's VERY possible to stumble upon NEW bugs
> that didn't even exist before the previous release (with in a
> year).
POSSIBLE, yes. LIKELY, for a newbie to Perl? No.
> > > A better point is... it's less than likely that someone who
> > > isn't Perl savvy enough to 'use strict' will find a bug
> > > with the language.
>
> > That is exactly what my message said. Read my message again.
> Maybe you should read it. You didn't write that buddy.
Are you dense or just a troll? I honestly can't tell. I asked
whether it's more likely that there's a new bug THAT THE OP JUST
HAPPENED TO FIND or that the OP made a mistake. I did not ANYWHERE
say it was unlikely there was a bug in Perl.
Regardless, I'm done with you. You're not worth any further wastes of
my time.
Paul Lalli
------------------------------
Date: Fri, 15 Jun 2007 11:00:02 +0100
From: Ian Wilson <scobloke2@infotop.co.uk>
Subject: Re: Perl system call fails under windows 2003 server
Message-Id: <46726324$0$30332$fa0fcedb@news.zen.co.uk>
rahulkats@gmail.com wrote:
> Hi,
>
> I'm having trouble with perl system call. The system call calls
> ntbackup.exe , the windows inbuilt utiility but the system errors out
> by saying cannot find ntbackup.exe even after giving the full path.
> I'm using windows 2003 server with Perl 5.8
>
> Any suggestions?
>
This script works fine on my Windows XP PC:
#!perl
use strict;
use warnings;
my $args = 'ntbackup.exe';
system ($args) == 0
or die "system '$args' failed - $?";
What happens if you cut & paste (do not retype) the above into notepad,
save as tb.pl on your 2003 server and, from a command prompt type `perl
tb.pl`?
Cut & paste the script, the command line and any error message back into
a posting here.
Have you read `perldoc -f system`?
------------------------------
Date: Fri, 15 Jun 2007 07:10:32 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <IXqci.19421$C96.5288@newssvr23.news.prodigy.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.8 $)
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.rehabitation.com/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 that they do
know and are being the "bad kind" of Lazy.
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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
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 517
**************************************
