[27264] in Perl-Users-Digest
Perl-Users Digest, Issue: 9027 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 7 18:05:57 2006
Date: Tue, 7 Mar 2006 15:05:10 -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 Tue, 7 Mar 2006 Volume: 10 Number: 9027
Today's topics:
Re: A Problem With GD <matthew.garrish@sympatico.ca>
Re: A Problem With GD <markem@airmail.net>
Re: A Problem With GD <jgibson@mail.arc.nasa.gov>
Re: Force numeric variable ! <tadmc@augustmail.com>
Re: Force numeric variable ! <rm@biteme.org>
Re: Posting Guidelines for comp.lang.perl.misc ($Revisi <rm@biteme.org>
Re: Regex: Backreferences do not work inside quantifier <1usa@llenroc.ude.invalid>
Re: Regex: Backreferences do not work inside quantifier <matthew.garrish@sympatico.ca>
Re: Regex: Backreferences do not work inside quantifier <matthew.garrish@sympatico.ca>
Re: Regex: Backreferences do not work inside quantifier <tadmc@augustmail.com>
Re: Regex: Backreferences do not work inside quantifier <usenet@nana.franken.de>
Re: Regex: Backreferences do not work inside quantifier <1usa@llenroc.ude.invalid>
Re: Regex: Backreferences do not work inside quantifier <nospam-abuse@ilyaz.org>
Re: Regex: Backreferences do not work inside quantifier <usenet@nana.franken.de>
Re: Standing in line (was Re: Posting Guidelines for co <rm@biteme.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 7 Mar 2006 14:00:32 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: A Problem With GD
Message-Id: <gLkPf.625$xM2.67593@news20.bellglobal.com>
"Mark Manning" <markem@airmail.net> wrote in message
news:120rl20pn8a9p40@corp.supernews.com...
>
>
> Matt Garrish wrote:
>
>> So we know you're at least ten. Somehow that seems about right for the
>> stunted vocabulary and make-pretend conversations...
>>
>
> Oh my. Aren't we the smart one? Could you provide one of the
> "make-pretend conversations" and maybe an example of a "stunted
> vocabulary"? Or do you just like to throw out words and hope they mean
> something?
>
Oh please, you're still a half-wit, as evidenced throughout this thread. I
mistook this post for the new troll, that's all.
Matt
------------------------------
Date: Tue, 07 Mar 2006 13:36:42 -0600
From: Mark Manning <markem@airmail.net>
Subject: Re: A Problem With GD
Message-Id: <120ro43gi4qt5b7@corp.supernews.com>
A. Sinan Unur wrote:
>>Since it is you and I talking here - you should be able to know what
>>the "it" is. Others, if they want to know what "it" is should read
>>the previous posts. Therefore, the "it" is unnecessary.
>
>
> Quoting properly is necessary.
You do not quote the entire dictionary just because you want to reference it.
>>The only thing that needed to be posted was:
>>
>> $rgb = (r<<16)|(g<<8)|b;
>>
>> should replace all of the colorAllocations.
>
>
> So, you are telling everyone that the whole GD::Image interface is
> wrong. Talk about arrogance. How about the thousands of people who are
> able to write correct code?
Ok, excuse me here - but what leap of faith did you make? Up until this point
no one has said anything about "the whole GD::Image interface is wrong."
Suddenly, because I have said I may have found a problem the whole thing is no
longer useful? Talk about over the top. And your next sentence you should say
to yourself while looking into a mirror. Last, but not least is the question of
"What constitutes CORRECT code?" Just because you like to write something one
way does not mean that is the only correct way to do it. Is
for( $i=0; $i<10; $i++ )...
any better than
$i=-1;
while( $i++ < 10 )...
any worse? Which is correct? I believe that Larry Wall put it best once when
he said that there is no one way to write a Perl program. Maybe you should
follow his lead.
>>That's right! So if you DON'T want to VOLUNTEER to help out - then
>>DON'T! But DON'T try to make others conform to YOUR way of doing
>>things! That's like going over to Louisiana, bringing food and water
>>to those people who need it - and then telling them they have to pay
>>you for your services! And your excuse would be "HEY! I'M JUST A
>>VOLUNTEER! YOU HAVE TO DO WHAT I SAY!" What a load of bunk!
>
>
> Let's see: So, I am handing out food and blankets after a natural
> disaster (although I am not presumptuous enough to think that the help
> we provide here is *that* important).
>
> While I am handing out stuff, I see a strong person push away the meek
> to get to the front of the line. According to you, I am supposed to say
> "here, take as much as you want".
Ah. Another lapse in logic. If you want to look at c.l.p.misc as a line - then
no one has a choice but to wait in line since the computer forces you to be put
in in a certain order. Therefore, there can not be (logically) someone FORCING
their way to the front of the line. YOU, if you so choose, can jump to
whereever you want in the line while READING the messages - but >I< can not
FORCE YOU to read my message. Therefore, saying that >I< have forced my way to
the head of the line is illogical and without merit.
>
> In fact, take a look at how the Red Cross operates: You have to do as
> they say to get the help. You cannot go to a shelter, and start a fight.
> You cannot cut to the front of the line.
More illogical nonsense. First, the Red Cross will only help if you ask them to
help. They do not force themselves on to anyone. They offer their services,
but if the country, province, state, parish, city, or even individual refuses
their help they do not usually force themselves onto the other party. So your
demented "You have to do as they say" is incorrect - but be my guess and please
go tell them that they are forcing themselves off on to others.
Now as for the "You cannot go to a shelter..." thing. This is incorrect as
well. You CAN go to a shelter and start a fight just like you started one here
with me. The reaction you might get would be, as in this case, well deserved.
>
> Volunteers are people who provide help to other people for the
> satisfaction they feel afterwards of helping people whom, they feel,
> deserve it. They are not slaves. They have every right to choose whom
> they help, and other what conditions.
Yes, but as has been said repeatedly to you - the person would first have to
want to be helped in the first place. Otherwise, you are forcing yourself off
onto another. Similar to how rape happens. That being the one person forcing
themselves off onto the other.
Now - I want you to realize something. When you say "They have every right to
choose whom they help" you are correct. This is, after all, what I have said
all along. It is the "and other what conditions" (which I take to really mean
"and under what conditions") which is wrong. The first half of the sentence
says you want to help. The second says you have the right to rape me in order
for me to get the help. So somehow, I think I must say "Thank you," but "No
thank you".
> No one *has to be* tolerant of anything. I mean, if anything goes, why
> even have a hierarchy of groups. Why not have just one group where
> everyone asks whatever question he feels like asking, and those helpful
> volunteers can slave away trying to figure out which questions they can
> answer.
You obviously missed the entire point. As I said, if you want moderation use
c.l.p.moderated. If you want a hodge-podge of things to do with Perl you use
c.l.p.misc(ellaneous). Nor did I suggest that everything be dumped into one
group. Again - those are your words - not mine. And as for volunteers slaving
away: it can feel like that but it still doesn't give you the right to act like
you have. No one is forcing you to act like this. No one ever said you have to
treat people like you do. You just do. Or - you just don't.
>
> Having a hierarchy of groups with specialized topics and customs allow
> those helpful people to do the most good with the least effort.
Yes, it does. But misc is still misc. Good, bad, or ugly - it is still misc.
>
> You are proposing to make it hard for us to do good.
Again, >I< have not proposed you do anything with the groups. >YOU< may be now
proposing it; but >I< did no such thing.
>
> You are trying to bully us into accepting that the interface to a whole
> module which thousands of other people have successfully used ought to
> be changed because of your own incompetence. Do you really think that
> the colorAllocate method has been deficient all this time and you are
> the one genius who stumbled upon it?
Ah! More name calling. Now I'm incompetent. To answer your question though:
Genius? Ehhhhh...probably not. Stumbled upon it? Probably. After all, there
are litterally thousands of things which people have stumbled upon before this -
so why is it so amazing that I stumbled upon this problem?
>
> Don't answer that: We now know your arrogance does not know any limits.
Ah, yes. My arrogance knows no bounds. That's why you are saying such things
as "because of your own incompetence". Oh yes. I'm the one who's arrogant and
childish and misinformed. Hmmmmmmmmmmmm
>>go over and beat them up - you're just going to act like say - Hitler
>>and put up a set of rules and regulations and then try to enforce
>>those rules and regulations by ostracizing those who are different.
>
>
> Apparently you do not understand what Hitler and the Nazi's did.
Apparently I may better than you.
>
> Only someone with great insensitivity can equate the holocaust with a
> response to one's own rudeness. What an inappropriate comparison!
>
> http://en.wikipedia.org/wiki/Godwin's_law
>
> Sinan
Only someone who has lived through the aftermath knows how closely what you are
saying and doing is to what happened during that time.
Did you ever - perchance - read "The way"? Notice any similarities to what you
have been propounding and what the teacher did in the story?
Here's the link for you:
http://www.amazon.com/gp/product/0440993717/qid=1141760056/sr=1-1/ref=sr_1_1/002-9183861-4839212?s=books&v=glance&n=283155
------------------------------
Date: Tue, 07 Mar 2006 11:38:59 -0800
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: A Problem With GD
Message-Id: <070320061138595380%jgibson@mail.arc.nasa.gov>
In article <120rl955l6voa6f@corp.supernews.com>, Mark Manning
<markem@airmail.net> wrote:
> I have a question for you. Someone else has mentioned that I am
> "top-posting".
> All I am doing is using the reply button and everything is showing up like
> this:
>
> A
> +-->B
> +--->C
>
> and so on. Are you saying it is coming out as
>
> A
> B
> C
>
> ???? So instead of indenting properly it is starting a new thread each time?
No. Top-posting (also called TOFU) means adding comments at the
beginning of a reply instead of below the text to which you are
responding. Top-posting is very common in some e-mail communication
circles, but it is generally frowned upon in Usenet.
See, for example, <http://en.wikipedia.org/wiki/Top-posting>
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Tue, 7 Mar 2006 14:48:15 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Force numeric variable !
Message-Id: <slrne0rscf.4r4.tadmc@magna.augustmail.com>
S.Marion <sm244@kent.ac.uk> wrote:
> I want to compare 2 hexadecinal numbers.
There is no such thing as a "hexadecimal number",
there is only the concept of "a number".
There are many many *representations* of a particular number:
10 base 10
0A base 16
1010 base 2
5 + 5
Those all represent the *same* number, commonly referred to
as "ten".
> Consider this example:
> my $var1 = "0x00d9";
var1 does not contain a hexadecimal number.
It contains a string, which will, when used as if it was a number
be auto-converted to the number zero.
> my $var2 = 0x00d9;
var2 contains the number known as 217 in base 10.
> if ($var1 != $var2){
So here you have:
if (0 != 217 ){
> print "Yep, you get the point... it's not equal, which is my problem!!\n";
so you are *supposed* to get not-equal.
> How can I force perl to compare?
By converting the string in hex notation into an actual number.
Consider this example:
--------------------------
#!/usr/bin/perl
use warnings;
use strict;
my $var1 = "0x00d9";
my $var2 = 0x00d9;
# treat them as a string
print "var1 ($var1) is ", length($var1), " chars long\n";
print "var2 ($var2) is ", length($var2), " chars long\n";
# treat them as a number
print "var1 as a number is ", 0 + $var1, "\n";
print "var2 as a number is ", 0 + $var2, "\n";
# convert the string in hex notation to a number
if (hex($var1) == $var2){
print "they ARE equal!\n";
}
--------------------------
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Tue, 07 Mar 2006 20:58:50 GMT
From: Ronald Matthews <rm@biteme.org>
Subject: Re: Force numeric variable !
Message-Id: <eumPf.716$xM2.72434@news20.bellglobal.com>
Tad McClellan <tadmc@augustmail.com> trolled:
> S.Marion <sm244@kent.ac.uk> wrote:
> > I want to compare 2 hexadecinal numbers.
> There is no such thing as a "hexadecimal number",
> there is only the concept of "a number".
Here is a man with his head jammed, way, way, up his ass.
> There are many many *representations* of a particular number:
And any number expressed in base 16 is a hexadecimal number, you
dumb fuck. Do a google search for "hexadecimal number" and you will
come up with all kinds of definitions from online dictionaries.
Please, stop posting.
cordially, as always,
rm
------------------------------
Date: Tue, 07 Mar 2006 19:41:55 GMT
From: Ronald Matthews <rm@biteme.org>
Subject: Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <7mlPf.1278$Qh1.34670@news20.bellglobal.com>
Matt Garrish <matthew.garrish@sympatico.ca> trolled:
> Okay, let's walk through the subscriber agreement:
> - Transmitting unsolicited messages which, in the sole judgement
> of Your Service Provider, cause significant disruption or elicit
> complaints from other Internet users.
Sorry, but complaints from a few anals like you hardly constitutes
"significant disruption." In any case, they are talking about
emails, not usenet.
> You've got that one against you.
Actually that is one for our side.
> - Harassing users or groups in any way including but not limited
> to defaming, abusing, stalking, threatening or otherwise violating
> the legal rights of others.
We don't see any defamation, stalking, abusing. We don't see any
threats or violation of any legal rights. Hopefully, for your sake,
you'll be able to provide examples in your complaints.
> That makes two.
That's two fingers you've used. Only 8 more before you have to take
your shoes off.
> - Impersonating other Sympatico subscribers or other Internet service
> providers' subscribers in any way.
> This is the one you have trouble with. Try and comprehend the "in
> any way" part before you claim what you do and do not have a right
> to do on Bell's servers.
Sorry, sweetie. But using the same handle does not constitute
impersonation in any way. Try and comprehend the "in any way."
> - Create a false identity for the purpose of misleading others or
> forge the headers of your email messages in any way.
Nearly everyone posting to usenet creates false identities for the
purpose of misleading others. And I have yet to forge a valid email
header.
I hear you accusing me of stuff. But I don't see any examples of
what I am supposed to have done. Sympatico won't accept this. They
will want to see examples and if you don't provide them, your
"complaint" will be ignored.
cordially, as always,
rm
------------------------------
Date: Tue, 07 Mar 2006 19:17:25 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <Xns977F9179A5A9Basu1cornelledu@127.0.0.1>
Wolfgang Thomas <usenet@nana.franken.de> wrote in news:dukl07$lhr$01$1
@news.t-online.com:
> I have a line of the following format:
> string length followed by colon followed by the actual
> string.
> To extract the string with the correct length I use the
> following regular expression:
>
> my $s = "3:abcd";
> $s =~ /([\d]+):(.{\1})/;
Where did you get the notion that backreferences could be used in this
way?
...
> What am I doing wrong?
You are using regular expressions to solve a problem to which they are
ill-suited.
Important question: What do you want to do if the string to the right of
the colon is shorter than the length specified?
Your attempted use of .{\1} means you want the match to fail in that
case. I don't know if this matters.
#!/usr/bin/perl
use strict;
use warnings;
while ( <DATA> ) {
chomp;
next unless length;
my $length = 0 + substr $_, 0, index($_, ':');
my $string = substr $_, 1 + index($_, ':'), $length;
print "Length = $length\nString = $string\n";
}
__DATA__
3:abcd
10:012345689
3:abc
5:aaa
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Tue, 7 Mar 2006 14:21:06 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <y2lPf.639$xM2.68151@news20.bellglobal.com>
"Wolfgang Thomas" <usenet@nana.franken.de> wrote in message
news:dukl07$lhr$01$1@news.t-online.com...
>I have a line of the following format:
> string length followed by colon followed by the actual
> string.
So why aren't you using split and substr?
> To extract the string with the correct length I use the
> following regular expression:
>
> my $s = "3:abcd";
> $s =~ /([\d]+):(.{\1})/;
\d is shorthand for a character class; why are you then putting it in one?
> print "$1\n";
> print "$2\n";
>
>
> However this does not match. Neither $1 nor $2 become
> defined. If I replace \1 with 3 it works as expected,
> I get 3 in $1 and "abc" in $2.
>
That's because you can't dynamically assign the value. To perl it's just
braces and a comma to match. For example:
my $s = "3:a{,}bcd";
$s =~ /(\d+):(.{\1,})/;
print "$1\n";
print "$2\n";
There might be some way to do this using the extended regexes, but off the
top of my head I couldn't say, and would recommend the two functions named
above... : )
Matt
------------------------------
Date: Tue, 7 Mar 2006 14:23:40 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <Y4lPf.641$xM2.68434@news20.bellglobal.com>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
news:y2lPf.639$xM2.68151@news20.bellglobal.com...
>
> "Wolfgang Thomas" <usenet@nana.franken.de> wrote in message
> news:dukl07$lhr$01$1@news.t-online.com...
>>I have a line of the following format:
>> string length followed by colon followed by the actual
>> string.
>
> So why aren't you using split and substr?
>
>> To extract the string with the correct length I use the
>> following regular expression:
>>
>> my $s = "3:abcd";
>> $s =~ /([\d]+):(.{\1})/;
>
> \d is shorthand for a character class; why are you then putting it in one?
>
>> print "$1\n";
>> print "$2\n";
>>
>>
>> However this does not match. Neither $1 nor $2 become
>> defined. If I replace \1 with 3 it works as expected,
>> I get 3 in $1 and "abc" in $2.
>>
>
> That's because you can't dynamically assign the value. To perl it's just
> braces and a comma to match. For example:
>
> my $s = "3:a{,}bcd";
my $s = "3:a{3,}bcd";
Matt
------------------------------
Date: Tue, 7 Mar 2006 14:24:02 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <slrne0rqv2.4r4.tadmc@magna.augustmail.com>
Wolfgang Thomas <usenet@nana.franken.de> wrote:
> I have a line of the following format:
> string length followed by colon followed by the actual
> string.
> my $s = "3:abcd";
> $s =~ /([\d]+):(.{\1})/;
The square brackets serve no purpose there.
You would need the s///s modifier to handle "3:1\n34567".
> print "$1\n";
> print "$2\n";
You should *never* use the dollar-digit variables unless you
have first ensured that the pattern match *succeeded*:
if ( $s =~ /(\d+):(.{\1})/s ) {
print "$1\n";
...
> I have studied the "Perl Programming" book and
> the active perl regex documentation,
What is the "active perl regex documentation"?
Is that different from the standard documentation for Perl?
> but could not
> find a restriction that backreferences must not be
> used inside quantifiers.
Me either.
> What am I doing wrong?
Nothing, other than attempting to use a backreference inside
of a quantifier. :-)
Do it a different way, perhaps:
---------------------
#!/usr/bin/perl
use warnings;
use strict;
my($length, $string) = decompose( '3:abcd' );
print "string '$string' of length '$length'\n";
sub decompose {
my($s) = @_;
return() unless $s =~ s/^(\d+)://; # data does not match
my $len = $1;
my $str = substr $s, 0, $len;
return($len, $str);
}
---------------------
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Tue, 07 Mar 2006 22:00:22 +0100
From: Wolfgang Thomas <usenet@nana.franken.de>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <duks94$ve4$00$1@news.t-online.com>
All,
thank you for your replies. You showed me how to better solve the problem.
Nevertheless I think that this restriction (or is it a bug?) should be
documented.
------------------------------
Date: Tue, 07 Mar 2006 21:03:32 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <Xns977FA377C9EF6asu1cornelledu@127.0.0.1>
Wolfgang Thomas <usenet@nana.franken.de> wrote in
news:duks94$ve4$00$1@news.t-online.com:
> thank you for your replies. You showed me how to better solve the
> problem.
What way to solve what problem? Please quote some context when you reply.
> Nevertheless I think that this restriction (or is it a bug?) should be
> documented.
Feel free to document it.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Tue, 7 Mar 2006 21:42:27 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <dukuo3$q4t$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
Wolfgang Thomas
<usenet@nana.franken.de>], who wrote in article <dukl07$lhr$01$1@news.t-online.com>:
> $s =~ /([\d]+):(.{\1})/;
This should match, e.g.,
123:a{123}
"{" is special in REx only in very few of contexts. When working over
RExen, I tried to "f1x" this misfeature (inheritance of [IMO,
completely broken] HS implementation); however, there was not way to
even insert a warning without heavy backward-compatibility penalty.
The best one can hope for is what the latest CPerl is doing to
circumvent this misfortune: it highlights "{" differently in the
different meanings...
Hope this helps,
Ilya
------------------------------
Date: Tue, 07 Mar 2006 23:44:22 +0100
From: Wolfgang Thomas <usenet@nana.franken.de>
Subject: Re: Regex: Backreferences do not work inside quantifiers?
Message-Id: <dul2c4$cb3$03$1@news.t-online.com>
Ilya Zakharevich wrote:
>> $s =~ /([\d]+):(.{\1})/;
>
> This should match, e.g.,
>
> 123:a{123}
>
> "{" is special in REx only in very few of contexts. When working over
> RExen, I tried to "f1x" this misfeature (inheritance of [IMO,
> completely broken] HS implementation); however, there was not way to
> even insert a warning without heavy backward-compatibility penalty.
>
> The best one can hope for is what the latest CPerl is doing to
> circumvent this misfortune: it highlights "{" differently in the
> different meanings...
>
> Hope this helps,
This was in fact very helpful. Thanks a lot.
------------------------------
Date: Tue, 07 Mar 2006 22:33:16 GMT
From: Rhonda Moffat <rm@biteme.org>
Subject: Re: Standing in line (was Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $))
Message-Id: <MSnPf.1026$xM2.79049@news20.bellglobal.com>
Matt Garrish <matthew.garrish@sympatico.ca> trolled:
> Right. Another cowardly, hypocritical lie from Roger Maynard. He
> curries favour with alt.rec.baseball by advocating Margarino, and
> then he comes to CPLM and advocates Parkay because people here
> like that better. CLPM is not for cowards who are afraid to use
> their real names.
Ok, we give up. Our real name is Rhonda Moffat. If you do a google
search you will see that this is true.
> We sh!t squarely in the face of Coward Ronald Matthews and we
> advise all others to do the same.
We don't know what we'll do if Rhonda isn't good enough for you.
cordially, as always,
rm
------------------------------
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 9027
***************************************
