[30472] in Perl-Users-Digest
Perl-Users Digest, Issue: 1715 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Jul 13 03:09:44 2008
Date: Sun, 13 Jul 2008 00:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sun, 13 Jul 2008 Volume: 11 Number: 1715
Today's topics:
Re: Could someone give me suggestions with my code? <rvtol+news@isolution.nl>
Re: Could someone give me suggestions with my code? <woody334@hotmail.com>
Re: empty first element after split <rvtol+news@isolution.nl>
Re: FAQ 1.1 What is Perl? <brian.d.foy@gmail.com>
Re: FAQ 1.1 What is Perl? <bill@ts1000.us>
Re: FAQ 1.1 What is Perl? <kkeller-usenet@wombat.san-francisco.ca.us>
Re: FAQ 1.1 What is Perl? <fawaka@gmail.com>
Re: FAQ 1.1 What is Perl? <szrRE@szromanMO.comVE>
Re: FAQ 1.12 What's the difference between "perl" and " <jwkenne@attglobal.net>
Re: FAQ 1.12 What's the difference between "perl" and " <seysig@gmail.com>
Re: How to get Perl CGI working on Mac OS 10.5? <szrRE@szromanMO.comVE>
new CPAN modules on Sun Jul 13 2008 (Randal Schwartz)
Re: remove previous lines of a log file (Jens Thoms Toerring)
Re: remove previous lines of a log file <fawaka@gmail.com>
Re: remove previous lines of a log file <fawaka@gmail.com>
Re: remove previous lines of a log file (Jens Thoms Toerring)
Re: Value of "Programming perl" 1st Ed.? <kkeller-usenet@wombat.san-francisco.ca.us>
Re: Value of "Programming perl" 1st Ed.? <kkeller-usenet@wombat.san-francisco.ca.us>
Re: Value of "Programming perl" 1st Ed.? <sky@shaw.ca>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 12 Jul 2008 22:50:52 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Could someone give me suggestions with my code?
Message-Id: <g5bcj1.nc.1@news.isolution.nl>
Uri Guttman schreef:
> today 1mb can be condsidered small
millibits were already small.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Sat, 12 Jul 2008 17:48:45 -0500
From: "JustinSain" <woody334@hotmail.com>
Subject: Re: Could someone give me suggestions with my code?
Message-Id: <dZSdnQG6R8HRqOTVnZ2dnUVZ_uGdnZ2d@centurytel.net>
> Uri Guttman schreef:
>
>> today 1mb can be condsidered small
>
> millibits were already small.
>
> --
> Affijn, Ruud
Roflmao ;-) Precisely !
------------------------------
Date: Sat, 12 Jul 2008 23:10:55 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: empty first element after split
Message-Id: <g5bdol.1ks.1@news.isolution.nl>
Tad J McClellan schreef:
> Michael Hamer:
>> my @fields = split /^([^:]+):\s*/m;
>> shift @fields; # for leading null field
>
> Others have answered your real question, but I'll point out
> that those 2 lines can be replaced with:
>
> my(undef, @fields) = split /^([^:]+):\s*/m; # ignore leading null
> field
The "[^:]+" can match a newline, so a "^([^:]+):" in a multiline context
is probably better written as "^(.+?):".
$ echo -ne "A: aaa\nB: bbb\n bbb\nC: ccc\n" |
perl -le'
undef $/;
$_ = <>;
print;
print "<$_>" for split /^([^:]+):\s*/m
'
A: aaa
B: bbb
bbb
C: ccc
<>
<A>
<aaa
>
<B>
<bbb
>
< bbb
C>
<ccc
>
$ echo -ne "A: aaa\nB: bbb\n bbb\nC: ccc\n" |
perl -le'
undef $/;
$_ = <>;
print;
print "<$_>" for split /^(.+?):\s*/m
'
A: aaa
B: bbb
bbb
C: ccc
<>
<A>
<aaa
>
<B>
<bbb
bbb
>
<C>
<ccc
>
A further variant, that captures a header field value that is white
space only:
$ echo -ne "A: aaa\nB: bbb\n bbb\nC:\n \nD: ddd\n" |
perl -le'
undef $/;
$_ = <>;
print;
print "<$_>" for split /^(.+?):[^\n\S]*/m
'
A: aaa
B: bbb
bbb
C:
D: ddd
<>
<A>
<aaa
>
<B>
<bbb
bbb
>
<C>
<
>
<D>
<ddd
>
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Sat, 12 Jul 2008 14:08:52 -0500
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 1.1 What is Perl?
Message-Id: <120720081408526445%brian.d.foy@gmail.com>
In article
<cea2add7-7842-4104-aeb7-adf27856c2ac@l42g2000hsc.googlegroups.com>,
Bill H <bill@ts1000.us> wrote:
> Is the FAQ server talking to itself here?
What do you mean? If you think there's a problem, can you be more
specific?
Thanks,
------------------------------
Date: Sat, 12 Jul 2008 15:48:14 -0700 (PDT)
From: Bill H <bill@ts1000.us>
Subject: Re: FAQ 1.1 What is Perl?
Message-Id: <2413f93b-8719-4fe4-98e4-f819856d18c1@34g2000hsf.googlegroups.com>
On Jul 12, 3:08=A0pm, brian d foy <brian.d....@gmail.com> wrote:
> In article
> <cea2add7-7842-4104-aeb7-adf27856c...@l42g2000hsc.googlegroups.com>,
>
> Bill H <b...@ts1000.us> wrote:
> > Is the FAQ server talking to itself here?
>
> What do you mean? If you think there's a problem, can you be more
> specific?
>
> Thanks,
Hi brian
On July 5th the server posted this, then on July 11th it posted it
again. Google has them linked up as a single conversation - so it
appears that the server is talking to itself.
Bill H
------------------------------
Date: Sat, 12 Jul 2008 16:11:13 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: FAQ 1.1 What is Perl?
Message-Id: <i9qnk5x6kh.ln2@goaway.wombat.san-francisco.ca.us>
On 2008-07-12, Bill H <bill@ts1000.us> wrote:
>
> On July 5th the server posted this, then on July 11th it posted it
> again. Google has them linked up as a single conversation - so it
> appears that the server is talking to itself.
That's just how Google is displaying the messages. There is no direct
link between the two postings other than the similarity of the Subject:
headers (which can't be helped).
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: 12 Jul 2008 23:23:08 GMT
From: Leon Timmermans <fawaka@gmail.com>
Subject: Re: FAQ 1.1 What is Perl?
Message-Id: <pan.2008.07.12.23.23.28@gmail.com>
On Sat, 12 Jul 2008 15:48:14 -0700, Bill H wrote:
> On Jul 12, 3:08 pm, brian d foy <brian.d....@gmail.com> wrote:
>> In article
>> <cea2add7-7842-4104-aeb7-adf27856c...@l42g2000hsc.googlegroups.com>,
>>
>> Bill H <b...@ts1000.us> wrote:
>> > Is the FAQ server talking to itself here?
>>
>> What do you mean? If you think there's a problem, can you be more
>> specific?
>>
>> Thanks,
>
> Hi brian
>
> On July 5th the server posted this, then on July 11th it posted it
> again. Google has them linked up as a single conversation - so it
> appears that the server is talking to itself.
>
> Bill H
The problem with that is simple: the way google groups works. Never
assume other people will see it the way GG presents it to you, that will
confuse other people.
Leon Timmermans
------------------------------
Date: Sat, 12 Jul 2008 23:39:50 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: FAQ 1.1 What is Perl?
Message-Id: <g5c7vm072h@news4.newsguy.com>
Bill H wrote:
> On Jul 12, 3:08 pm, brian d foy <brian.d....@gmail.com> wrote:
>> In article
>> <cea2add7-7842-4104-aeb7-adf27856c...@l42g2000hsc.googlegroups.com>,
>>
>> Bill H <b...@ts1000.us> wrote:
>>> Is the FAQ server talking to itself here?
>>
>> What do you mean? If you think there's a problem, can you be more
>> specific?
>>
>> Thanks,
>
> Hi brian
>
> On July 5th the server posted this, then on July 11th it posted it
> again. Google has them linked up as a single conversation - so it
> appears that the server is talking to itself.
There are also some news readers that (incorrectly) will group messages
with the name subject, instead of checking for references. The easy fix
is add something variable to the subject to make it different each time
that FAQ is posted, like, for example,
FAQ 123: Short Description of FAQ %
FAQ 123: Short Description of FAQ ^
FAQ 123: Short Description of FAQ $
Or some other way of making it unique. Yes, it's not a pretty way of
getting around that deficienty in some readers, but if you want to, then
that's what needs to be done afaik.
I wish more user agents would pay better attention to standards.
--
szr
------------------------------
Date: Sat, 12 Jul 2008 19:50:45 -0400
From: John W Kennedy <jwkenne@attglobal.net>
Subject: Re: FAQ 1.12 What's the difference between "perl" and "Perl"?
Message-Id: <48794356$0$5018$607ed4bc@cv.net>
Martijn Lievaart wrote:
> Are you really that thick, or are you pretending to be?
There is no question that he is a plain and simple, mentally ill troll
-- he's filter-proofing himself, which is a sure sign. Just stop responding.
--
John W. Kennedy
"The grand art mastered the thudding hammer of Thor
And the heart of our lord Taliessin determined the war."
-- Charles Williams. "Mount Badon"
------------------------------
Date: Sat, 12 Jul 2008 22:57:57 -0700
From: "Gordon Corbin Etly" <seysig@gmail.com>
Subject: Re: FAQ 1.12 What's the difference between "perl" and "Perl"?
Message-Id: <6dtjr7F4a06jU1@mid.individual.net>
John W Kennedy wrote:
> Martijn Lievaart wrote:
> > Are you really that thick, or are you pretending to be?
> >
> > YOU are quoting Larry out of context. When someone gives that
> > context,
> > you completely ignore it.
I didn't ignore it. What you and others have completely ignored is this:
Why do many people write "TIMTOWTDI", instead of "There is more than one
way to do it"? Maybe it's because it's just more convenient to write it
that way. Maybe it's a personal preference to write it that way. It
saves time when typing.
So why then is it in any way wrong to write "PERL", instead of writing
"Practical extraction and report language"?
None of you have countered this, but instead, I keep seeing the same
excuses, that it is some social issue, or that you consider someone who
writes that to be ignorant or incompetent, or that it was some joke. In
fact, someone using it in the manner I have described is someone who has
read of Larry, who is just writing in a form that *they* prefer, because
they are not a mindless sheep - who are you or I or anyone to dictate
personal preferences?
This forcing of a belief is little more than a "do this and that or you
can't join our club" mentality.
> -- he's filter-proofing himself, which is a sure sign. Just stop
> responding. --
This is untrue. If you filter by /Gordon\s+(?:C(?:.|orbin)?\s+)Etly/,
which covers all the ways I have written my name. If you really wanted
to killfile me, you could of easily done it long ago, so please stop
pushing falsehoods in order to make it appear you're on some moral high
ground.
--
Gordon C. Etly
Email: perl -e "print q{}.reverse(q{moc.liamg@ylte.nodrog})"
------------------------------
Date: Sat, 12 Jul 2008 23:32:05 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: How to get Perl CGI working on Mac OS 10.5?
Message-Id: <g5c7h506md@news4.newsguy.com>
Randal L. Schwartz wrote:
>>>>>> "szr" == szr <szr@szroman.com> writes:
>
> szr> <side question>
> szr> I never understood why that news group wasn't created up the
> szr> 'comp.*' hierarchy and why it was made under 'alt.*', was there
> szr> any particular reason for this?
> szr> </side question>
>
> Not sure what that alt. group is doing there, but
> comp.infosystems.www.servers.unix has always been the apache group to
> me.
Ah I completely forgot about that group, although it's not precisely a
dedicated apache group, believe it's close enough :-)
--
szr
------------------------------
Date: Sun, 13 Jul 2008 04:42:20 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Sun Jul 13 2008
Message-Id: <K3xH2K.17o2@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
AI-MegaHAL-0.07
http://search.cpan.org/~chorny/AI-MegaHAL-0.07/
Perl interface to the MegaHAL natural language conversation simulator.
----
AnyEvent-4.2
http://search.cpan.org/~mlehmann/AnyEvent-4.2/
provide framework for multiple event loops
----
Audio-M4P-0.51
http://search.cpan.org/~billh/Audio-M4P-0.51/
Perl QuickTime / MP4 / iTunes Music Store audio / video file tools
----
CPU-Z80-Assembler-2.00
http://search.cpan.org/~pscust/CPU-Z80-Assembler-2.00/
a Z80 assembler
----
Catalyst-Plugin-Authentication-Credential-HTTP-0.11
http://search.cpan.org/~bobtfish/Catalyst-Plugin-Authentication-Credential-HTTP-0.11/
HTTP Basic and Digest authentication for Catalyst.
----
Clone-0.29
http://search.cpan.org/~rdf/Clone-0.29/
recursively copy Perl datatypes
----
DBIx-IO-1.07
http://search.cpan.org/~rsandberg/DBIx-IO-1.07/
Abstraction layer for database I/O with auto-discovery of data dictionary.
----
DBIx-TableReferences-MSSQL-0.03
http://search.cpan.org/~edwardg/DBIx-TableReferences-MSSQL-0.03/
Perl extension for getting information about declared referential constraints in MS SQL Server 2000 databases.
----
DateTime-0.4303
http://search.cpan.org/~drolsky/DateTime-0.4303/
A date and time object
----
DateTime-Locale-0.41
http://search.cpan.org/~drolsky/DateTime-Locale-0.41/
Localization support for DateTime.pm
----
DateTime-TimeZone-0.78
http://search.cpan.org/~drolsky/DateTime-TimeZone-0.78/
Time zone object base class and factory
----
Devel-NYTProf-1.90_5
http://search.cpan.org/~timb/Devel-NYTProf-1.90_5/
Powerful feature-rich perl source code profiler
----
Domain-PublicSuffix-0.03
http://search.cpan.org/~nmelnick/Domain-PublicSuffix-0.03/
Parse a domain down to root
----
EV-3.431
http://search.cpan.org/~mlehmann/EV-3.431/
perl interface to libev, a high performance full-featured event loop
----
FCGI-Engine-0.05
http://search.cpan.org/~stevan/FCGI-Engine-0.05/
A flexible engine for running FCGI-based applications
----
Forest-0.02
http://search.cpan.org/~stevan/Forest-0.02/
A collection of n-ary tree related modules
----
I18N-Charset-1.394
http://search.cpan.org/~mthurn/I18N-Charset-1.394/
IANA Character Set Registry names and Unicode::MapUTF8 (et al.) conversion scheme names
----
Layout-Manager-0.04
http://search.cpan.org/~gphat/Layout-Manager-0.04/
2D Layout Management
----
LibTracker-Client-0.02
http://search.cpan.org/~gera/LibTracker-Client-0.02/
Perl interfce to libtrackerclient
----
LockFile-Simple-0.207
http://search.cpan.org/~jv/LockFile-Simple-0.207/
simple file locking scheme
----
Net-SNMP-Mixin-Dot1abLldp-0.11
http://search.cpan.org/~gaissmai/Net-SNMP-Mixin-Dot1abLldp-0.11/
mixin class for the Link Layer Discovery Protocol
----
ORLite-0.09
http://search.cpan.org/~adamk/ORLite-0.09/
Extremely light weight SQLite-specific ORM
----
Path-Router-0.01
http://search.cpan.org/~stevan/Path-Router-0.01/
A tool for routing paths
----
Pugs-Compiler-Rule-0.29
http://search.cpan.org/~fglock/Pugs-Compiler-Rule-0.29/
Compiler for Perl 6 regexes
----
Statistics-FisherPitman-0.04
http://search.cpan.org/~rgarton/Statistics-FisherPitman-0.04/
Randomization-based alternative to one-way independent groups ANOVA; unequal variances okay
----
Syntax-Highlight-Engine-Simple-0.0.1
http://search.cpan.org/~jamadam/Syntax-Highlight-Engine-Simple-0.0.1/
Simple, fast and flexible Syntax Highlight Engine
----
Syntax-Highlight-Engine-Simple-HTML-0.0.1
http://search.cpan.org/~jamadam/Syntax-Highlight-Engine-Simple-HTML-0.0.1/
(EXPERIMENTAL)HTML code highlighting class
----
Syntax-Highlight-Engine-Simple-Perl-0.0.1
http://search.cpan.org/~jamadam/Syntax-Highlight-Engine-Simple-Perl-0.0.1/
(EXPERIMENTAL) Perl code highlighting class
----
Sys-Info-0.52_92
http://search.cpan.org/~burak/Sys-Info-0.52_92/
Fetch information from the host system
----
WWW-Alexa-TrafficRank
http://search.cpan.org/~guruperl/WWW-Alexa-TrafficRank/
Query Alexa.com Traffic Rank of website.
----
XML-CompareML-0.2.4
http://search.cpan.org/~shlomif/XML-CompareML-0.2.4/
A processor for the CompareML markup language
----
XML-Compile-0.89
http://search.cpan.org/~markov/XML-Compile-0.89/
Compilation based XML processing
----
XML-Pastor-0.6.0
http://search.cpan.org/~aulusoy/XML-Pastor-0.6.0/
Generate Perl classes with XML bindings starting from a W3C XSD Schema
----
mpp3
http://search.cpan.org/~pfeiffer/mpp3/
----
stockmonkey-2.10
http://search.cpan.org/~jettero/stockmonkey-2.10/
----
v6-0.021
http://search.cpan.org/~fglock/v6-0.021/
An experimental Perl 6 implementation
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: 12 Jul 2008 20:03:11 GMT
From: jt@toerring.de (Jens Thoms Toerring)
Subject: Re: remove previous lines of a log file
Message-Id: <6dsgvvF45borU1@mid.uni-berlin.de>
Jens Thoms Toerring <jt@toerring.de> wrote:
> rajesh <sivarajesh.jarugula@gmail.com> wrote:
> > I need a parser logic in perl. I need to read a log file line by
> > line and search for a keyword. Once the keyword is found in any line,
> > I need to remove the previous two lines and current line. My new log
> > file, should not have these three lines.
> On most systems files are simply a sequence of bytes and you
> can't cut out something from the middle. It's not like a deck
> of cards, where each card is a line in the file, and where
> you can pull out a few cards from the middle. You have to
> copy everything from the old file to a new one (of course ex-
> cept the bits you want to remove) and then replace the old
> file by the new one. So in your case you have to keep three
> lines in memory, writing the oldest one out if the newest
> one does not contain the keyword you were looking for. Only
> if it's in the newest line forget about the three lines and
> copy all the rest of the contents of the old file to the new
> one. Something like this should do:
> #!/usr/bin/perl
> use strict;
> use warnings;
> open my $in, '<', 'log' or die "Can't open log file.\n";
> open my $out, '>', 'log.new' or die "Can't open replacement file.\n";
> my @lines;
> $lines[ 0 ] = <$in>;
> $lines[ 1 ] = <$in>;
> while ( <$in> ) {
> if ( /KEYWORD/ ) {
> while ( <$in> ) {
> print $out $_;
> }
> last;
> }
> print $out shift @lines;
> push @lines, $_;
> }
Sorry, just noticed that this will lose the last two lines
if 'KEYWORD' is never found, so change that to
while ( <$in> ) {
if ( /KEYWORD/ ) {
@lines = ( );
last;
}
print $out shift @lines;
push @lines, $_;
}
if ( @lines ) {
print $out, $_ for @lines;
} else {
while ( <$in> ) {
print $out, $_;
}
}
or something along that line.
> close $out;
> close $in;
> rename 'log.new', 'log';
Regards, Jens
--
\ Jens Thoms Toerring ___ jt@toerring.de
\__________________________ http://toerring.de
------------------------------
Date: 12 Jul 2008 23:23:27 GMT
From: Leon Timmermans <fawaka@gmail.com>
Subject: Re: remove previous lines of a log file
Message-Id: <pan.2008.07.12.23.23.47@gmail.com>
On Sat, 12 Jul 2008 20:03:11 +0000, Jens Thoms Toerring wrote:
>
> if ( @lines ) {
> print $out, $_ for @lines;
> } else {
> while ( <$in> ) {
> print $out, $_;
> }
> }
>
I'd skip those comma's after $out though ;-)
Leon Timmermans
------------------------------
Date: 12 Jul 2008 23:25:36 GMT
From: Leon Timmermans <fawaka@gmail.com>
Subject: Re: remove previous lines of a log file
Message-Id: <pan.2008.07.12.23.25.56@gmail.com>
On Sat, 12 Jul 2008 18:34:53 +0200, Dave B wrote:
> $f=~s/(?:.*\n){2}.*keyword.*\n//g;
>
> should do what you want. (Note that the last line in the file should be
> correctly terminated by a newline).
I think that last issue can be solved by the /m modifier
$f =~ s/ (?:.*\n){2} .* keyword .* $ //xmg;
Leon Timmermans
------------------------------
Date: 13 Jul 2008 01:40:50 GMT
From: jt@toerring.de (Jens Thoms Toerring)
Subject: Re: remove previous lines of a log file
Message-Id: <6dt4p2F49q3kU1@mid.uni-berlin.de>
Leon Timmermans <fawaka@gmail.com> wrote:
> On Sat, 12 Jul 2008 20:03:11 +0000, Jens Thoms Toerring wrote:
> >
> > if ( @lines ) {
> > print $out, $_ for @lines;
> > } else {
> > while ( <$in> ) {
> > print $out, $_;
> > }
> > }
> >
> I'd skip those comma's after $out though ;-)
I guess I also would do so after a bit more of thinking;-)
Regards, Jens
--
\ Jens Thoms Toerring ___ jt@toerring.de
\__________________________ http://toerring.de
------------------------------
Date: Sat, 12 Jul 2008 13:12:05 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: Value of "Programming perl" 1st Ed.?
Message-Id: <mpfnk5x4ag.ln2@goaway.wombat.san-francisco.ca.us>
On 2008-07-12, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>
> I'm sure gnus supports regular expressions.
This particular troll has changed often enough to defeat my first regex
(slrn, not gnus, but same principle), including using his ''cousin's''
name ''accidentally''. The one I have now seems to be working, but I
wouldn't be surprised if he evades it in the future.
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Sat, 12 Jul 2008 13:14:02 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: Value of "Programming perl" 1st Ed.?
Message-Id: <btfnk5xlag.ln2@goaway.wombat.san-francisco.ca.us>
On 2008-07-12, Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
> This particular troll has changed often enough to defeat my first regex
> (slrn, not gnus, but same principle), including using his ''cousin's''
> name ''accidentally''.
Whoops, different troll. Sorry folks. :( This troll's difficulty is
that a suitable regex might kill legitimate posters, so some people
might be reluctant to apply it. At that point one's mental killfile
needs to supplement the NNTP client's capability.
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Sat, 12 Jul 2008 20:02:26 -0700
From: Skyler <sky@shaw.ca>
Subject: Re: Value of "Programming perl" 1st Ed.?
Message-Id: <8feek.15226$uE5.10459@flpi144.ffdc.sbc.com>
Keith Keller wrote:
> On 2008-07-12, Keith Keller
> <kkeller-usenet@wombat.san-francisco.ca.us> wrote:
>> This particular troll has changed often enough to defeat my first
>> regex
>> (slrn, not gnus, but same principle), including using his
>> ''cousin's''
>> name ''accidentally''.
>
> Whoops, different troll. Sorry folks. :( This troll's difficulty is
> that a suitable regex might kill legitimate posters, so some people
> might be reluctant to apply it. At that point one's mental killfile
> needs to supplement the NNTP client's capability.
I haven't change it before. I wont do it again if it's that much of a
problem. I don't put a real one because of spammers. I was just having
fun screwing with Uri. He needed a taste of his own foul medicine.
-sky
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 1715
***************************************
