[29860] in Perl-Users-Digest
Perl-Users Digest, Issue: 1103 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Dec 10 21:09:41 2007
Date: Mon, 10 Dec 2007 18:09:06 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Mon, 10 Dec 2007 Volume: 11 Number: 1103
Today's topics:
Re: "use constant X=>(1,2);" or "use constant X=>[1,2]; <kingskippus@gmail.com>
Re: "use constant X=>(1,2);" or "use constant X=>[1,2]; <glex_no-spam@qwest-spam-no.invalid>
Re: "use constant X=>(1,2);" or "use constant X=>[1,2]; <kingskippus@gmail.com>
Re: comparing binary strings <joost@zeekat.nl>
Re: comparing binary strings <ben@morrow.me.uk>
Re: comparing binary strings <joost@zeekat.nl>
Re: comparing binary strings <joost@zeekat.nl>
Re: comparing binary strings <rvtol+news@isolution.nl>
Re: How can I print a number larger than 128? <kingskippus@gmail.com>
Re: How to execute tar inside a perl script ? <StaminaJ@nowhere.com>
Re: How to execute tar inside a perl script ? <joost@zeekat.nl>
Re: How to execute tar inside a perl script ? <ben@morrow.me.uk>
Re: How to execute tar inside a perl script ? <joost@zeekat.nl>
Re: How to execute tar inside a perl script ? <ben@morrow.me.uk>
Re: How to execute tar inside a perl script ? <joost@zeekat.nl>
Re: Problem in LDAP authentication <rkb@i.frys.com>
Re: Problem in LDAP authentication <glex_no-spam@qwest-spam-no.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 10 Dec 2007 14:17:41 -0800 (PST)
From: TonyV <kingskippus@gmail.com>
Subject: Re: "use constant X=>(1,2);" or "use constant X=>[1,2];"?
Message-Id: <554a6737-575b-402f-a528-4ae2cc33d2cc@e10g2000prf.googlegroups.com>
On Dec 8, 12:44 pm, Victor Porton <por...@narod.ru> wrote:
> What's better?
>
> use constant X=>(1,2);
>
> or
>
> use constant X=>[1,2];
Honestly? The best practices I've read say that the best of all is:
my @X = (1, 2);
In the first form X=>(1,2), you'll have to make sure X is in
parentheses to get at the values:
my $foo_1 = (X)[0];
my $foo_2 = (X)[1];
In the second form, you'll have to use the arrow operator to get at
the values:
my $foo_1 = X->[0];
my $foo_2 = X->[1];
If you just declare it as a normal variable, people won't wonder what
your code is trying to do, as it will appear as the standard:
my $foo_1 = $X[0];
my $foo_2 = $X[1];
Maybe not the most ideal answer, but I think it's probably the most
clear one (and thus the "best" one) to use.
------------------------------
Date: Mon, 10 Dec 2007 16:29:10 -0600
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: "use constant X=>(1,2);" or "use constant X=>[1,2];"?
Message-Id: <475dbdb6$0$493$815e3792@news.qwest.net>
TonyV wrote:
> On Dec 8, 12:44 pm, Victor Porton <por...@narod.ru> wrote:
>> What's better?
>>
>> use constant X=>(1,2);
>>
>> or
>>
>> use constant X=>[1,2];
>
> Honestly? The best practices I've read say that the best of all is:
> my @X = (1, 2);
TonyV. Honestly, first you should read
perldoc constant
so you understand what it provides, before you comment
on what's the 'best'.
------------------------------
Date: Mon, 10 Dec 2007 14:46:42 -0800 (PST)
From: TonyV <kingskippus@gmail.com>
Subject: Re: "use constant X=>(1,2);" or "use constant X=>[1,2];"?
Message-Id: <e584f967-d456-47a9-a6b3-8e2af9e9f492@w28g2000hsf.googlegroups.com>
On Dec 10, 5:29 pm, "J. Gleixner" <glex_no-s...@qwest-spam-no.invalid>
wrote:
> TonyV. Honestly, first you should read
>
> perldoc constant
>
> so you understand what it provides, before you comment
> on what's the 'best'.
Actually, what I read a long time ago was O'Reilly's "Perl Best
Practices," section 4.5: Use named constants, but don't use
"constant". (I.e. the constant pragma.) It follows with several good
reasons why using the constant pragma is generally not as good an idea
as other things, such as constants not being able to be interpolated,
constants being difficult to use where bareword strings are accepted,
and constants being package-scoped instead of lexically-scoped, which
can cause weirdities if you don't know what you're doing.
The book actually recommends using the Readonly module instead, but
generally, the easiest thing by far to do, in my opinion, is to just
not use constants.
Obviously, you're free to disagree and use constants to your heart's
content, but I'm not just making this up out of nowhere, and I have
read the documentation. I just happen to agree with O'Reilly's best
practices book on this one and think that constants in Perl are more
trouble than they're worth, at least through version 5.8, which is
what I use.
------------------------------
Date: 10 Dec 2007 16:34:00 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: comparing binary strings
Message-Id: <475d6a78$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 14:27:12 +0000, Ben Morrow wrote:
> Quoth Yakov <iler.ml@gmail.com>:
>> , and I need to ensure that comparison (lt, gt) of those strings not
>> depend on locale and not be utf-8 interpreted.
Don't use locales then. For the purposes of lt and gt and eq it's
irrelevant wether the strings are utf-8 encoded or not.
If you want to be able to output them as bytes, just don't insert any
chars > 255.
> Don't attempt to mix POSIX locales and Perl's UTF8 support. The two
> don't play well together at all yet.
Yup.
>> How can I "label" thise string "raw binary" in CreateEightByteString
>> so that any subsequent comparison be as raw binary 8 bytes, independent
>> on program's locale ?
>
> You can't. You need to perform *the comparisons* under 'use bytes'.
No, you don't need to. The only time the encoding of the strings is
important is when you're passing them to external code as a C-style char*
pointer. Or at least it should be.
In general, I'd say: don't use bytes. It breaks stuff - for instance, it
makes it impossible to compare an utf-8 encoded string with a non-utf8
encoded one.
> If you aren't using locales, and you call CreateEightByteString under
> 'use bytes', you will get byte-strings back. If you only mix these with
> other byte-strings, they will stay that way.
As long as you're reading and writing to filehandles that have the
correct encoding layer the internal encoding of the strings doesn't
matter to perl code.
Joost.
------------------------------
Date: Mon, 10 Dec 2007 21:38:02 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: comparing binary strings
Message-Id: <q6o035-am4.ln1@osiris.mauzo.dyndns.org>
Quoth Joost Diepenmaat <joost@zeekat.nl>:
> On Mon, 10 Dec 2007 14:27:12 +0000, Ben Morrow wrote:
>
> > You can't. You need to perform *the comparisons* under 'use bytes'.
>
> No, you don't need to. The only time the encoding of the strings is
> important is when you're passing them to external code as a C-style char*
> pointer. Or at least it should be.
I agree, it should be; it's not, however. For instance, under 5.8.8, a
string containing "\xc1" (capital A acute) will match /\w/ if it is
utf8-encoded and not if its not. I'm not sure if this is fixed in 5.10;
I'm not sure, either, what the correct fix would be.
Ben
------------------------------
Date: 10 Dec 2007 22:03:43 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: comparing binary strings
Message-Id: <475db7bf$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 21:38:02 +0000, Ben Morrow wrote:
> Quoth Joost Diepenmaat <joost@zeekat.nl>:
>> On Mon, 10 Dec 2007 14:27:12 +0000, Ben Morrow wrote:
>>
>> > You can't. You need to perform *the comparisons* under 'use bytes'.
>>
>> No, you don't need to. The only time the encoding of the strings is
>> important is when you're passing them to external code as a C-style
>> char* pointer. Or at least it should be.
>
> I agree, it should be; it's not, however. For instance, under 5.8.8, a
> string containing "\xc1" (capital A acute) will match /\w/ if it is
> utf8-encoded and not if its not. I'm not sure if this is fixed in 5.10;
> I'm not sure, either, what the correct fix would be.
Hm... You're right. That's not good, and arguably a bug (and with some
heavy backward-compatibility considerations). It doesn't say anything
about binary strings, though.
I'll give it a shot in the latest blead perl (once I've got and compiled
it) to see what's what.
Joost.
------------------------------
Date: 10 Dec 2007 22:53:47 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: comparing binary strings
Message-Id: <475dc37b$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 22:03:43 +0000, Joost Diepenmaat wrote:
> I'll give it a shot in the latest blead perl (once I've got and compiled
> it) to see what's what.
>
:-/ Perl 5.10 rc-2 still does the same.
Joost.
------------------------------
Date: Tue, 11 Dec 2007 02:49:14 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: comparing binary strings
Message-Id: <fjku39.1r0.1@news.isolution.nl>
Joost Diepenmaat schreef:
> Ben Morrow:
>> Joost Diepenmaat:
>>> Ben Morrow:
>>>> You can't. You need to perform *the comparisons* under 'use bytes'.
>>>
>>> No, you don't need to. The only time the encoding of the strings is
>>> important is when you're passing them to external code as a C-style
>>> char* pointer. Or at least it should be.
>>
>> I agree, it should be; it's not, however. For instance, under 5.8.8,
>> a string containing "\xc1" (capital A acute) will match /\w/ if it is
>> utf8-encoded and not if its not. I'm not sure if this is fixed in
>> 5.10; I'm not sure, either, what the correct fix would be.
>
> Hm... You're right. That's not good, and arguably a bug (and with some
> heavy backward-compatibility considerations). It doesn't say anything
> about binary strings, though.
"\xA0" is whitespace in iso-8859-1:
perl -wle'
print 0+/^[\s\w]/
for "\xC1",
"\xC1\x{100}",
"\xA0",
"\xA0\x{100}",
substr("\xA0\x{100}", 0, 1),
'
0
1
0
1
1
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Mon, 10 Dec 2007 14:02:32 -0800 (PST)
From: TonyV <kingskippus@gmail.com>
Subject: Re: How can I print a number larger than 128?
Message-Id: <1050d2ca-fdd9-4383-a6d8-feb3eda01927@e10g2000prf.googlegroups.com>
On Dec 10, 10:07 am, Q...@domain.invalid wrote:
> spamb...@milmac.com (Doug Miller) wrote in message-id: <dH97j.76990$YL5.33...@newssvr29.news.prodigy.net>
>
> > In article <pan.2007.12.09.23.08...@rtij.nl.invlalid>, Martijn Lievaart <m...@rtij.nl.invlalid> wrote:
> > >On Sun, 09 Dec 2007 22:25:59 +0000, Doug Miller wrote:
>
> > >>>> >The one byte constraint is more than a bit limiting though.
>
> > >>>> Huh? One byte = 8 bits, which can hold values up to 2^8 - 1 = 255. All
> > >>>> he needs to do is send it in binary.
>
> > >>>cause the OP says that he wishes to send _only one byte_
>
> > >> And your point would be....?
>
> > >> 255 > 128, last time I checked.
>
> > >Ah I see it now. The OP wants to send a number GREATER than 128.
>
> > Wouldn't matter if he wanted to send a number less than 128. As long as it's
> > in the range 0..255, one byte is sufficient to express it. If it's out of that
> > range, it's not, and no compression algorithm is going to change that.
>
> Clocking.
>
> Assume for a moment that the sending software and receiving software both
> have hardcoded a _timing_ mechanism (asynchronous transmission).
>
> Now the sending client starts the timer by sending its first bit, lets say
> it is a zero, the sender will now not send any more bits until the value
> of the bit is to change (lets say 14 cycles).
>
> The receiver should now have a number like this, although it has received
> only 1 bit. (the initial bit and 14 repetitions of that bit.)
>
> 0000000 00000000
>
> Now the sender sends the next bit to indicate a change from 0 to 1.
> Perhaps this time the sends waits 2 cycles after sending.
>
> The reciever should now have a number like this, and we have sent
> only 2 bits so far.
>
> 11 10000000 00000000
>
> Some ethernet encodings work in a similar fashion to this.
>
> Many more ways to do this.. gl
I think the user just wants to be able to send binary data. This
algorithm sounds way over the top of what he's asking.
In short, to send an integer using n bytes in a conventional manner,
the integer will need to be between 0 and 2^(8*n) - 1. One byte will
accommodate an integer between 0 and 255. Two bytes will accommodate
an integer between 0 and 65535. Three bytes will... Well, you get
the idea.
I think smallpond has the exact answer the OP is looking for.
------------------------------
Date: Mon, 10 Dec 2007 14:39:12 -0600
From: aaah <StaminaJ@nowhere.com>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <V6ednYCVgMZtPsDaRVnyigA@giganews.com>
This is a correct, but it's prob worth expanding on this slightly to
get you going, from within your code, try the following:
my $tar_cmd = "tar czvf "/usr/local/myname/$tarfile" ./*.php" ;
my $result = system($tar_cmd) ;
If $result ends up being non - zero then you have an issue. For
more info on manipulating the external commands, see the cookbook.
On Mon, 10 Dec 2007 12:59:34 +0000, Matthew Lincoln wrote:
> When I code in a perl script
>
> tar czvf "/usr/local/myname/$tarfile" ./*.php
perl isn't a shell. tar isn't a perl function. czvf can be all kinds
of
things in perl. If you want to execute an external commmand and
interpolate wildcards via the shell you have to explicitly say so.
> So how do I correctly execute a tar command from within a perl
script ?
http://perldoc.perl.org/functions/system.html
Joost.
--
--------------------------------- --- -- -
Posted with NewsLeecher v3.9 Beta 6
Web @ http://www.newsleecher.com/?usenet
------------------- ----- ---- -- -
------------------------------
Date: 10 Dec 2007 20:46:53 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <475da5bd$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 14:39:12 -0600, aaah wrote:
> This is a correct, but it's prob worth expanding on this slightly to get
> you going, from within your code, try the following:
>
> my $tar_cmd = "tar czvf "/usr/local/myname/$tarfile" ./*.php" ;
That's not valid perl. You probably mean
my $tar_cmd = "tar czvf /usr/local/myname/$tarfile ./*.php" ;
Joost.
------------------------------
Date: Mon, 10 Dec 2007 21:44:01 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <1io035-am4.ln1@osiris.mauzo.dyndns.org>
Quoth Joost Diepenmaat <joost@zeekat.nl>:
> On Mon, 10 Dec 2007 14:39:12 -0600, aaah wrote:
>
> > This is a correct, but it's prob worth expanding on this slightly to get
> > you going, from within your code, try the following:
> >
> > my $tar_cmd = "tar czvf "/usr/local/myname/$tarfile" ./*.php" ;
>
> That's not valid perl. You probably mean
>
> my $tar_cmd = "tar czvf /usr/local/myname/$tarfile ./*.php" ;
No, he probably meant
my $tar_cmd = qq{tar czvf "/usr/local/myname/$tarfile" ./*.php};
as the "" are important. It would be *much* better to use the list form
of system: it avoids all these nasty quoting issues, including the one
you haven't noticed yet when you have a file 'My Script.php'.
system tar => czvf => "/usr/local/myname/$tarfile", <*.php>;
(handling the return value left as an exercise for the reader, as it's a
pain :).)
Ben
------------------------------
Date: 10 Dec 2007 21:57:53 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <475db661$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 21:44:01 +0000, Ben Morrow wrote:
> Quoth Joost Diepenmaat <joost@zeekat.nl>:
>> On Mon, 10 Dec 2007 14:39:12 -0600, aaah wrote:
>>
>> > This is a correct, but it's prob worth expanding on this slightly to
>> > get you going, from within your code, try the following:
>> >
>> > my $tar_cmd = "tar czvf "/usr/local/myname/$tarfile" ./*.php" ;
>>
>> That's not valid perl. You probably mean
>>
>> my $tar_cmd = "tar czvf /usr/local/myname/$tarfile ./*.php" ;
>
> No, he probably meant
>
> my $tar_cmd = qq{tar czvf "/usr/local/myname/$tarfile" ./*.php};
Which won't work, because it won't interpolate ./*.php. Which sort of
proves both our points :-)
>
> as the "" are important. It would be *much* better to use the list form
> of system: it avoids all these nasty quoting issues, including the one
> you haven't noticed yet when you have a file 'My Script.php'.
>
> system tar => czvf => "/usr/local/myname/$tarfile", <*.php>;
Yes, that would work, and more reliably than all the crap above. (though
I don't like => to quote strings except in very idiomatic constructs).
Joost.
------------------------------
Date: Mon, 10 Dec 2007 22:12:36 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <k7q035-q15.ln1@osiris.mauzo.dyndns.org>
Quoth Joost Diepenmaat <joost@zeekat.nl>:
> On Mon, 10 Dec 2007 21:44:01 +0000, Ben Morrow wrote:
>
> > Quoth Joost Diepenmaat <joost@zeekat.nl>:
> >> On Mon, 10 Dec 2007 14:39:12 -0600, aaah wrote:
> >>
> >> > This is a correct, but it's prob worth expanding on this slightly to
> >> > get you going, from within your code, try the following:
> >> >
> >> > my $tar_cmd = "tar czvf "/usr/local/myname/$tarfile" ./*.php" ;
> >>
> >> That's not valid perl. You probably mean
> >>
> >> my $tar_cmd = "tar czvf /usr/local/myname/$tarfile ./*.php" ;
> >
> > No, he probably meant
> >
> > my $tar_cmd = qq{tar czvf "/usr/local/myname/$tarfile" ./*.php};
>
> Which won't work, because it won't interpolate ./*.php. Which sort of
> proves both our points :-)
Yes it will. That is, ./*.php will be passed literally to the shell,
which will then expand it before calling tar. This is why $tarfile needs
two levels of quoting, with qq{} (for Perl) and "" (for the shell).
Ben
------------------------------
Date: 10 Dec 2007 22:23:03 GMT
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: How to execute tar inside a perl script ?
Message-Id: <475dbc47$0$31825$e4fe514c@dreader26.news.xs4all.nl>
On Mon, 10 Dec 2007 21:57:53 +0000, Joost Diepenmaat wrote:
> Which won't work, because it won't interpolate ./*.php. Which sort of
> proves both our points :-)
Scratch that. ofcourse it will work.
Joost.
------------------------------
Date: Mon, 10 Dec 2007 10:45:46 -0800 (PST)
From: Ron Bergin <rkb@i.frys.com>
Subject: Re: Problem in LDAP authentication
Message-Id: <16cdca2a-b0f2-4a98-854d-29f791b52a9f@s12g2000prg.googlegroups.com>
I haven't done much with LDAP, so I'll leave that to others that have
more experience with it, but I'll touch on a couple other parts of
your script.
On Dec 10, 7:50 am, Praki <visitprakashin...@gmail.com> wrote:
>
> > as it is known user i tried with the last two stpes.here is the full
> > code i m using.
>
> > #!/usr/local/bin/perl5
> > &top();
> > &login_check();
> > &bottom();
No need to use both & and ( ) remove one or the other. My preference
is to use the () parens.
> > sub top{
> > print <<EOM1;
> > Content-type: text/html
>
> > <html>
> > <head>
> > <title>Login Authentication</title>
> > </head>
> > <body>
> > EOM1}
I'd drop the sub and use the CGI module instead, which will make this
cleaner and easier.
use CGI;
my $cgi = CGI->new; # I prefer the OO methods rather than the
functional approach.
print $cgi->header, $cgi->start_html('Login Authentication');
>
> > sub bottom{
> > print <<EOM2;
> > </body>
> > </html>
> > EOM2}
Again, drop this sub.
print $cgi->end_html;
>
> > sub login_check{
>
> > use warnings;
> > use strict;
> > use Net::LDAP;
Move these use statements to the beginning of the script so they will
be loaded at compile time instead of runtime.
>
> > my ($userid,$ldap,$mesg,@entries,@attrs,$attr,$entry);
> > $userid='prakash';
> > $ldap = Net::LDAP->new('ldap.abc.com', port=> '389');
>
> > $mesg = $ldap->bind('ou=active,ou=employees,ou=people,o=abc.com',userPassword =>
>
> > 'test');
>
> > $mesg = $ldap->search(filter=>"uid=$userid",
> > base=>"ou=active,ou=employees,ou=people,o=abc.com");
> > @entries = $mesg->entries;
> > foreach $entry (@entries) {
> > print "dn: " . $entry->dn() . "\n";
> > @attrs = $entry->attributes();
> > foreach $attr (@attrs) {
> > printf("\t%s: %s\n", $attr, $entry->get_value($attr));
> > }
> > }
>
> > }
>
> > $mesg = $ldap->bind('ou=active,ou=employees,ou=people,o=abc.com',userPassword =>
>
> > 'test');
I realize that a couple of the lines got wrapped in the positing, but
consistency and proper use of indentation and whitespace will make
your code easier to follow and maintain.
------------------------------
Date: Mon, 10 Dec 2007 13:09:18 -0600
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Problem in LDAP authentication
Message-Id: <475d8edf$0$499$815e3792@news.qwest.net>
Ron Bergin wrote:
[...]
> On Dec 10, 7:50 am, Praki <visitprakashin...@gmail.com> wrote:
>>> as it is known user i tried with the last two stpes.here is the full
>>> code i m using.
>>> #!/usr/local/bin/perl5
>>> &top();
>>> &login_check();
>>> &bottom();
> No need to use both & and ( ) remove one or the other. My preference
> is to use the () parens.
There are times to use '&' and times to use '()'. Correct usage should
be the deciding factor, not your 'preference'.
perldoc -q "What's the difference between calling a function as &foo and
foo()"
>>> sub login_check{
>>> use warnings;
>>> use strict;
>>> use Net::LDAP;
> Move these use statements to the beginning of the script so they will
> be loaded at compile time instead of runtime.
It doesn't matter where 'use' is located in the program, though
most would agree to put them at the top.
perldoc -f use
------------------------------
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 1103
***************************************
