[25692] in Perl-Users-Digest
Perl-Users Digest, Issue: 7933 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 1 14:05:23 2005
Date: Fri, 1 Apr 2005 11:05:08 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 1 Apr 2005 Volume: 10 Number: 7933
Today's topics:
"UNLOCK THE MOST POWERFUL SECRET TO DOUBLING YOUR SALES getresponses@gmail.com
Re: CD-R or CD-RW ? <nobull@mail.com>
Re: Need syntax/small footprint help <nobull@mail.com>
perl hangs after receiving signal <jeremy.slade@intel.com>
Re: perl hangs after receiving signal (Anno Siegel)
Re: Perl script hangs <nobull@mail.com>
Re: Perl script hangs (Anno Siegel)
Re: Perl script hangs <nobull@mail.com>
Re: Perl script hangs <matternc@comcast.net>
Re: Redirect on the NO pushing button <lawrence.tierney@bipcontracts.com>
Re: slicing syntax question (Anno Siegel)
Re: Unable to connect to remote host <lawrence.tierney@bipcontracts.com>
Re: Unable to connect to remote host <nobull@mail.com>
Re: Unable to connect to remote host <srithota@gmail.com>
Re: Using a for() statement to create a variable?? <nobull@mail.com>
Re: Using HTTPS with LWP::UserAgent = Bad Service <usenet@vyznev.invalid>
Re: using Perl to insert footer into PDF files? <sbryce@scottbryce.com>
Re: Why doesn't Perl have cp or mv? <bart.lateur@pandora.be>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 1 Apr 2005 09:54:45 -0800
From: getresponses@gmail.com
Subject: "UNLOCK THE MOST POWERFUL SECRET TO DOUBLING YOUR SALES!"
Message-Id: <1112378085.687703.280500@f14g2000cwb.googlegroups.com>
"UNLOCK THE MOST POWERFUL SECRET TO DOUBLING YOUR SALES!"
"With NEW intelligent software that's FREE and GUARANTEED!"
That secret is "follow up" -- but the trick is to be fast,
repetitive, personalized and consistent. New, sophisticated
autoresponder does all that for you ... And more! SAVE time
and money. GRAB YOUR FREE VERSION NOW! Marketers grab a
FREE report: "How to Double Your Sales With a Proper Email
Strategy"! Don't wait, click below NOW:
http://www.GetResponse.com/index/vphil
------------------------------
Date: Fri, 01 Apr 2005 17:49:18 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: CD-R or CD-RW ?
Message-Id: <d2k183$hr8$1@sun3.bham.ac.uk>
kielhd wrote:
> is there a way for Perl to find out, if a CD is a CD-R or a CD-RW?
If your operating system provides and interface that makes this
information available to applications then no doubt you can get at it
with Perl.
For example on Unix-like OSs there's probably an IOCTL you can use on
the device file correspoding to the CD.
------------------------------
Date: Fri, 01 Apr 2005 17:16:07 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Need syntax/small footprint help
Message-Id: <d2jv9u$grn$1@sun3.bham.ac.uk>
robic0@yahoo.com wrote:
> On Sun, 27 Mar 2005 10:28:12 +0000, Brian McCauley <nobull@mail.com>
> wrote:
>
>
>>
>>robic0@yahoo.com wrote:
>>
>>
>>>Hello, last month I wrote a rather large 10,000 line program that
>>>parses xml (expat). The data is read into compound structures
>>>then analyzed later. Below is one of the subroutines. I would like
>>>to make it smaller so that its easier to read and understand and
>>>also make the regular expressions less complicated for performance.
>>>Any ideas?
>>>
>>>---------------------------
>>>sub eCHK_RegDel ## -- checks Redundant Regkey Delete // Regkey
>>>exists --
>>>{
>>> my ($details) = @_;
>>> return 1 if (@{$details} == 0);
>>
>> return 1 unless @$details;
>
> yes, the same
>
>>But actually this is, I think, redundant. There is no point since if
>>@$details is empty so will @regdel so nothing will happen anyhow.
>>
>
> return from @details empty check comes b4 @regdel population?
You think it is relevant why? It is always better to write code with
fewer cases handled as exceptional.
>>> if (@regdel)
>>> {
>>
>>Again this is redundant. "If the next line would do nothing then don't
>>do it". But if the next line would do nothing there's no cost in doing
>>it anyhow.
>
>
> It may look weird but I assure you its the same push return addr onto
> the stack register without a goto.
I have no idea what you just said.
> also, its proper form that more code may end up below "if" statement,
> large code dictates you leave the door open.
What you call "leaving the door open" is what makes your code large.
If someone is going to add more code that needs to be outside the loop
but conditional on @regdel being non-empty then the additional effort of
adding the if is trivial.
Remember: always write less code unless this would make your code less
readable.
>>> next if (exists ($aref->[4]{$KEYNAME}) &&
>>>length($aref->[4]{$KEYNAME}) > 0);
>>
>>You mean defined() not exists().
>>
>>length() can never be negative so >0 is redundant.
>>
>
> Not true...
Why?
> $aref->[4]{$KEYNAME} is dynamic. it MUST exist
> and if it does is sometimes zero length, which is a condition
> that is unacceptable...
That supports my assertion. When disagreeing with someone it is
convetional to put forward reasons why they are wrong, not why they are
right.
>
>>> my @regx_esc_codes = ( "\\", '/', '(', ')', '[', ']', '?', '|',
>>> '+', '.', '*', '$', '^', '{',
>>>'}', '@' );
>>
>>This is invarient and should be taken outside the loop or maybe even
>>outside the subroutine. But you don't need it at all probably.
>
>
> Not true... it is not inside a loop.
Sorry my mistake.
> global scope had no use for
> it.... in general, scoping in Perl is just like C++, dump it as soon
> as possible !!
Yes in general, yes. There are however exceptions. Constants are one.
>>> for (@regdel)
>>> {
>>> my $aref = $_;
>>> next if (!(exists ($aref->[4]{$KEYNAME}) &&
>>>length($aref->[4]{$KEYNAME}) > 0));
>>
>>Why the second loop? Why not a do it in a single pass?
>>
>
> for alot of reasons... one is the side affects of trying to do such
> a complicated maneuver all at once... generally a good
> precautionarry measure especially since the first does not
> slow down the second at all, since the @regdel array of
> structures has been pre-conditioned via a sort engine
> that maximizes this kind of check ahead of time.
> Pre-fetching like this occurs sometimes 6 levels deep
> before analysis begins. Its a trade-off where clarity wins
> vs. bug introduction, but the engines must be designed
> for this type of thing ahead of time... which were.
I have no idea what you just said. I think you are saying that if an
error is detected in thre first loop then the second loop is not
executed. That's simply not true.
>> $kname =~ s/(\Q$tc\E)/\\$1/g;
>
> I don't know what this is... I guess I should check it.
> If you can resolve ALL the "$tc" with the "\Q"
> in regx then this should work... have you tried this method yourself?
Yes I have used quotemeta (or \Q) in Perl a lot.
> Without eval on the @regx codes you can't esc an "odd" number
> of '\' without muting the '$' in "$tc". I hope it works I will try it
> tommorow. @regx is array of single chars, this won't work on
> expressions as are the eval in the dynamic strings compared later.
I have no idea what you just said there. You seem to be saying you
think eval() is somehow the solution to some problem you were having.
As far as I can see all the problems you mention are a _consequence_ of
your decision to use eval().
Most of your code seems devoted to checking if string $kname starts with
string $first_kname. In most languages there's an easy way to do this.
Surely the fact that you spent a couple of dozen lines on it should
have rung alarm bells.
In Perl this is simply:
$kname =~ /^\Q$first_kname/
...or...
!index($kname,$first_kname)
To make it case insensative you can simply put a /i on the refeg or
convert everything to lowercase.
> Course thats why its done here right....
I have no idea what you are talking about. What are you suggesting you
have done right?
>>But I suspect you simply wanted
>>
>> $kname = quotemeta $kname;
>>
>>But I'm guessing you wouldn't need to do anything if you got rid of some
>>more of the pointless eval()s in your code.
>>
>>All in all I think you are working way too. Hard. I'll stop now with
>>the line-by-line and go have another look at your code in its entirity.
>> Get back to you soon.
>
>
> You know, I'm being paid far too much money for it too .... hehe!!!
So that's why you'll spend ten units of effort working around a bug you
could fix in one unit.
------------------------------
Date: Fri, 01 Apr 2005 10:09:23 -0700
From: Jeremy Slade <jeremy.slade@intel.com>
Subject: perl hangs after receiving signal
Message-Id: <d2jv83$23b$1@news01.intel.com>
I have a script running in perl 5.6.1 on a debian sarge system (kernel
2.6.8).
On occasion, the perl interpreter just hangs. I have been able to
attach to the process with gdb to get a stack trace, and unfortunately
it is not always the same. But there does seem to be some consistency.
The last frame of the stack is always pthread_setcanceltype() from
libc.so.6. Farther down the stack there is almost always
Perl_signalhandler. Here's an example stack trace:
#0 0x4014b7a1 in pthread_setcanceltype () from /lib/tls/libc.so.6
#1 0x4019a940 in __after_morecore_hook () from /lib/tls/libc.so.6
#2 0x40199fcc in ?? () from /lib/tls/libc.so.6
#3 0x00000011 in ?? ()
#4 0x400d9d53 in posix_memalign () from /lib/tls/libc.so.6
#5 0x40300010 in ?? ()
#6 0x40300490 in ?? ()
#7 0x0847f15c in ?? ()
#8 0x0847f15c in ?? ()
#9 0x0849fe00 in ?? ()
#10 0x080a4ac8 in Perl_sv_clear ()
#11 0x080a4f0b in Perl_sv_free ()
#12 0x080aef69 in Perl_pp_vec ()
#13 0x08098f98 in Perl_runops_standard ()
#14 0x0805cbca in perl_call_sv ()
#15 0x0805cb0a in perl_call_sv ()
#16 0x08095247 in Perl_sighandler ()
#17 <signal handler called>
#18 0x400d62a8 in free () from /lib/tls/libc.so.6
#19 0x4019a940 in __after_morecore_hook () from /lib/tls/libc.so.6
#20 0x084e39e8 in ?? ()
#21 0x0870fc10 in ?? ()
#22 0x0870fc10 in ?? ()
#23 0xbffffb70 in ?? ()
#24 0x08097b43 in Perl_av_undef ()
#25 0x080a4b0f in Perl_sv_clear ()
#26 0x080a4f0b in Perl_sv_free ()
#27 0x0807ff75 in Perl_cv_undef ()
#28 0x080a4b4c in Perl_sv_clear ()
#29 0x080a4f0b in Perl_sv_free ()
#30 0x080b680a in Perl_free_tmps ()
#31 0x080994b1 in Perl_pp_unstack ()
#32 0x08098f98 in Perl_runops_standard ()
#33 0x0805c2df in perl_run ()
#34 0x0805c15a in perl_run ()
#35 0x08059c3a in main ()
I have tried the same script on debian stable systems (same perl 5.6.1
binary, however), and it seems to work much better, I don't ever see
this problem.
Since this call to pthread_setcanceltype happens way down inside other
function calls, I suspect this is not at all a perl problem, but rather
a linux or libc problem. But I am hoping that someone can offer some
help in determining why this hangs and what I might be able to do about it.
Thanks,
Jeremy
------------------------------
Date: 1 Apr 2005 19:04:58 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: perl hangs after receiving signal
Message-Id: <d2k60q$5hr$1@mamenchi.zrz.TU-Berlin.DE>
Jeremy Slade <jeremy.slade@intel.com> wrote in comp.lang.perl.misc:
> I have a script running in perl 5.6.1 on a debian sarge system (kernel
^^^^^
> 2.6.8).
Perl signal handling was unsafe before 5.8.0. In particular, if a program
was interrupted during a memory allocation, and the signal handler started
off another memory allocation (can easily happen in inconspicuous code),
that usually meant a segfault.
> On occasion, the perl interpreter just hangs. I have been able to
I don't know why it hangs, but when you re-enter non-re-entrant code
basically anything can happen.
> Perl_signalhandler. Here's an example stack trace:
[stack trace much shortened, missing parts indicated]
...
> #4 0x400d9d53 in posix_memalign () from /lib/tls/libc.so.6
...
> #16 0x08095247 in Perl_sighandler ()
> #17 <signal handler called>
> #18 0x400d62a8 in free () from /lib/tls/libc.so.6
...
The signal arrives during free(), a memory (de-)allocation. The memory
heap may be inconsistent. In the signal handler, something called
posix_memalign() is called. I don't know what it is, but it sounds much
like something that might be sensitive to an inconsistent heap. That
seems to match the theory pretty well.
Anno
------------------------------
Date: Fri, 01 Apr 2005 17:55:00 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Perl script hangs
Message-Id: <d2k1ip$hrb$1@sun3.bham.ac.uk>
Anno Siegel wrote:
> Kurt <kurt.semba@gmx.de> wrote in comp.lang.perl.misc:
>
>
>>I had a while loop with a counter like this:
>>
>>counter = 0;
>>while ($array[$counter])
>> {
>> ...
>> if (some_statement)
>> {
>> ...
>> $counter++;
>> }
>> }
>>
>>In this short version of the code it is easy to see what happens if
>>the "some_statement" never evaluates to true --> endless loop. But it
>>was not that obvious to me in the "long" version of the code :)
>
>
> s/never evaluates to true/ever evaluates to false/
Er, no.
"never evaluates to true for a given value of $counter".
So long as some_condition() will eventually become true for any value of
$counter there is no infinite loop.
------------------------------
Date: 1 Apr 2005 18:09:19 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Perl script hangs
Message-Id: <d2k2of$3ht$1@mamenchi.zrz.TU-Berlin.DE>
Brian McCauley <nobull@mail.com> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
> > Kurt <kurt.semba@gmx.de> wrote in comp.lang.perl.misc:
> >
> >
> >>I had a while loop with a counter like this:
> >>
> >>counter = 0;
> >>while ($array[$counter])
> >> {
> >> ...
> >> if (some_statement)
> >> {
> >> ...
> >> $counter++;
> >> }
> >> }
> >>
> >>In this short version of the code it is easy to see what happens if
> >>the "some_statement" never evaluates to true --> endless loop. But it
> >>was not that obvious to me in the "long" version of the code :)
> >
> >
> > s/never evaluates to true/ever evaluates to false/
>
> Er, no.
>
> "never evaluates to true for a given value of $counter".
>
> So long as some_condition() will eventually become true for any value of
> $counter there is no infinite loop.
But $counter won't change anymore once some_statement() evaluates to
false, so it's stuck.
Anno
------------------------------
Date: Fri, 01 Apr 2005 18:26:51 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Perl script hangs
Message-Id: <d2k3ee$irn$1@sun3.bham.ac.uk>
Anno Siegel wrote:
> Brian McCauley <nobull@mail.com> wrote in comp.lang.perl.misc:
>
>>
>>So long as some_condition() will eventually become true for any value of
>>$counter there is no infinite loop.
>
> But $counter won't change anymore once some_statement() evaluates to
> false, so it's stuck.
It's amazing how you can tell just form the name that the result of
some_statement() will not change if $counter does not change.
Me, I'd need to look at the definition of some_statement().
------------------------------
Date: Fri, 01 Apr 2005 13:36:22 -0500
From: Chris Mattern <matternc@comcast.net>
Subject: Re: Perl script hangs
Message-Id: <epKdnStL7dQ7CdDfRVn-2Q@comcast.com>
Anno Siegel wrote:
> Brian McCauley <nobull@mail.com> wrote in comp.lang.perl.misc:
>> Anno Siegel wrote:
>> > Kurt <kurt.semba@gmx.de> wrote in comp.lang.perl.misc:
>> >
>> >
>> >>I had a while loop with a counter like this:
>> >>
>> >>counter = 0;
>> >>while ($array[$counter])
>> >> {
>> >> ...
>> >> if (some_statement)
>> >> {
>> >> ...
>> >> $counter++;
>> >> }
>> >> }
>> >>
>> >>In this short version of the code it is easy to see what happens if
>> >>the "some_statement" never evaluates to true --> endless loop. But it
>> >>was not that obvious to me in the "long" version of the code :)
>> >
>> >
>> > s/never evaluates to true/ever evaluates to false/
>>
>> Er, no.
>>
>> "never evaluates to true for a given value of $counter".
>>
>> So long as some_condition() will eventually become true for any value of
>> $counter there is no infinite loop.
>
> But $counter won't change anymore once some_statement() evaluates to
> false, so it's stuck.
You are assuming that once some_statement() evaluates to false, it
will always evaluate to false on succeeding iterations. I see no
support for such an assumption.
>
> Anno
--
Christopher Mattern
"Which one you figure tracked us?"
"The ugly one, sir."
"...Could you be more specific?"
------------------------------
Date: Fri, 01 Apr 2005 16:21:41 GMT
From: "Lord0" <lawrence.tierney@bipcontracts.com>
Subject: Re: Redirect on the NO pushing button
Message-Id: <pye3e.94$il.58@newsfe5-win.ntli.net>
This dude is loco
------------------------------
Date: 1 Apr 2005 17:05:34 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: slicing syntax question
Message-Id: <d2jv0u$1r2$1@mamenchi.zrz.TU-Berlin.DE>
<xhoster@gmail.com> wrote in comp.lang.perl.misc:
> "AC" <clarke@n_o_s_p_a_m_hyperformix.com> wrote:
[...]
> > my @items = qw(a b c d e);
> > @hash{@items} = 0..$#items;
> > I really want to use fewer lines in my code and I'd hate to use one line
> > to declare the hash and one line to initialize it.
>
> newlines are optional almost everywhere in Perl.
>
> my %hash; @hash{@items}= 0..$#items;
Ah, but that's only cosmetics :)
my %hash = map { $items[ $_] => $_ } 0 .. $#items;
Anno
------------------------------
Date: Fri, 01 Apr 2005 16:15:10 GMT
From: "Lord0" <lawrence.tierney@bipcontracts.com>
Subject: Re: Unable to connect to remote host
Message-Id: <ise3e.90$il.74@newsfe5-win.ntli.net>
"I'm running CGI program (written using perl) with Tomcat.
Cgi program written in perl has a telnet operation. It is trying to
connect to a port on a remote host. When i run the perl script as a
standalone, it works perfectly. when i try to run the same script with
tomcat server i am getting the following error."
I have had a similar problems. i.e. run perl script standalone is fine. Run
under Tomcat broken. I think this could be to do with Tomcats security
settings and how it interacts with the OS, in this case Perl. You maybe want
to post on a java/tomcat group and see what get. BTW if you find an answer
let me know eh? :-)
Lord0
------------------------------
Date: Fri, 01 Apr 2005 17:33:14 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Unable to connect to remote host
Message-Id: <d2k09e$h93$1@sun3.bham.ac.uk>
srithota@gmail.com wrote:
> I'm running CGI program (written using perl) with Tomcat.
> Cgi program written in perl has a telnet operation. It is trying to
> connect to a port on a remote host. When i run the perl script as a
> standalone, it works perfectly. when i try to run the same script with
> tomcat server i am getting the following error.
>
> Mar 31, 2005 9:37:21 PM org.apache.catalina.core.ApplicationContext log
> INFO: cgi: runCGI (stderr):problem creating socket: Unknown error at
> C:/Perl/sit
> e/lib/AOLserver/CtrlPort.pm line 125
>
> ctrlport.pm is the perl module and line 125 in the module is my $t =
> Net::Telnet->new(%options);
I suggest you look for the line that's carp()ing with the message
"problem creating socket" and include $^E alongside $!.
------------------------------
Date: 1 Apr 2005 10:20:58 -0800
From: "sri" <srithota@gmail.com>
Subject: Re: Unable to connect to remote host
Message-Id: <1112379658.576654.22390@g14g2000cwa.googlegroups.com>
Thanks for the response Brian. The error is araising at this line
my $t = Net::Telnet->new(%options);
You want me to add :
$^E my $t = Net::Telnet->new(%options); $!
What does these charcters do... ?
Thank you
Sri
------------------------------
Date: Fri, 01 Apr 2005 18:50:07 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Using a for() statement to create a variable??
Message-Id: <d2k4q1$ji1$1@sun3.bham.ac.uk>
A. Sinan Unur wrote:
[ of "robic0@yahoo.com" ]
> Your ignorance is amusing.
No, I think it has long ceased to be. robic0 is now rapidly[1]
decomming the heir apparent to the thrown of she whose name we shall not
utter.
We are all Frank.
[1] Fredian slip - I initially typed "rabidly".
------------------------------
Date: Fri, 1 Apr 2005 20:18:00 +0300
From: Ilmari Karonen <usenet@vyznev.invalid>
Subject: Re: Using HTTPS with LWP::UserAgent = Bad Service
Message-Id: <slrnd4r0i8.2mc.usenet@boojum.home.vyznev.net>
Richard Lawrence <richard.lawrence@gmail.com> kirjoitti 31.03.2005:
>
> $ perl testproxy.pl 1
> HTTPS_PROXY=http://10.10.200.44:8080/
> HTTPS_PROXY_PASSWORD=mypassword
> HTTPS_PROXY_USERNAME=richard
> HTTP_PROXY=http://10.10.199.45:80/
> Going to get https://www.nodeworks.com
> Using HTTPS proxy http://10.10.200.44:8080/
> Result is:
> 500 (Internal Server Error) Can't connect to www.nodeworks.com:443 (Bad
> service '8080/')
Ah, I think I see what the problem is now.
Try getting rid of the trailing slash after ":8080".
--
Ilmari Karonen
To reply by e-mail, please replace ".invalid" with ".net" in address.
------------------------------
Date: Fri, 01 Apr 2005 11:08:45 -0700
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: using Perl to insert footer into PDF files?
Message-Id: <dp6dncSP5OiqE9DfRVn-1g@comcast.com>
Scott Bryce wrote:
> The PDF spec is fairly complex. This will not be a simple matter of
> inserting page breaks. The entire document will have to be re-built.
My bad. I had this confused with a post on comp.text.pdf. The OP does
not want to add page breaks.
Adding footers might be easier than adding page breaks, but it will
still be a bit complex.
------------------------------
Date: Fri, 01 Apr 2005 17:14:46 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Why doesn't Perl have cp or mv?
Message-Id: <960r41liekeuhmi8342v62g47toaapn0tm@4ax.com>
Andras Malatinszky wrote:
>Why is it that Perl emulates Unix commands like chmod and chown but not
>such basic operations like cp or mv?
On a similar note, I've always wondered why Perl had no curdir, or cwd.
Cwd() exists to solve that problem, but the question still remains.
Currently, I'm more inclinced on moving stuff *out* of perl and into
modules. For example, I see no reason why socket calls couldn't actually
be part of a module, instead of built into perl.
Just blame perl4, because extensible perl (with XS modules) was new for
perl5 -- since around 1995.
--
Bart.
------------------------------
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 7933
***************************************
