[16478] in Perl-Users-Digest
Perl-Users Digest, Issue: 3890 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Aug 2 18:15:41 2000
Date: Wed, 2 Aug 2000 15:15:28 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <965254528-v9-i3890@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Wed, 2 Aug 2000 Volume: 9 Number: 3890
Today's topics:
Re: Removing newline chars <lr@hpl.hp.com>
Re: Removing newline chars <godzilla@stomp.stomp.tokyo>
Re: Removing newline chars <godzilla@stomp.stomp.tokyo>
Re: Removing newline chars <care227@attglobal.net>
Re: Removing newline chars <godzilla@stomp.stomp.tokyo>
Re: Removing newline chars <care227@attglobal.net>
Re: Removing newline chars (Logan Shaw)
Re: Removing newline chars <godzilla@stomp.stomp.tokyo>
Re: Removing newline chars <lr@hpl.hp.com>
Re: Removing newline chars <care227@attglobal.net>
Re: Removing newline chars (Logan Shaw)
Re: Script Failure. Need Some Advice Please... <care227@attglobal.net>
Re: Script Failure. Need Some Advice Please... (Cyber Thief)
Re: Script Failure. Need Some Advice Please... <care227@attglobal.net>
Re: Script Failure. Need Some Advice Please... (Cyber Thief)
Re: splitting on spaces (Abigail)
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 2 Aug 2000 11:05:09 -0700
From: Larry Rosler <lr@hpl.hp.com>
Subject: Re: Removing newline chars
Message-Id: <MPG.13f202b24467b6a698ac28@nntp.hpl.hp.com>
In article <39884557.DD779FB9@stomp.stomp.tokyo> on Wed, 02 Aug 2000
08:59:19 -0700, Godzilla! <godzilla@stomp.stomp.tokyo> says...
> Larry Rosler wrote:
>
> > Godzilla! wrote:
...
> Learning experiences are usually good but not always
> enjoyable. I will share another learning experience
> via an article you will not read. I have cancelled
> this article. I tested your code, but neglected to
> remember to include the /s switch. Of course, doubled
> up spaces appeared. I made an assumption you had
> posted untested code again and, in response, chastised
> you for your habit of not testing before posting.
I have many bad habits. But posting untested code without saying so
explicitly isn't among them.
> Nevertheless, a result of my personal rule of testing
> before utterance, after testing your code, with having
> forgotten to include the /s switch, my tests confirmed a
> mindless mistake, this result caused me to think,
>
> "This is not in keeping with Mr. Rosler's expertise."
>
> With this thought foremost in my mind, I went over all
> givens again and again, until I noted my /s mistake but
> not until after I had posted my erroneous article.
Most programming environments support 'copy-and-paste', which obviates
most such recopying errors.
> Lesson here is not really in how easy it is to overlook
> a small detail, become blind to it until you force yourself
> to see, in my case by reading givens backwards, the real
> lesson here is in being objective, fair and ethically
> responsible in dealing with a person, even if you hold
> an opinion he is braying jackass.
Hee-haw!
> True lesson here is a difference between women and men,
> in general. We women have healthy egos allowing us point
> out our mistakes, even when we have no need to do so. Most
> men are incapable of this notion and defer to braying.
Hee-haw!
> I made a mistake you most likely would have never known
> about without my openingly discussing this mistake of mine.
Very open and forthcoming. Much appreciated.
Someone else snidely presumed that your medication was kicking in. I
think it is simply good sense, perhaps induced by a developing trust in
what happens here.
> I question if your code is an order of magnitude faster.
Modern Perl 5 has a tool to test such conjectures. Here is an example:
#!/usr/local/bin/perl -w
use strict;
use Benchmark;
use vars '$s';
$s = '
This is
a string
with
an
arbitrary
number
of
newlines
here
and
there
' x 100;
timethese( 1 << (shift || 0), {
Cntrl => '(my $x = $s)',
Regex => '(my $x = $s) =~ s/[\r\n]+/ /g',
Tr => '(my $x = $s) =~ tr/\r\n/ /s',
} );
__END__
Output:
Benchmark: timing 16384 iterations of Cntrl, Regex, Tr...
Cntrl: 1 wallclock secs ( 0.55 usr + 0.00 sys = 0.55 CPU) @
29952.47/s (n=16384)
Regex: 58 wallclock secs (57.64 usr + 0.00 sys = 57.64 CPU) @
284.25/s (n=16384)
Tr: 8 wallclock secs ( 9.59 usr + 0.00 sys = 9.59 CPU) @
1707.91/s (n=16384)
(57.64 - 0.55) / (9.59 - 0.55) = 6.32
Near enough to 'an order of magnitude', by my reckoning. YMMV.
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Wed, 02 Aug 2000 11:24:00 -0700
From: "Godzilla!" <godzilla@stomp.stomp.tokyo>
Subject: Re: Removing newline chars
Message-Id: <39886740.9D80F4FB@stomp.stomp.tokyo>
Uri Guttman brayed:
> > Godzilla! wrote:
> > > Larry Rosler wrote:
(snipped)
> Sheeee haaw... Sheeee haw.. haw.. haw...
* laughs *
Godzilla!
--
I am a belly dancer. I will rock you like a flute charmed cobra.
http://la.znet.com/~callgirl3/belly-10.mid
------------------------------
Date: Wed, 02 Aug 2000 11:40:05 -0700
From: "Godzilla!" <godzilla@stomp.stomp.tokyo>
Subject: Re: Removing newline chars
Message-Id: <39886B05.728D2F99@stomp.stomp.tokyo>
Larry Rosler wrote:
> Godzilla! wrote:
> > Larry Rosler wrote:
> > > Godzilla! makes a backhanded apology:
(snipped my backhanded apology)
> > Lesson here is not really in how easy it is to overlook
> > a small detail, become blind to it until you force yourself
> > to see, in my case by reading givens backwards, the real
> > lesson here is in being objective, fair and ethically
> > responsible in dealing with a person, even if you hold
> > an opinion he is braying jackass.
> Hee-haw!
Thats "Gee!" and "Haw!" which translated into
mule braying is "turn left" and "turn right".
Seriously. We trained our mules, as many farmers,
to respond to Gee! and Haw! at row's end. For
trivia, depending how many hands high of a mule,
Gee! and Haw! are critical because a mule cannot
turn on dime like my Corvette Mako Shark, not that
it is my customary habit to tow a stepin-harness plow
behind my Corvette. When plowing, you have to skip
every second or third row, depending on the size of
the mule's ass you are following. At field's end,
you iterate (heh!) back through your field to catch
unplowed rows.
> Hee-haw!
See instructions above.
> > I question if your code is an order of magnitude faster.
> Modern Perl 5 has a tool to test such conjectures. Here is an example:
> Benchmark: timing 16384 iterations of Cntrl, Regex, Tr...
> Cntrl: 1 wallclock secs ( 0.55 usr + 0.00 sys = 0.55 CPU) @
> 29952.47/s (n=16384)
> Regex: 58 wallclock secs (57.64 usr + 0.00 sys = 57.64 CPU) @
> 284.25/s (n=16384)
> Tr: 8 wallclock secs ( 9.59 usr + 0.00 sys = 9.59 CPU) @
> 1707.91/s (n=16384)
>
> (57.64 - 0.55) / (9.59 - 0.55) = 6.32
> Near enough to 'an order of magnitude', by my reckoning. YMMV.
Bet I can plow a rabbit holed back forty faster than you.
Godzilla!
A mule's story.
http://la.znet.com/~callgirl/cybefarm.html
------------------------------
Date: Wed, 02 Aug 2000 14:46:22 -0400
From: Drew Simonis <care227@attglobal.net>
Subject: Re: Removing newline chars
Message-Id: <39886C7E.828CADD5@attglobal.net>
"Godzilla!" wrote:
>
> Nevertheless, a result of my personal rule of testing
> before utterance
And, in: <398847A0.CB256331@stomp.stomp.tokyo>, "Godzilla!" wrote:
> Very nice! I haven't tested your code yet but have no
> reason to doubt it works well.
Can you explain your contradictory remarks?
------------------------------
Date: Wed, 02 Aug 2000 12:12:56 -0700
From: "Godzilla!" <godzilla@stomp.stomp.tokyo>
Subject: Re: Removing newline chars
Message-Id: <398872B8.640E09A6@stomp.stomp.tokyo>
Drew Simonis wrote:
> "Godzilla!" wrote:
> > Nevertheless, a result of my personal rule of testing
> > before utterance
> And, in: <398847A0.CB256331@stomp.stomp.tokyo>, "Godzilla!" wrote:
> > Very nice! I haven't tested your code yet but have no
> > reason to doubt it works well.
> Can you explain your contradictory remarks?
Yes, this contradiction is often thought of
as being polite and courteous, notions, both
of which, you are sorely unaware.
Perhaps some sweet oats in your feed bag
will take this sore note edge off your
cranky mule braying.
"Illiteracy is an American Shakesperian tragedy."
- Kira
Godzilla!
My bottom is big, fat and makes this rocking world go round.
http://la.znet.com/~callgirl5/bottom.mid
------------------------------
Date: Wed, 02 Aug 2000 15:57:43 -0400
From: Drew Simonis <care227@attglobal.net>
Subject: Re: Removing newline chars
Message-Id: <39887D37.325F8180@attglobal.net>
"Godzilla!" wrote:
>
> Drew Simonis wrote:
>
> > "Godzilla!" wrote:
>
> > > Nevertheless, a result of my personal rule of testing
> > > before utterance
>
> > And, in: <398847A0.CB256331@stomp.stomp.tokyo>, "Godzilla!" wrote:
>
> > > Very nice! I haven't tested your code yet but have no
> > > reason to doubt it works well.
>
> > Can you explain your contradictory remarks?
>
> Yes, this contradiction is often thought of
> as being polite and courteous, notions, both
> of which, you are sorely unaware.
>
Shouldn't that sentence be:
Yes, this contradiction is often thought of as being polite and
courteous. Both notions of which you are sorely unaware.
And anyway, contridicting yourself does not make you more
polite than I. What it does is make you look confused.
------------------------------
Date: 2 Aug 2000 15:45:52 -0500
From: logan@cs.utexas.edu (Logan Shaw)
Subject: Re: Removing newline chars
Message-Id: <8ma1a0$elc$1@provolone.cs.utexas.edu>
In article <MPG.13f164cdfc1b8fe198ac23@nntp.hpl.hp.com>,
Larry Rosler <lr@hpl.hp.com> wrote:
>In article <39876FA4.28055EDD@stomp.stomp.tokyo>,
>godzilla@stomp.stomp.tokyo says...
>> Your code, =~ s/[\r\n]+/ /g; would seem best choice
>
>Excellent. Here's another good learning experience, assuming an order-
>of-magnitude performance improvement matters in the particular
>application:
>
> tr/\r\n/ /s
I wasn't sure about this order-of-magnitude thing. Regular expressions
are slow, but it's only the parsing and the building of state machine
that's slow, not the running of the stuff through the state machine.
(An exception is when backtracking is involved -- that's really slow.)
So anyway, I decided to test it out and see how much slower the regular
expression was is than the straight tr way. I ran a script that does
each one on a string which is my /etc/termcap repeating 50 times.
The first thing to note is that it actually takes a significant
amount of time for this:
$tc1 = $tc2 = $termcap x 50;
to run. Anyway, this:
$tc1 =~ tr/\r\n/ /s;
takes 0.79 seconds, while this:
$tc2 =~ s/[\r\n]+/ /g;
takes 2.71 seconds. So, it's a factor of about 3.4, which is a little
larger than the square root of ten.
In other words, it's just over half an order-of-magnitude slower. :-)
- Logan
------------------------------
Date: Wed, 02 Aug 2000 13:46:15 -0700
From: "Godzilla!" <godzilla@stomp.stomp.tokyo>
Subject: Re: Removing newline chars
Message-Id: <39888897.4DECFE45@stomp.stomp.tokyo>
Drew Simonis attempted to write:
> "Godzilla!" wrote:
> > Drew Simonis scrawled:
> > > "Godzilla!" wrote:
> Shouldn't that sentence be:
(red lined)
My belief is you have selected a wrong person
to engage in debate pertaining to writing
techniques and writing styles employing our
English language.
Would you like to try my Native Tongue, Choctaw?
Chahta imanumpa ish anumpola hinla ho?
Chahta iskitini anumpuli li!
* giggles *
Dr. Kiralynne Schilitubi
Professor of English; Creative Writing
University of California at Riverside
English and Science Educator, Retired
Riverside Unified School District
--
print "DUH!";
exit;
------------------------------
Date: Wed, 2 Aug 2000 14:09:34 -0700
From: Larry Rosler <lr@hpl.hp.com>
Subject: Re: Removing newline chars
Message-Id: <MPG.13f22de5266403fa98ac2b@nntp.hpl.hp.com>
In article <8ma1a0$elc$1@provolone.cs.utexas.edu> on 2 Aug 2000 15:45:52
-0500, Logan Shaw <logan@cs.utexas.edu> says...
...
> The first thing to note is that it actually takes a significant
> amount of time for this:
>
> $tc1 = $tc2 = $termcap x 50;
>
> to run.
What is 'a significant amount of time'? Is it, for example, 0.4
seconds? See below.
> Anyway, this:
>
> $tc1 =~ tr/\r\n/ /s;
>
> takes 0.79 seconds, while this:
>
> $tc2 =~ s/[\r\n]+/ /g;
>
> takes 2.71 seconds. So, it's a factor of about 3.4, which is a little
> larger than the square root of ten.
>
> In other words, it's just over half an order-of-magnitude slower. :-)
You don't show your code, nor how you measure the time, nor how many
lines and characters are in your data string. So it's impossible to
test this on another processor.
But if your times include the initialization, say 0.4 sec, then the real
ratio of the operation speeds is 5.9, similar to what I posted before.
BTW: Don't fall into the common benchmarking trap of doing that
operation in a loop without reinitializing the variable each time.
Otherwise you will be doing slow no-ops after the first iteration.
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Wed, 02 Aug 2000 17:13:51 -0400
From: Drew Simonis <care227@attglobal.net>
Subject: Re: Removing newline chars
Message-Id: <39888F0F.9DD78A09@attglobal.net>
"Godzilla!" wrote:
>
>
> Dr. Kiralynne Schilitubi
> Professor of English; Creative Writing
> University of California at Riverside
> English and Science Educator, Retired
> Riverside Unified School District
>
I wouldn't be proud to be a member of an educational system
that has such horrible results. But...
:Yes, this contradiction is often thought of
:as being polite and courteous, notions, both
: ^
:of which, you are sorely unaware.
That comma is misplaced.
------------------------------
Date: 2 Aug 2000 16:47:06 -0500
From: logan@cs.utexas.edu (Logan Shaw)
Subject: Re: Removing newline chars
Message-Id: <8ma4sq$esd$1@provolone.cs.utexas.edu>
In article <MPG.13f22de5266403fa98ac2b@nntp.hpl.hp.com>,
Larry Rosler <lr@hpl.hp.com> wrote:
>In article <8ma1a0$elc$1@provolone.cs.utexas.edu> on 2 Aug 2000 15:45:52
>-0500, Logan Shaw <logan@cs.utexas.edu> says...
>> it actually takes a significant amount of time for this:
>>
>> $tc1 = $tc2 = $termcap x 50;
>>
>> to run.
>
>What is 'a significant amount of time'?
1.32 seconds.
>> $tc1 =~ tr/\r\n/ /s;
>>
>> takes 0.79 seconds, while this:
>>
>> $tc2 =~ s/[\r\n]+/ /g;
>>
>> takes 2.71 seconds.
>
>You don't show your code, nor how you measure the time, nor how many
>lines and characters are in your data string.
Presumably, most versions of /etc/termcap are pretty similar. Nevertheless:
$ wc -lc /etc/termcap
14679 627979 /etc/termcap
$
The method I used to time it was to write a perl script that does a
print() before and after each thing I wanted to time. Then, I ran
"strace" (Linux's system call tracer) on the process as it ran and
watch the timestamps of the system that print() triggered. I put a
unique string in each one so it was easy to tell them apart.
>But if your times include the initialization, say 0.4 sec, then the real
>ratio of the operation speeds is 5.9, similar to what I posted before.
The times don't include the initialization. However, they do include
one call to print().
>BTW: Don't fall into the common benchmarking trap of doing that
>operation in a loop without reinitializing the variable each time.
That's why I had two separate variables ($tc1 and $tc2), each of which
was set to a really long string (31398950 bytes) in advance of the
timing of the tr/// and the s///.
- Logan
------------------------------
Date: Wed, 02 Aug 2000 14:30:22 -0400
From: Drew Simonis <care227@attglobal.net>
Subject: Re: Script Failure. Need Some Advice Please...
Message-Id: <398868BE.9122EFF0@attglobal.net>
Cyber Thief wrote:
>
> Hey, sorry to bother you guys, but I need some assistance from the experts.
> I've been having problems with people leeching files on my site (copying links
> to actual files instead of downloading and uploading them to their own
> webspace). I really loathe this practice, and would pretty much go to the ends
> of the Earth to put a stop to it. A couple years ago, some guy wrote a script
> for me that should accomplish that purpose. Unfortunately, I can't get it
> working, and I'm pretty sure the problem relates to the script, more than the
> server. Anyway, this is the error message I'm receiving...
>
> "It looks like there was an error: Your script produced this error: (Maybe you
> didn't strip carriage returns after a network transfer?)"
Where is this message appearing, and what are you doing to generate it?
This certainly isn't a Perl error, so your author has obviously written
their own traps. Without more information, I doubt anyone will be able
to
assist you much.
------------------------------
Date: Wed, 02 Aug 2000 19:42:11 GMT
From: fake@address.com (Cyber Thief)
Subject: Re: Script Failure. Need Some Advice Please...
Message-Id: <nQ_h5.19032$RG6.1561065@bgtnsc05-news.ops.worldnet.att.net>
In article <398868BE.9122EFF0@attglobal.net>, care227@attglobal.net
says...
>
>Where is this message appearing, and what are you doing to generate
>it? This certainly isn't a Perl error, so your author has obviously
>written their own traps. Without more information, I doubt anyone
>will be able to assist you much.
Ok, the script requires I set up the links on my page like this:
<a
href="http://www.whatever.com/cgi-bin/stoopleech_100.pl?textfile.txt">
Click here to download the file</a>
So I set that up accordingly on my script. My Perl scripts are located
on Tripod in the cgi-bin directory. My page is on InternetTrash. When I
click the link I just created, the program is run on Tripod and I get
the error described in my original post. Anyway, here is the script
itself:
---------------------------------
# author : Arthur Dardia
# descrip : Stop-Leech - a program to stop file leeching
# version : 1.00
# date : 10/20/98
# vrsn. hist. : 0.50 - intial release
# : \_ let's hope it works.
# : 1.00 - new features
# : \_ added support for multiple allowed URLs
# : \_ planning to add support for multiple file
servers in next release
# : \_ to be specified by:
stopleech_xxx.pl?server=3&file=a.zip
# : \_ will redirect to a.zip on the 3rd file
server
require "cgi-lib.pl";
#################################################################
# Define Subs
sub wrong_ref {
print "<title>Ooops!</title>\n";
print "</head><body>\n";
print "<h1>Reference Mismatch</h1>Referring URL
<i>$ENV{HTTP_REFERER}</i> does not match allowed
URL(s).<P></body></html>";
exit(0);
}
sub config_err {
print "<title>Ooops!</title>\n";
print "</head><body>\n";
print "<h1>Configuration Error</h1>Bad or missing config
file.<P></body></html>";
exit(0);
}
# Done
#################################################################
#################################################################
# Define Variables
# the base url of your files
$base_files="http://ct109b.tripod.com/incoming/";
# the name of your config files
$allow_file="allowed.cfg";
# for determining whether or not a matching url has been found
$allowable_url=0;
# for signifying the end of a config file
$end="end";
# Done
#################################################################
&ReadParse; # get the values of
variable
open ALLOW, "<$allow_file" or &config_err; # open config file
$base=<ALLOW>; # get first url to
test
chomp $base; # remove \n from the
url
print "Content-type: text/html\n\n"; # html header
print `<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">`;
print "\n<html><head>\n";
while (allowable_url==0) {
if ($ENV{HTTP_REFERER} =~ /^$base/) { # check if ref
starts with a correct one
$allowable_url=1; # so we exit the
while loop.
print "<title></title>\n";
print "</head><body>\n";
print "Location: $base_files$in{file}\n\n";# send to file
stopleech.pl?file=x
print "</body></html>";
close(ALLOW);
exit(0); # sent to file,
so end
} else { # referring url
does not start with $base
$base=<ALLOW>; # try the next
url in config file
chomp $base;
if ($base =~ /^$end/) {
&wrong_ref;
}
}
}
close(ALLOW);
Cyber Thief
http://internettrash.com/users/cyberthief/
http://wwp.mirabilis.com/83606927
cyberthief@deathsdoor.nospam.com (Remove the .nospam to reply)
1-800-226-0007 Box 233 (After Hours)
------------------------------
Date: Wed, 02 Aug 2000 15:52:20 -0400
From: Drew Simonis <care227@attglobal.net>
Subject: Re: Script Failure. Need Some Advice Please...
Message-Id: <39887BF4.CD39D38B@attglobal.net>
Cyber Thief wrote:
>
> "It looks like there was an error: Your script produced this error: (Maybe you
> didn't strip carriage returns after a network transfer?)"
>
Did you upload this as binary?
------------------------------
Date: Wed, 02 Aug 2000 21:02:26 GMT
From: fake@address.com (Cyber Thief)
Subject: Re: Script Failure. Need Some Advice Please...
Message-Id: <C%%h5.9188$ZL5.570828@bgtnsc07-news.ops.worldnet.att.net>
Hey, I just realized I had been making a stupid mistake. WS FTP (the utility I
use for most of my uploads) sends all files in binary by default. After setting
it to ASCII, I re-uploaded the script and everything appears to be working as
intended. Thanks.
--
Cyber Thief
http://internettrash.com/users/cyberthief/
http://wwp.mirabilis.com/83606927
cyberthief@deathsdoor.nospam.com (Remove the .nospam to reply)
1-800-226-0007 Box 233 (After Hours)
------------------------------
Date: 02 Aug 2000 20:54:58 GMT
From: abigail@foad.org (Abigail)
Subject: Re: splitting on spaces
Message-Id: <slrn8oh2kg.6n1.abigail@alexandra.foad.org>
Bob Dilworth (bdilworth@mco.edu) wrote on MMDXXVIII September MCMXCIII in
<URL:news:39883b30.9949539@news.mco.edu>:
[]
[] So ... there's not a simple explanation that your yourself could have
[] provided? Such knowledge must be "earned" as part of some sort of
[] initiation ritual?
Yes, it's called "lurk for a while". It's the same thing when arriving at
a party in progress, full of people unknown to you. You wouldn't start
tapdancing on a table with your pants down just because your beerbuddies
never complain about that. You would first try to find out whether that's
appropriate behaviour.
[] Where such pressure come from? It takes less time to be mean than it
[] does to be nice? Jeesh.
[]
[] How'd I do with this posting? Does it pass the necessary muster?
You blew it with the previous paragraph.
Abigail
--
perl -Mstrict -we '$_ = "goto Z.print chop;\n=rekcaH lreP rehtona tsuJ";Z1:eval'
------------------------------
Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 16 Sep 99)
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: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.
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 V9 Issue 3890
**************************************
