[16839] in Perl-Users-Digest
Perl-Users Digest, Issue: 4251 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Sep 7 18:10:31 2000
Date: Thu, 7 Sep 2000 15:10:15 -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: <968364615-v9-i4251@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Thu, 7 Sep 2000 Volume: 9 Number: 4251
Today's topics:
perl book? <kphung@interchange.ubc.ca>
Re: perl book? <kelley.a.kent@intel.com>
Re: perl book? <ddorward@hotmail.com>
Re: perl book? (Mark-Jason Dominus)
Re: perl book? <kelley.a.kent@intel.com>
Re: perl book? (David Wall)
Re: perl book? <montuori@arrakisplanet.com>
Re: perl book? <sysnovice@my-deja.com>
Re: perl book? (Craig Berry)
Re: perl book? (Abigail)
pl2bat missing from IndigoPerl distribution <cogswheel@my-deja.com>
Re: Small golf problem (Craig Berry)
The Heartbreak of Inscrutable Perl Code (avast)
Re: The Heartbreak of Inscrutable Perl Code <care227@attglobal.net>
Re: The Heartbreak of Inscrutable Perl Code <lr@hpl.hp.com>
Re: Trouble using CGI.pm on VMS Perl <dan@tuatha.sidhe.org>
Re: World Wide PERL PROGRAMMERS TELECOMMUTE <gellyfish@gellyfish.com>
Re: World Wide PERL PROGRAMMERS TELECOMMUTE <care227@attglobal.net>
Re: World Wide PERL PROGRAMMERS TELECOMMUTE <care227@attglobal.net>
Re: World Wide PERL PROGRAMMERS TELECOMMUTE <uri@sysarch.com>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 7 Sep 2000 12:24:00 -0700
From: "kevin" <kphung@interchange.ubc.ca>
Subject: perl book?
Message-Id: <8p8pcq$o92$1@nntp.itservices.ubc.ca>
so what's THE perl book to buy?
------------------------------
Date: Thu, 7 Sep 2000 12:29:00 -0700
From: "Kelley Kent" <kelley.a.kent@intel.com>
Subject: Re: perl book?
Message-Id: <8p8q7h$nhv@news.or.intel.com>
> so what's THE perl book to buy?
IMHO ....
- for learning Perl, it's Teach yourself Perl in 21 days (Sam's).
There's a Unix and Windows version available (or at least there used to be).
- for reference, without question it's Programming Perl 2nd edition.
- for more advanced Perl topics, both the Perl Cookbook and Advanced
Perl Programming are excellent (both O'Reilly)
- for fun (at least I enjoyed reading it) is Effective Perl Programming
(Addison Wesley). Many Perl nuances are covered quite well.
-- Kelley
------------------------------
Date: Thu, 07 Sep 2000 20:32:50 +0100
From: David Dorward <ddorward@hotmail.com>
To: kevin <kphung@interchange.ubc.ca>
Subject: Re: perl book?
Message-Id: <39B7ED62.DE2134FF@hotmail.com>
kevin wrote:
>
> so what's THE perl book to buy?
I like the Perl CD Bookshelf
http://www.amazon.co.uk/exec/obidos/ASIN/1565924622/o/qid=960649629/sr=2-3/026-8242836-0969228/daviddorward/
NB: The above link is an affiliate link, so there is a possible conflict
of interest here. BUT I really do think it is a good book. (1 book + 6
ebooks on CD)
--
David Dorward
http://www.dorward.co.uk/
------------------------------
Date: Thu, 07 Sep 2000 20:19:24 GMT
From: mjd@plover.com (Mark-Jason Dominus)
Subject: Re: perl book?
Message-Id: <39b7f84c.4578$30d@news.op.net>
In article <8p8q7h$nhv@news.or.intel.com>,
Kelley Kent <kelley.a.kent@intel.com> wrote:
> - for reference, without question it's Programming Perl 2nd edition.
Why the 2nd edition and not the 3rd edition?
------------------------------
Date: Thu, 7 Sep 2000 13:27:37 -0700
From: "Kelley Kent" <kelley.a.kent@intel.com>
Subject: Re: perl book?
Message-Id: <8p8tle$q5l@news.or.intel.com>
> > - for reference, without question it's Programming Perl 2nd edition.
>
> Why the 2nd edition and not the 3rd edition?
Mainly cause I didn't realise there was a 3rd edition out there. And I
thought I was well on my way to becoming a perl guru. Curses! :-p
-- Kelley
------------------------------
Date: 7 Sep 2000 16:48:42 -0400
From: darkon@one.net (David Wall)
Subject: Re: perl book?
Message-Id: <8FA8A72CBdarkononenet@206.112.192.118>
kelley.a.kent@intel.com (Kelley Kent) wrote in
<8p8q7h$nhv@news.or.intel.com>:
> - for reference, without question it's Programming Perl 2nd edition.
It's a good book, but I'd recommend getting the 3rd edition. :-)
--
David Wall
darkon@one.net
------------------------------
Date: Thu, 7 Sep 2000 16:42:33 -0400
From: kevin montuori <montuori@arrakisplanet.com>
Subject: Re: perl book?
Message-Id: <ydy1yywx7av.fsf@kulon.arrakisplanet.com>
>>> Kelley Kent writes:
>> so what's THE perl book to buy?
the one that looks the nicest on your shelf, of course.
kk> [...] it's Programming Perl 2nd edition.
third edition. the second edition is very out of date.
for what it's worth, i think this article:
http://x64.deja.com/getdoc.xp?AN=662518976&CONTEXT=968358690.883359755&hitnum=3
sums up the current state of Perl literature quite well.
cheers,
k.
--
kevin montuori
------------------------------
Date: Thu, 07 Sep 2000 21:13:48 GMT
From: Greg Donovan <sysnovice@my-deja.com>
Subject: Re: perl book?
Message-Id: <8p90dn$jei$1@nnrp1.deja.com>
In article <8p8pcq$o92$1@nntp.itservices.ubc.ca>,
"kevin" <kphung@interchange.ubc.ca> wrote:
> so what's THE perl book to buy?
>
> If you have no programming experience "Beggining Perl by Simon Cozens"
is a good book.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Thu, 07 Sep 2000 21:18:56 GMT
From: cberry@cinenet.net (Craig Berry)
Subject: Re: perl book?
Message-Id: <srg1i0rkljn46@corp.supernews.com>
kevin (kphung@interchange.ubc.ca) wrote:
: so what's THE perl book to buy?
For learning, _Learning Perl_; for reference, _The Perl Programming
Language_. AKA "The Llama" and "The Camel" respectively. Both are
published by O'Reilly.
--
| Craig Berry - http://www.cinenet.net/~cberry/
--*-- "Every force evolves a form."
| - Shriekback
------------------------------
Date: 07 Sep 2000 21:58:17 GMT
From: abigail@foad.org (Abigail)
Subject: Re: perl book?
Message-Id: <slrn8rg3pu.vlt.abigail@alexandra.foad.org>
Craig Berry (cberry@cinenet.net) wrote on MMDLXIV September MCMXCIII in
<URL:news:srg1i0rkljn46@corp.supernews.com>:
** kevin (kphung@interchange.ubc.ca) wrote:
** : so what's THE perl book to buy?
**
** For learning, _Learning Perl_; for reference, _The Perl Programming
** Language_. AKA "The Llama" and "The Camel" respectively. Both are
** published by O'Reilly.
For learning, there are at least 3 books I'd strongly prefer over the
Llama, and none of them are published by O'Reilly.
Nigel Chapman: "Perl, the programmers compagnion"
Clint Pierce: "Teach yourself Perl in 24 hours"
Andrew Johnson: "Elements of Programming with Perl"
However, if you want to spend the money on just one book to make your
Perl programming better, buy "Advanced Programming in the UNIX Environment"
from Stevens.
Abigail
--
sub _'_{$_'_=~s/$a/$_/}map{$$_=$Z++}Y,a..z,A..X;*{($_::_=sprintf+q=%X==>"$A$Y".
"$b$r$T$u")=~s~0~O~g;map+_::_,U=>T=>L=>$Z;$_::_}=*_;sub _{print+/.*::(.*)/s};;;
*_'_=*{chr($b*$e)};*__=*{chr(1<<$e)}; # Perl 5.6.0 broke this...
_::_(r(e(k(c(a(H(__(l(r(e(P(__(r(e(h(t(o(n(a(__(t(us(J())))))))))))))))))))))))
------------------------------
Date: Thu, 7 Sep 2000 14:18:18 -0500
From: "Cogswheel" <cogswheel@my-deja.com>
Subject: pl2bat missing from IndigoPerl distribution
Message-Id: <8p8pg7$sep$1@unlnews.unl.edu>
I just downloaded and installed the IndigoPerl distribution for Win32
and discovered that there was no pl2bat utility included. Could someone
point me to a source?
Thanks,
Cogswheel
------------------------------
Date: Thu, 07 Sep 2000 21:13:21 GMT
From: cberry@cinenet.net (Craig Berry)
Subject: Re: Small golf problem
Message-Id: <srg17hu1ljn100@corp.supernews.com>
Yanick Champoux (yanick@babyl.sympatico.ca) wrote:
: That one is a wee bit shorter. But I can't vouch
: for the 'smarter' part. :)
:
: my %foo = ( key1 => 1, key2 => 1, key3 => 0, key4 => 0 );
:
: my $s = ';';
: $s = $foo{$_}?"$_,$s":"$s,$_" for keys %foo;
: $s =~ s/,?;,?/;/;
:
: print $s;
Nice. Or how about:
@a=grep{$foo{$_}}keys%foo;
delete@foo{@a};
print join';',map{join',',@$_}[keys%foo],\@a;
--
| Craig Berry - http://www.cinenet.net/~cberry/
--*-- "Every force evolves a form."
| - Shriekback
------------------------------
Date: Thu, 07 Sep 2000 20:14:49 GMT
From: avast@hortonsbay.com (avast)
Subject: The Heartbreak of Inscrutable Perl Code
Message-Id: <39b7f250.27089060@news.mco.edu>
In article <MPG.14205c5c8ef332e98ad2f@nntp.hpl.hp.com>,
Larry Rosler <lr@hpl.hp.com> wrote:
<snip>
> Here is some compactly-writtten code to play with. I don't have time to
> write a detailed explanation. Breaking it down into beginner-level code
> may be instructive as an exercise.
>
> #!/usr/bin/perl -w
> use strict;
>
> my %users;
> chomp(my $fields = <DATA>);
> my @fields = split /,\s+/ => $fields;
>
> /([^,]+),\s+([^,]+),\s+"([^@]+)/ and
> @{$users{$1}{@fields[1, 2]}} = ($2, $3) while <DATA>;
>
> {
> local ($,, $\) = ("\t", "\n");
> print @fields, "\n";
> print $_, @{$users{$_}{@fields[1, 2]}} for sort keys %users;
> }
> __END__
> user, password, alias
> Rod, abc, "rod@hotmail.com"
> Jane, def, "jane@excite.com"
> Freddy, ghi, "freddy@bigfoot.com"
As a perl (or is it Perl?) novice I find it extremely instructive to
analyze the code of highly experienced pratitioners. Larry's above
example is a good one. Coming from C and COBOL (please don't laugh),
however, I continue to have some difficulty with perl idioms. Some of
these idioms (e.g., foreach my $thingy (@somearray) ) are clearly
superior to C's more clunky "for (x=0;x<something;x++)" both in
readability and expressiveness. Others, unfortunately, still seem
overly obtuse and inscrutable to me. For example the line:
my @fields = split /,\s+/ => $fields;
can be re-written as:
$fields =~ s/ +//g;
@fields = split /,/,$fields;
Larry's example uses one line instead of two but to what end? My
assumption is that Larry is doing this for a good reason and the
reason probably has to do with speed. Question number 1: Is it OK to
err on the side of clarity (i.e., two lines) or should one ultimately
strive for the compactness of Larry's example?
Even more inscrutable to me is the following:
/([^,]+),\s+([^,]+),\s+"([^@]+)/ and
@{$users{$1}{@fields[1, 2]}} = ($2, $3) while <DATA>;
It'll probably take a good hour or so for me to puzzle this one out.
Again, is this type of compactness something to strive for or is it
merely a personal preference on the part of the author? Are there
useful lessons hidden here?
Most inscruatble of all is:
{
local ($,, $\) = ("\t", "\n");
print @fields, "\n";
print $_, @{$users{$_}{@fields[1, 2]}} for sort keys %users;
}
The use of the seemingly bare curly braces is something I've not see
before. Additionally, the use of "local" instead of "my" here seems
significant but I have no idea why it's used in this case. I know
that "local" saves the values of it's arguments on a run time stack
and puts them back when the script leaves the "block" containing
"local". In the above case I don't see the significance in doing
this. I'm sure that there's a good reason but my noviceness is
keeping the scales firmly attached to my eyeballs at this point. I'm
not even sure where to go to look for the answer (not _what_ local
is but _when_ to use it).
This kind of stuff is extremely depressing to me in that what I think
I know about perl and how to use it seems horribly trivial and
mundane. My ultimate goal is to be able to write stuff like the
above code without even thinking about it. I want it to be second
nature. My problem right now is I'm not sure how to get there. Any
advice would be greatly appreciated.
Avast
------------------------------
Date: 07 Sep 2000 21:16:45 GMT
From: Drew Simonis <care227@attglobal.net>
Subject: Re: The Heartbreak of Inscrutable Perl Code
Message-Id: <39B80337.9DF78F6E@attglobal.net>
avast wrote:
>
> Others, unfortunately, still seem
> overly obtuse and inscrutable to me. For example the line:
>
> my @fields = split /,\s+/ => $fields;
>
> can be re-written as:
>
> $fields =~ s/ +//g;
> @fields = split /,/,$fields;
>
> Larry's example uses one line instead of two but to what end?
Compactness, lower golf scores.
> My
> assumption is that Larry is doing this for a good reason and the
> reason probably has to do with speed.
This can be checked using the benchmark module. And its fun too!
> Question number 1: Is it OK to
> err on the side of clarity (i.e., two lines) or should one ultimately
> strive for the compactness of Larry's example?
This is up to you. If you are writing large programs that need to
be maintained for a long while by other programmers, perhaps writing
in a more verbose style is in order. If you are writing for yourself,
or you are very carefull about comments, you can feel free to use
the more compact syntax. Remember the Perl motto...
> Even more inscrutable to me is the following:
>
> /([^,]+),\s+([^,]+),\s+"([^@]+)/ and
> @{$users{$1}{@fields[1, 2]}} = ($2, $3) while <DATA>;
>
> Are there useful lessons hidden here?
If you hold that code up to a mirror, it reveals the name of Larry's
secret identity! Remember, Larry and his ilk are masters among us.
Always strive to be your best, and use these bits of flare as
benchmarks to measure your progress.
>
> Most inscruatble of all is:
>
> {
> local ($,, $\) = ("\t", "\n");
> print @fields, "\n";
> print $_, @{$users{$_}{@fields[1, 2]}} for sort keys %users;
> }
>
> The use of the seemingly bare curly braces is something I've not see
> before.
Bare blocks enable the use of local without impacting other parts
of the program, but where a subroutine is not in order.
> Additionally, the use of "local" instead of "my" here seems
> significant but I have no idea why it's used in this case.
my() creates an entirely new variable with no relation to others
of the same name. local() creates a temporary copy of the variable.
When dealing with builtin vars, such as in this example, it is
necessary to use local().
>
> This kind of stuff is extremely depressing to me in that what I think
> I know about perl and how to use it seems horribly trivial and
> mundane. My ultimate goal is to be able to write stuff like the
> above code without even thinking about it. I want it to be second
> nature. My problem right now is I'm not sure how to get there. Any
> advice would be greatly appreciated.
Practice, practice and more practice. Work up a solution to every
problem posted here, and then compare with what the pro's post in
response. You'll learn all sorts of shortcuts.
------------------------------
Date: Thu, 7 Sep 2000 14:58:24 -0700
From: Larry Rosler <lr@hpl.hp.com>
Subject: Re: The Heartbreak of Inscrutable Perl Code
Message-Id: <MPG.1421af569b10115098ad38@nntp.hpl.hp.com>
In article <39b7f250.27089060@news.mco.edu> on Thu, 07 Sep 2000 20:14:49
GMT, avast <avast@hortonsbay.com> says...
+ In article <MPG.14205c5c8ef332e98ad2f@nntp.hpl.hp.com>,
+ Larry Rosler <lr@hpl.hp.com> wrote:
+ <snip>
+ > Here is some compactly-writtten code to play with. I don't have
+ > time to write a detailed explanation.
Apparently I will end up doing just that! :-)
+ > Breaking it down into beginner-level
+ > code may be instructive as an exercise.
+ >
+ > #!/usr/bin/perl -w
+ > use strict;
+ >
+ > my %users;
+ > chomp(my $fields = <DATA>);
+ > my @fields = split /,\s+/ => $fields;
+ >
+ > /([^,]+),\s+([^,]+),\s+"([^@]+)/ and
+ > @{$users{$1}{@fields[1, 2]}} = ($2, $3) while <DATA>;
+ >
+ > {
+ > local ($,, $\) = ("\t", "\n");
+ > print @fields, "\n";
+ > print $_, @{$users{$_}{@fields[1, 2]}} for sort keys %users;
+ > }
+ > __END__
+ > user, password, alias
+ > Rod, abc, "rod@hotmail.com"
+ > Jane, def, "jane@excite.com"
+ > Freddy, ghi, "freddy@bigfoot.com"
+
+ As a perl (or is it Perl?) novice I find it extremely instructive to
+ analyze the code of highly experienced pratitioners.
perlfaq1: "What's the difference between ``perl'' and ``Perl''?"
+ Larry's above
+ example is a good one. Coming from C and COBOL (please don't laugh),
+ however, I continue to have some difficulty with perl idioms. Some of
+ these idioms (e.g., foreach my $thingy (@somearray) ) are clearly
+ superior to C's more clunky "for (x=0;x<something;x++)" both in
+ readability and expressiveness. Others, unfortunately, still seem
+ overly obtuse and inscrutable to me. For example the line:
+
+ my @fields = split /,\s+/ => $fields;
+
+ can be re-written as:
+
+ $fields =~ s/ +//g;
+ @fields = split /,/,$fields;
+
+ Larry's example uses one line instead of two but to what end? My
+ assumption is that Larry is doing this for a good reason and the
+ reason probably has to do with speed.
It has to do with dealing with the particular problem. The data shown
use a comma followed by a space as the field separator. For all I know,
some day one of the data fields would include an interior space, which
your first line of code would wipe out.
As for the generalization from one space to a sequence of whitespace
characters, that allows for my having misread the space for a tab, or
whatever. Call it 'Defensive Coding', which adds robustness to the code
at little or no expense.
+ Question number 1: Is it OK to
+ err on the side of clarity (i.e., two lines) or should one ultimately
+ strive for the compactness of Larry's example?
It is OK to 'err' on the side of correctness.
+ Even more inscrutable to me is the following:
+
+ /([^,]+),\s+([^,]+),\s+"([^@]+)/ and
+ @{$users{$1}{@fields[1, 2]}} = ($2, $3) while <DATA>;
+
+ It'll probably take a good hour or so for me to puzzle this one out.
+ Again, is this type of compactness something to strive for or is it
+ merely a personal preference on the part of the author? Are there
+ useful lessons hidden here?
This is personal preference, or bravado. It may actually be harder to
maintain this kind of code in real programs. Some would prefer it the
following way, which is functionally identical but has lots more
punctuation:
while (<DATA>) {
next unless /([^,]+),\s+([^,]+),\s+"([^@]+)/;
@{$users{$1}{@fields[1, 2]}} = ($2, $3);
}
The assignment to a hash slice using an array slice for the keys is just
a bit of instructive fun.
$users{$1}{$fields[1]} = $2;
$users{$1}{$fields[2]} = $3;
How very mundane!
+ Most inscruatble of all is:
+
+ {
+ local ($,, $\) = ("\t", "\n");
+ print @fields, "\n";
+ print $_, @{$users{$_}{@fields[1, 2]}} for sort keys %users;
+ }
+
+ The use of the seemingly bare curly braces is something I've not see
+ before.
It creates a naked block, which lets one restrict the visibility of any
variables declared within it. The same thing works for C++ or for C; in
the latter declarations must be at the top of the block.
+ Additionally, the use of "local" instead of "my" here seems
+ significant but I have no idea why it's used in this case.
One cannot use 'my' for Perl special variables.
+ I know
+ that "local" saves the values of it's arguments on a run time stack
+ and puts them back when the script leaves the "block" containing
+ "local". In the above case I don't see the significance in doing
+ this.
So as not to mess up any output statements later that might expect the
default values of these variables. There are no such statements in this
tiny example, but the idea is to make good practices habitual.
+ I'm sure that there's a good reason but my noviceness is
+ keeping the scales firmly attached to my eyeballs at this point. I'm
+ not even sure where to go to look for the answer (not _what_ local
+ is but _when_ to use it).
perlfaq7: "What's the difference between dynamic and lexical (static)
scoping? Between local() and my()?"
+ This kind of stuff is extremely depressing to me in that what I think
+ I know about perl and how to use it seems horribly trivial and
+ mundane. My ultimate goal is to be able to write stuff like the
+ above code without even thinking about it. I want it to be second
+ nature. My problem right now is I'm not sure how to get there. Any
+ advice would be greatly appreciated.
Read the newsgroup, read The Perl Cookbook (where the authors don't go
out of their way for compactness, just for style), read, ..., and
write, write, write...
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: Thu, 07 Sep 2000 21:22:10 GMT
From: Dan Sugalski <dan@tuatha.sidhe.org>
Subject: Re: Trouble using CGI.pm on VMS Perl
Message-Id: <6GTt5.8016$CW2.89798@news1.rdc1.ct.home.com>
Mike Flaherty <mflaherty2@earthlink.net> wrote:
> #!/usr/local/bin/perl
> use CGI;
> $query = new CGI;
> this is expected. However, when I run the same script (minus the path to
> perl) on VMS, I get
> DILBRT> perl billperl.pl
> Unrecognized character \x13 at /perl_root/lib/shellwords.pl line 49.
> Compilation failed in require at (eval 2) line 7.
> %SYSTEM-F-NOLOGNAM, no logical name match
> DILBRT>
You probably FTP'd it over in binary mode or something of the sort. (Or
SAMBA got the file conversion wrong, or something) That program works OK
either typed in directly or when dumped into a file on VMS, so odds are
you've got some spurious characters in there. (0x13 is a Control-S--might
want to pull the file into EDT and see if there are any in there, or any
other control characters)
Dan
------------------------------
Date: 6 Sep 2000 21:01:04 +0100
From: Jonathan Stowe <gellyfish@gellyfish.com>
Subject: Re: World Wide PERL PROGRAMMERS TELECOMMUTE
Message-Id: <8p67q0$2tv$1@orpheus.gellyfish.com>
On Tue, 05 Sep 2000 23:09:12 GMT Chris wrote:
> No offense Guttman but if I had to pick on who I didn't want in the
> group it would be you. Take a look at some of your responses to posts
> and you'll see why, you are the only person that replies with such
> hate towards everything.
>
> Soo back in your face for all the newbies you shit on.
>
Bye, Bye
*plonk*
/J\
--
yapc::Europe in assocation with the Institute Of Contemporary Arts
<http://www.yapc.org/Europe/> <http://www.ica.org.uk>
------------------------------
Date: 07 Sep 2000 21:01:56 GMT
From: Drew Simonis <care227@attglobal.net>
Subject: Re: World Wide PERL PROGRAMMERS TELECOMMUTE
Message-Id: <39B7FFC0.BEF12453@attglobal.net>
Russ Jones wrote:
>
> Raphael Pirker wrote:
> >
> > > P> $15.00 to $25.00 per hour commensurate with experience.
> > consider adding a 0 to your offer or you won't get any programmer!
>
> I happen to know that Drew needs a job and he'll work for $15.000 to
> $25.000. (US, where that's a decimal point)
I do not! I am now again gainfully employeed and I haven't worked for
that small ammount of money in days!
------------------------------
Date: 07 Sep 2000 21:03:44 GMT
From: Drew Simonis <care227@attglobal.net>
Subject: Re: World Wide PERL PROGRAMMERS TELECOMMUTE
Message-Id: <39B8002C.13C5D0B9@attglobal.net>
Uri Guttman wrote:
>
> >>>>> "C" == Chris <exit72@excite.com> writes:
>
> C> No offense Guttman but if I had to pick on who I didn't want in the
> ^^ ^^^^^^^
> C> group it would be you. Take a look at some of your responses to posts
> C> and you'll see why, you are the only person that replies with such
> C> hate towards everything.
>
> C> Soo back in your face for all the newbies you shit on.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> i don't know what your definition of no offense is, but that hurts! :)
>
Worse than being called Buttman?
------------------------------
Date: Thu, 07 Sep 2000 21:52:52 GMT
From: Uri Guttman <uri@sysarch.com>
Subject: Re: World Wide PERL PROGRAMMERS TELECOMMUTE
Message-Id: <x7em2vkgy4.fsf@home.sysarch.com>
>>>>> "DS" == Drew Simonis <care227@attglobal.net> writes:
DS> Uri Guttman wrote:
>>
>> >>>>> "C" == Chris <exit72@excite.com> writes:
>>
C> No offense Guttman but if I had to pick on who I didn't want in the
>> ^^ ^^^^^^^
C> group it would be you. Take a look at some of your responses to posts
C> and you'll see why, you are the only person that replies with such
C> hate towards everything.
>>
C> Soo back in your face for all the newbies you shit on.
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> i don't know what your definition of no offense is, but that hurts! :)
>>
DS> Worse than being called Buttman?
moronzilla calling me buttman hurts the least of all the insults i had
had thrown at me. even lower than this twit who said no offense when
offending.
uri
--
Uri Guttman --------- uri@sysarch.com ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
------------------------------
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 4251
**************************************
