[28479] in Perl-Users-Digest
Perl-Users Digest, Issue: 9843 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 13 14:05:47 2006
Date: Fri, 13 Oct 2006 11:05:06 -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, 13 Oct 2006 Volume: 10 Number: 9843
Today's topics:
500 Chunked must be last Transfer-Encoding 'identity' carmstrong@cbamedia.com
ANNOUNCE - Perl module Google::Adwords v0.4 <rohan@almeida.in>
Re: bless an object in a BEGIN block (Singleton) (Randal L. Schwartz)
Re: bless an object in a BEGIN block (Singleton) <sc@rimple.net>
Re: Data inheritence with classes in Perl don.hosek@gmail.com
Re: Data inheritence with classes in Perl anno4000@radom.zrz.tu-berlin.de
Re: Data inheritence with classes in Perl <sc@rimple.net>
Re: FAQ 4.36 How can I expand variables in text strings <m@remove.this.part.rtij.nl>
Re: FAQ 4.36 How can I expand variables in text strings anno4000@radom.zrz.tu-berlin.de
Re: Help with test program anno4000@radom.zrz.tu-berlin.de
Re: Help with test program anno4000@radom.zrz.tu-berlin.de
Re: openGL 0.5 perl module problem, again <glex_no-spam@qwest-spam-no.invalid>
Re: Probs with nested conditions <ultimard@yahoo.com>
Re: Probs with nested conditions anno4000@radom.zrz.tu-berlin.de
Re: QUERY_STRING parsing and '$value =~ tr/+/ /;' treat anno4000@radom.zrz.tu-berlin.de
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 13 Oct 2006 10:55:04 -0700
From: carmstrong@cbamedia.com
Subject: 500 Chunked must be last Transfer-Encoding 'identity'
Message-Id: <1160762104.215320.255070@k70g2000cwa.googlegroups.com>
I'm trying to use the tor proxy with LWP. I keep getting the message:
"500 Chunked must be last Transfer-Encoding 'identity'"
Does anybody know what that means and how to solve that. (FYI the tor
proxy works fine with a browser).
My code is:
#!/usr/bin/perl #-w
use strict;
use LWP::UserAgent;
my $ua = new LWP::UserAgent;
$ua->proxy('http', 'http://127.0.0.1:8118' );
my $url = 'http://www.google.com/';
my $response = $ua->get($url);
print $response->content;
Thanks
------------------------------
Date: Fri, 13 Oct 2006 13:45:57 GMT
From: "Rohan Almeida" <rohan@almeida.in>
Subject: ANNOUNCE - Perl module Google::Adwords v0.4
Message-Id: <J72y2o.uwn@zorch.sf-bay.org>
Hi All,
I'm pleased to announce the release of v0.4 of Google::Adwords
Perl module. Major change is the use of v6 of the Adwords API.
The token method is no longer supported, in favour of the
developerToken and applicationToken methods.
Description
-----------------
This collection of modules under Google::Adwords provides
an easy to use object oriented interface to the Google Adwords
SOAP API. You don't need to understand SOAP or web
services to use this module.
Changes since v0.2
------------------------------
- implements the AccountService and CreativeService API calls
- uses v6 of the Adwords API
- token method deprecated in favour of developerToken
- added method applicationToken
- getUnitCountForClients method added to the InfoService module
- Following modules were added to the distribution
* Google::Adwords::AccountInfo
* Google::Adwords::AccountService
* Google::Adwords::Address
* Google::Adwords::ClientUsageRecord
* Google::Adwords::CoverageType
* Google::Adwords::Creative
* Google::Adwords::CreativeService
* Google::Adwords::CreditCard
* Google::Adwords::EmailPromotionsPreferences
* Google::Adwords::Image
Please visit http://search.cpan.org/~rohan/Google-Adwords-v0.4.0/ for
documentation of all the modules.
You can install this module via cpan, or download it from -
http://prdownloads.sourceforge.net/google-adwords/Google-Adwords-v0.4...
Thanks,
Rohan
http://rohan.almeida.in
------------------------------
Date: 13 Oct 2006 08:41:57 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Martijn Lievaart <m@rtij.nl>
Subject: Re: bless an object in a BEGIN block (Singleton)
Message-Id: <867iz4i5oa.fsf@blue.stonehenge.com>
>>>>> "Martijn" == Martijn Lievaart <m@remove.this.part.rtij.nl> writes:
Martijn> Gang of Four, the authors of "Design Patterns". One of those books
Martijn> every programmer should read.
And then ignored for the most part in Perl, because it was written about
things that had to be done awkardly in C++ and Java that are usually trivial
in Perl.
Every language has things it does well (inherently, perhaps), and things it
does poorly. Every language will thus develop its own collection of "recipes"
over time of how to do things that aren't one-liners. An example of that is
the Perl Cookbook and Perl Best Practices for basic Perl, or things like the
examples section of poe.perl.org for the POE framework.
It's a mistake to presume that GoF is "universal" in some way.
A far closer non-Perl book to serve as a model for Perl patterns is "Smalltalk
Best Practice Patterns" by Kent Beck, probably now out of print but you can
find it at better bookstores around. Smalltalk (late-binding) is a much
closer fit to Perl than either C++ or Java (compile-time binding), so the
problems and solutions are much more similar. I wrote about this in a recent
column (http://www.stonehenge.com/merlyn/LinuxMag/col84.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!
--
Posted via a free Usenet account from http://www.teranews.com
------------------------------
Date: 13 Oct 2006 09:19:58 -0700
From: "sc" <sc@rimple.net>
Subject: Re: bless an object in a BEGIN block (Singleton)
Message-Id: <1160756398.237085.271920@b28g2000cwb.googlegroups.com>
Hi Davy,
Do you mean the code like this:
{
package Person;
my $instance;
sub new {
my ($class, $name) = @_;
$instance = bless \$name, $class unless ref $instance;
return $instance;
}
sub name {
$self = shift;
$$self;
}
}
my $me = Person->new("hello");
my $you = Person->new("world"); # Only one Person can be created
print $me->name, " ", $you->name, "\n";
On Oct 13, 3:02 pm, "Davy" <zhushe...@gmail.com> wrote:
> Hi all,
>
> A perl design pattern document talk about Singleton.
> (http://www.perl.com/pub/a/2003/06/13/design1.html?page=2)
>
> My problem is what's the BEGIN block mean? I just can not find it in
> Perl Doc.
>
> package Name;
> my $singleton;
> BEGIN {
> $singleton = {
> attribute => 'value',
> another => 'something',
> };
> bless $singleton, "Name";}sub new {
> my $class = shift;
> return $singleton;
>
> }About Singleton: GoF calls the special case when there is a single
> resource that everyone needs to share the singleton pattern. Perhaps
> the resource is a hash of configuration parameters. Everyone should be
> able to look there, but it should only be built on startup (and
> possibly rebuilt on some signal).
>
> Best regards,
> Davy
------------------------------
Date: 13 Oct 2006 07:55:01 -0700
From: don.hosek@gmail.com
Subject: Re: Data inheritence with classes in Perl
Message-Id: <1160751301.408768.193000@e3g2000cwe.googlegroups.com>
anno4000@radom.zrz.tu-berlin.de wrote:
> > $bar_of{$self}=6;
>
> The line above is wrong in two ways.
>
> You are not supposed to access the attribute hashes of other classes
> directly.
This is an unfortunate bit of perl dogma. In general, yes, this is
true, but it's not always the case that we want to do this. In
particular, a base class may set up a standard data structure which is
then provided different methods for the derived classes.
An example, I may have a class BitmapFont which sets up a common data
structure for typeface data, then have derived classes BitmapFont::PK
BitmapFont::PXL BitmapFont::BDF etc. which provide different read and
write methods for reading from or writing to disk, but are otherwise
identical in their implementations. In a language with data
inheritence, this is no big deal. In Perl, there is a level of
indirection which is required. I had missed the automatic generation of
get_ and set_ methods, but this has the problem that I've just exposed
getting and setting my data not just within my hierarchy but to anyone
who comes along as well (I rarely provide any access to the data
structures of my classes to anyone but a class and its children). The
overhead should generally be low, except in the case where what I
really want is, for example, the size of an array rather than the array
(or is perl good enough in its parsing that if get_foo() returns an
array and I say $bar=$baz->get_foo() that it'll return the size of that
array for me rather than sending back the array and then calculating
its size?
-dh
------------------------------
Date: 13 Oct 2006 16:20:06 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Data inheritence with classes in Perl
Message-Id: <4p9slmFhs7neU1@news.dfncis.de>
<don.hosek@gmail.com> wrote in comp.lang.perl.misc:
>
> anno4000@radom.zrz.tu-berlin.de wrote:
> > > $bar_of{$self}=6;
> >
> > The line above is wrong in two ways.
> >
> > You are not supposed to access the attribute hashes of other classes
> > directly.
>
> This is an unfortunate bit of perl dogma. In general, yes, this is
> true, but it's not always the case that we want to do this. In
> particular, a base class may set up a standard data structure which is
> then provided different methods for the derived classes.
It's not a dogma but a consequence of the way OO is implemented in perl.
If you want encapsulation, you *must* exclude direct access to
attributes. Inside-out classes (the type you're using) were invented
to enforce encapsulation, among other things.
> An example, I may have a class BitmapFont which sets up a common data
> structure for typeface data, then have derived classes BitmapFont::PK
> BitmapFont::PXL BitmapFont::BDF etc. which provide different read and
> write methods for reading from or writing to disk, but are otherwise
> identical in their implementations. In a language with data
> inheritence, this is no big deal.
inheritance
> In Perl, there is a level of
> indirection which is required.
What do you mean? Going through the accessors instead of accessing
the data directly? If that is prohibitive overhead then (that part
of) the program probably shouldn't be written in Perl in the first
place.
Otherwise, Perl allows you to do just that (break encapsulation)
if you think you need to. Just not with properly implemented
inside-out classes, so in that case you'd be better off with a
traditional implementation of an object-as-a-hash.
>I had missed the automatic generation of
> get_ and set_ methods, but this has the problem that I've just exposed
> getting and setting my data not just within my hierarchy but to anyone
> who comes along as well (I rarely provide any access to the data
> structures of my classes to anyone but a class and its children).
In Perl (5) all methods are public. Derived classes don't have any
privileges. The accepted way is to give methods that are meant to be
private a name that starts with an underline. That indicates privacy,
but doesn't enforce it.
It makes no difference whether the methods are auto-generated. You could
write their exact equivalent yourself and the behavior would be no
different.
> The
> overhead should generally be low, except in the case where what I
> really want is, for example, the size of an array rather than the array
> (or is perl good enough in its parsing that if get_foo() returns an
> array and I say $bar=$baz->get_foo() that it'll return the size of that
> array for me rather than sending back the array and then calculating
> its size?
It works exactly like that if what you return is an actual array
(not a list). It also works when the return value is the result of
grep() or map(). Perl context powerful and noiseless.
Anno
------------------------------
Date: 13 Oct 2006 09:30:14 -0700
From: "sc" <sc@rimple.net>
Subject: Re: Data inheritence with classes in Perl
Message-Id: <1160757014.798432.53250@h48g2000cwc.googlegroups.com>
Hi,
It's better for you to read the section 8.3 of Advanced Perl
Programming, 1st edition.
C++ uses "attribute inheritance", and Perl does not support it.
-sc
On Oct 13, 12:01 pm, don.ho...@gmail.com wrote:
> As I'm getting a bit deeper into working with some object-oriented
> design in Perl, I'm running into a big problem with how I deal with
> things: In, say C++, I could have
>
> class foo {
> protected int bar
>
> }class baz : public foo {
> void mymethod {
> bar=6;
> }
>
> }to give a grossly simplified example of what I'd like to do. But by
> default, there is no data inheritence in perl. So if I have
>
> package foo;
> use Class::Std;
> my %bar_of : ATTR;
>
> package baz;
> use Class::Std;
> use base qw(foo);
>
> sub mymethod {
> my $self=shift;
> $bar_of{$self}=6;
>
> }Won't work. What would the best way of dealing with this be?
------------------------------
Date: Fri, 13 Oct 2006 16:03:37 +0200
From: Martijn Lievaart <m@remove.this.part.rtij.nl>
Subject: Re: FAQ 4.36 How can I expand variables in text strings?
Message-Id: <pan.2006.10.13.14.03.37.412796@remove.this.part.rtij.nl>
On Fri, 13 Oct 2006 09:53:00 +0000, anno4000 wrote:
> Martijn Lievaart <m@remove.this.part.rtij.nl> wrote in
> comp.lang.perl.misc:
>> On Thu, 12 Oct 2006 18:03:02 -0700, PerlFAQ Server wrote:
>>
>> > Let's assume that you have a string that contains placeholder
>> > variables.
>> >
>> > $text = 'this has a $foo in it and a $bar';
>> >
>> > You can use a substitution with a double evaluation. The first /e
>> > turns $1 into $foo, and the second /e turns $foo into its value.
>> > You may want to wrap this in an "eval": if you try to get the
>> > value of an undeclared variable while running under "use strict",
>> > you get a fatal error.
>> >
>> > eval { $text =~ s/(\$\w+)/$1/eeg };
>> > die if $@;
>>
>> What is wrong with
>> $text = eval "$text";
>
> It's utter nonsense, that's what's wrong. Take the time to run your code
> at least once before posting.
Sorry, wasn't thinking to clearly. I ment eval "\"$text\"";
#/usr/bin/perl
use strict;
use warnings;
my ($foo, $bar) = qw(x y);
my $text = 'this has a $foo in it and a $bar';
$text = eval "\"$text\"";
die $@ if $@;
print $text;
And the answer obviously is, it breaks when there is a " in the string.
M4
--
Redundancy is a great way to introduce more single points of failure.
------------------------------
Date: 13 Oct 2006 16:33:50 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: FAQ 4.36 How can I expand variables in text strings?
Message-Id: <4p9tfeFhvj92U1@news.dfncis.de>
Martijn Lievaart <m@remove.this.part.rtij.nl> wrote in comp.lang.perl.misc:
> On Fri, 13 Oct 2006 09:53:00 +0000, anno4000 wrote:
>
> > Martijn Lievaart <m@remove.this.part.rtij.nl> wrote in
> > comp.lang.perl.misc:
> >> On Thu, 12 Oct 2006 18:03:02 -0700, PerlFAQ Server wrote:
> >>
> >> > Let's assume that you have a string that contains placeholder
> >> > variables.
> >> >
> >> > $text = 'this has a $foo in it and a $bar';
> >> >
> >> > You can use a substitution with a double evaluation. The first /e
> >> > turns $1 into $foo, and the second /e turns $foo into its value.
> >> > You may want to wrap this in an "eval": if you try to get the
> >> > value of an undeclared variable while running under "use strict",
> >> > you get a fatal error.
> >> >
> >> > eval { $text =~ s/(\$\w+)/$1/eeg };
> >> > die if $@;
> >>
> >> What is wrong with
> >> $text = eval "$text";
> >
> > It's utter nonsense, that's what's wrong. Take the time to run your code
> > at least once before posting.
>
> Sorry, wasn't thinking to clearly. I ment eval "\"$text\"";
>
> #/usr/bin/perl
>
> use strict;
> use warnings;
>
> my ($foo, $bar) = qw(x y);
> my $text = 'this has a $foo in it and a $bar';
> $text = eval "\"$text\"";
> die $@ if $@;
> print $text;
>
> And the answer obviously is, it breaks when there is a " in the string.
You must also be sure what the string contains. It could be
'this has a $foo in it and it removes /tmp/x @{ [ `rm /tmp/x`] }'
$foo and $bar are not dangerous in this way. They are only interpolated,
not evaluated.
Anno
------------------------------
Date: 13 Oct 2006 13:38:09 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Help with test program
Message-Id: <4p9j61Fhiqj3U1@news.dfncis.de>
<joubertb@gmail.com> wrote in comp.lang.perl.misc:
> I have been working on this for the past few days and still can't
> figure out what I am doing wrong.
>
> Below the my test program. Can someone point out to me what I am doing
> wong?
>
> Thanks.
>
> --joubert
>
> ===========================< cut here >===============================
>
> package foobar;
No strict? No warnings?
> sub new {
> my $class = shift;
> my $self = {};
>
> return bless $self, $class;
> }
>
> sub func {
> my $self = shift;
> my $param = shift;
> print "inside function\n";
>
> print "param=$param\n";
>
> return "zzzzz";
> }
>
>
> $f = new foobar;
Better written as
$f = foobar->new;
>
> my %myarray = (
It's a hash. Why call it an array?
> foo => { func => $f->func, }
> );
> #
> # When I do the above assignment, it calls the method $f->func. What I
> want it to do is assign the
> # function pointer to func so that below I can call it.
> #
What function pointer? Perl has coderefs (hard and symbolic). These
are not the same as C function pointers.
Further, the role of $f in the game isn't clear. Should all future
calls call ->func with this particular object? With what arguments?
I'll assume you want to supply arguments at the time of the later
call. Then store it as (untested)
$myarray{ foo} = { func => sub { $f->func( @_) } };
and call as
$myarray{ foo}->{ func}->( $arg1, $arg2);
(Yes, you can leave out the arrows between parentheses. I prefer to
out them.)
Anno
------------------------------
Date: 13 Oct 2006 13:52:58 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Help with test program
Message-Id: <4p9k1qFhrfpjU1@news.dfncis.de>
Charles DeRykus <ced@blv-sam-01.ca.boeing.com> wrote in comp.lang.perl.misc:
> Peter J. Holzer wrote:
> > On 2006-10-08 20:47, joubertb@gmail.com <joubertb@gmail.com> wrote:
> The OP may want to take a look at the "Creating References to Methods"
> and "Calling Methods Indirectly" recipes in the "Perl Cookbook" for some
> further background.
>
> The recipe has an explanation of why 'can' is unlikely to do what you
> want since object context is lost. Yet something like this appears to
> work and retains object context partially.
What exactly do you mean by "object context" and how is it "partially
retained"? The result of $f->can( 'func') is a coderef, pure and
simple. No trace of the particular object ($f) is left in it.
> my %myarray = ( foo => { func => $f->can('func') } );
> my $funcptr = $myarray{foo}{func};
> my $xxx = $f->$funcptr("abc123");
>
> If @ISA were changed, the recommended method would pick up the change;
> whereas, the 'can' solution wouldn't. But,if @ISA remains intact,
> can anyone cite possible flaws with the 'can' ref...?
Right, method resolution happens when the value is stored in %myarray,
not at call time.
The way I understand the OP, the particular object should also be cached
in %myarray. If so, your ->can method can't be used as given. That's
not so much a flaw than a limitation. You'd have to store $f
independently and construct the call accordingly. Method resolution
would still happen early. Storing
sub { $f->func( @_) }
both keeps the value of $f and does method resolution at call time,
at the cost of another sub call.
Anno
------------------------------
Date: Fri, 13 Oct 2006 10:15:41 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: openGL 0.5 perl module problem, again
Message-Id: <452fad39$0$25773$815e3792@news.qwest.net>
thedwig@gmail.com wrote:
> hi.
>
> %tar -xvf OpenGL-0.5.tar.gz
> %cd OpenGL-0.5
> %perl Makefile.PL
>
> and then i met messages.....
>
> Note (probably harmless): No library found for -lGLUT
> Note (probably harmless): No library found for -lGLX
> Note (probably harmless): No library found for -lMesaGLU
> Note (probably harmless): No library found for -lMesaGLUT
> Note (probably harmless): No library found for -lMesaGLX
> Note (probably harmless): No library found for -lXIE
>
> how can i solve this problem? help...
>
> ok. i got it- library isn't exist-
>
> but, how can i install this libraries (GLUT, GLX, etc.)???? -help
That isn't a perl question.
Find the libraries, either as source or binary, and install them
according to the documentation for your OS. Depending on your OS,
there may be a port or an RPM for some of them, otherwise use
your favorite search engine. Of course, if you actually
visited the link I sent in a previous post, it's likely you'd
have found a page, under "Coding Resources", for the libraries
and they seem to have a pretty handy Wiki where the libraries
are covered under "Getting Started".
Once you have them installed and have a perl question, feel free
to post them here. Helping you install graphics libraries is not
the purpose of this newsgroup.
------------------------------
Date: 13 Oct 2006 09:47:25 -0700
From: "ultimard@yahoo.com" <ultimard@yahoo.com>
Subject: Re: Probs with nested conditions
Message-Id: <1160758044.984460.60190@b28g2000cwb.googlegroups.com>
Thanks to all who replied, that indeed was my problem
using = instead of ==, I guess that is what happens when you do 95%
work in shell and 5% in perl.
------------------------------
Date: 13 Oct 2006 16:54:31 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Probs with nested conditions
Message-Id: <4p9um7Fhvj92U3@news.dfncis.de>
ultimard@yahoo.com <ultimard@yahoo.com> wrote in comp.lang.perl.misc:
>
> Thanks to all who replied, that indeed was my problem
> using = instead of ==, I guess that is what happens when you do 95%
> work in shell and 5% in perl.
Why?
Oh, and in csh it's == too.
Anno
------------------------------
Date: 13 Oct 2006 17:30:02 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: QUERY_STRING parsing and '$value =~ tr/+/ /;' treatment
Message-Id: <4pa0oqFgq12lU1@news.dfncis.de>
Yohan N Leder <ynl@nsparks.net> wrote in comp.lang.perl.misc:
> In article <Xns98569544EFBD4asu1cornelledu@127.0.0.1>,
> 1usa@llenroc.ude.invalid says...
[...]
> The question was not 'how to handle URLencoded data', but about non-
> URLencoded data... And Bill S. replied pertinently : GET is not for non-
> URLencoded data.
The question was, to recapitulate:
...treating extracted values with a "$value =~ tr/+/ /;" for
'unwebification' of the '+' signs.
But, this kind of treatment will corrupt any QUERY_STRING
content which is not simple text (for example, I've done
test on base64 data).
So, how does CGI.pm handle this ? ...
> > Given that you can look at the CGI.pm source code yourself, I am not
> > sure why you have to ask this here.
> >
>
> Of course, everybody can always do without the others, but it may help
> to gain time
Now this is plain arrogant!
Given the question, even the module author would have to look at the
source code to answer it reliably, far more an average Joe who tries
to answer general questions on clpm. A little thought on your side
would have told you so. Translation: I don't have the time to look
it up, so would some of you guys do it for me?
Anno
------------------------------
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 9843
***************************************
