[31887] in Perl-Users-Digest
Perl-Users Digest, Issue: 3150 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Sep 28 06:09:24 2010
Date: Tue, 28 Sep 2010 03:09:10 -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 Tue, 28 Sep 2010 Volume: 11 Number: 3150
Today's topics:
Re: Claimed to be an "old hack" <ben@morrow.me.uk>
Re: Is $A = $B = n; valid? <uri@StemSystems.com>
Re: Is $A = $B = n; valid? <sherm.pendley@gmail.com>
Re: Is $A = $B = n; valid? <uri@StemSystems.com>
Re: Is $A = $B = n; valid? <mvdwege@mail.com>
Re: Is $A = $B = n; valid? <bugbear@trim_papermule.co.uk_trim>
Re: Is $A = $B = n; valid? <rvtol+usenet@xs4all.nl>
Re: Long script "just stops" sometime <ben@morrow.me.uk>
Re: Long script "just stops" sometime <whynot@pozharski.name>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: toy list processing problem: collect similar terms <usenet-nospam@seebs.net>
Re: toy list processing problem: collect similar terms <john@castleamber.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 28 Sep 2010 09:51:07 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Claimed to be an "old hack"
Message-Id: <rsm8n7-6n22.ln1@osiris.mauzo.dyndns.org>
Quoth Ilya Zakharevich <nospam-abuse@ilyaz.org>:
> On 2010-09-28, Ben Morrow <ben@morrow.me.uk> wrote:
> >
> > Quoth cpolish@nonesuch.com:
> >> {(!($^O=~/^[M]*$32/i)&&($0=~s!^.*/!!))||($0=~s!.*\\!!)}
>
> > I almost certainly doesn't do what it's supposed to do :). That '*$32'
> > ought to read '.*32$'.
>
> Just make sure that $32 eq '.*32$'. ;-) But `$1 means \1'-fix (if
> whereever was one - do not remember offhand) may intervene...
>
> > Making that correction, we have an expression of
> > the form
> >
> > (A && B) || C
> >
> > which is a nasty shorthand for
> >
> > if (A) {
> > B
> > }
> > else {
> > C
> > }
>
> No, it is not.
I know it's not *equivalent*. But, in this case, that *is* how it's
being used. It's a very usual way of doing a compact if-then-else in
shell, which is probably where it comes from.
Ben
------------------------------
Date: Tue, 28 Sep 2010 01:05:04 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <87r5gefofz.fsf@quad.sysarch.com>
>>>>> "TM" == Tad McClellan <tadmc@seesig.invalid> writes:
TM> Uri Guttman <uri@StemSystems.com> wrote:
>>>>>>> "TM" == Tad McClellan <tadmc@seesig.invalid> writes:
>>
TM> Pigs can fly.
>>
TM> The syntax of that is perfectly fine.
>>
TM> Its semantics are certainly questionable (ie. wrong).
>>
>> not according to pink floyd! :)
TM> Those wankers won't even let you have any pudding until
TM> after you've finished your meat.
it all depends on your definitions of pudding and meat. what about a
beef pudding?
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 28 Sep 2010 01:59:45 -0400
From: Sherm Pendley <sherm.pendley@gmail.com>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <m21v8exvam.fsf@sherm.shermpendley.com>
"Uri Guttman" <uri@StemSystems.com> writes:
>>>>>> "JLi" == Joey@still Learning invalid <Joey@still_Learning.invalid> writes:
>
> JLi> Tad McClellan wrote:
> >> Joey@still_Learning.invalid <Joey@still_Learning.invalid> wrote:
> >>
> >>> Is the syntax $A = $B = $C = number acceptable?
> >>
> >>
> >> It is awfully rude of you to ask people when a machine could be asked
> >> instead.
> >>
> >> perl -ce '$A = $B = $C = 42'
> >>
> >> -e syntax OK
>
> JLi> Thanks, Tad.
>
> JLi> Sorry for your loss.
>
> your loss as tad will likely not help you again.
Read Tad's signature please - I don't think Joey was being snarky.
sherm--
--
Sherm Pendley
<http://camelbones.sourceforge.net>
Cocoa Developer
------------------------------
Date: Tue, 28 Sep 2010 02:17:08 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <87fwwufl3v.fsf@quad.sysarch.com>
>>>>> "SP" == Sherm Pendley <sherm.pendley@gmail.com> writes:
SP> "Uri Guttman" <uri@StemSystems.com> writes:
>>>>>>> "JLi" == Joey@still Learning invalid <Joey@still_Learning.invalid> writes:
>>
JLi> Tad McClellan wrote:
>> >> Joey@still_Learning.invalid <Joey@still_Learning.invalid> wrote:
>> >>
>> >>> Is the syntax $A = $B = $C = number acceptable?
>> >>
>> >>
>> >> It is awfully rude of you to ask people when a machine could be asked
>> >> instead.
>> >>
>> >> perl -ce '$A = $B = $C = 42'
>> >>
>> >> -e syntax OK
>>
JLi> Thanks, Tad.
>>
JLi> Sorry for your loss.
>>
>> your loss as tad will likely not help you again.
SP> Read Tad's signature please - I don't think Joey was being snarky.
yeah my bad. i spoke to tad the other day about that. a distant cousin.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 28 Sep 2010 06:17:58 +0200
From: Mart van de Wege <mvdwege@mail.com>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <86sk0uo615.fsf@gareth.avalon.lan>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth Mart van de Wege <mvdwege@mail.com>:
>> "Joey@still_Learning.invalid" <Joey@still_Learning.invalid> writes:
>>
>> > Is the syntax $A = $B = $C = number acceptable?
>>
>> Depends on what you want to do; it *would* assign 'number' to all three
>> variables.
>>
>> Can't say I like the construct though. It looks awfully hacky, IMO.
>
> Explain? It's a standard construction in C-derived languages, and makes
> perfect sense once you realise assignment is just an operator like any
> other with a well-defined return value (and useful side-effects, of
> course).
>
I know it makes sense. In my eyes, although slightly redundant, I think
separate assignments look clearer.
>
> Furthermore, in Perl (but not in C), assignment returns the LHS as an
> lvalue, leading to standard idioms like
>
> (my $y = $x) =~ s/foo/bar/;
>
This doesn't grate on my nerves as much; probably because, as you say,
it's standard idiom.
Mart
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
------------------------------
Date: Tue, 28 Sep 2010 09:01:50 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <EK2dnc7-N7VzPTzRnZ2dnUVZ8oudnZ2d@brightview.co.uk>
Ben Morrow wrote:
> Quoth "Joey@still_Learning.invalid" <Joey@still_Learning.invalid>:
>> Is the syntax $A = $B = $C = number acceptable?
>
> What happened when you tried it?
The trouble with trying things is you don't know
if the behaviour you observe is part of the defined
behaviour, or merely a quirk of the implementation.
It is "trying things" and using what works that led
to many Mac programmers creating software that failed
when Apple change non-documented parts of the OS.
the should have worked from the spec, not the implementation,
at least as far as possible.
IMHO the OP is quite correct to ask his question
(I find that while pretty much everything in Perl
*is* documented, finding the right part of the
documentation is hard, and I've been using Perl
for a few years now)
BugBear
------------------------------
Date: Tue, 28 Sep 2010 11:48:41 +0200
From: "Dr.Ruud" <rvtol+usenet@xs4all.nl>
Subject: Re: Is $A = $B = n; valid?
Message-Id: <4ca1b9f9$0$41112$e4fe514c@news.xs4all.nl>
On 2010-09-28 00:11, Joey@still_Learning.invalid wrote:
> Is the syntax $A = $B = $C = number acceptable?
I would not use capital letters for variable names, but further it looks
ok to me.
#!/usr/bin/perl -w
use strict;
sub number { 42 }
my $foo = my $bar = my $baz = number;
__END__
--
Ruud
------------------------------
Date: Tue, 28 Sep 2010 09:47:47 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Long script "just stops" sometime
Message-Id: <jmm8n7-6n22.ln1@osiris.mauzo.dyndns.org>
Quoth Xho Jingleheimerschmidt <xhoster@gmail.com>:
> Ben Morrow wrote:
> > Quoth Xho Jingleheimerschmidt <xhoster@gmail.com>:
> >> Peter J. Holzer wrote:
> >>
> >> Unfortunately, if you use strace "-p" option to attach to an
> >> already-running process, if often doesn't show you what call the process
> >> was waiting on at the time of the attachment. You would have to start
> >> stracing the process from the beginning, which is inconvenient if the
> >> situation at question only happens occasionally.
> >
> > You can find out what call the process is currently blocking in with ps.
>
> Well, maybe *you* can. I've never been able to.
Really?
~% uname
FreeBSD
~% perl -MPOSIX=pause -epause &
[3] 68357
~% ps -lp 68357
UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
1001 68357 14199 0 61 0 5204 3160 pause S 3 0:00.06 perl -MPOSI
~%
~$ uname
Linux
~$ perl -MPOSIX=pause -epause &
[1] 10335
~$ ps -lp 10335
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
0 S 1051 10335 10321 0 80 0 - 5759 pause pts/1 00:00:00 perl
~$
It only tells you *which* syscall, of course, not what arguments it was
called with, but that's something.
Ben
------------------------------
Date: Tue, 28 Sep 2010 10:26:21 +0300
From: Eric Pozharski <whynot@pozharski.name>
Subject: Re: Long script "just stops" sometime
Message-Id: <slrnia364s.b4e.whynot@orphan.zombinet>
with <slrnia0hkn.set.whynot@orphan.zombinet> Eric Pozharski wrote:
*SKIP*
> I've just checked (linux, 2.6.30, Debian). Neither '-n
> /boot/System.map-2.6.30*' nor '-n /proc/*/wchan' helps 'ps' to find
> syscall. 'ps' fails with its default routine either. Thus the output
> for 'WCHAN' column is always either '-' or '?'. I remember, it was
> there. Now it's missing.
I've checked more thoroughly, all 'wchan' files (there're
'/proc/*/task/*/wchan' too) are always '0'. BTW, they don't have
trailing newline either. R.I.P.
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Tue, 28 Sep 2010 02:09:13 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <C_WdnVreh80ECTzRnZ2dnUVZ5oOdnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: 28 Sep 2010 04:18:38 GMT
From: Seebs <usenet-nospam@seebs.net>
Subject: Re: toy list processing problem: collect similar terms
Message-Id: <slrnia2r4u.2705.usenet-nospam@guild.seebs.net>
On 2010-09-28, John Bokma <john@castleamber.com> wrote:
> Seebs <usenet-nospam@seebs.net> writes:
>> On 2010-09-26, J?rgen Exner <jurgenex@hotmail.com> wrote:
>>> It was livibetter who without any motivation or reasoning posted Python
>>> code in CLPM.
>> Not exactly; he posted it in a crossposted thread, which happened to include
>> CLPM and other groups, including comp.lang.python.
>> It is quite possible that he didn't know about the crossposting.
> Oh, he does. It has been Xah's game for years.
But did "livibetter" know about it? I wasn't defending Xah, who is indeed
at the very least clueless and disruptive. But I was sort of defending
the poster who was accused of posting Python code in CLPM, because that
poster may not have understood the game.
-s
--
Copyright 2010, all wrongs reversed. Peter Seebach / usenet-nospam@seebs.net
http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures
http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated!
I am not speaking for my employer, although they do rent some of my opinions.
------------------------------
Date: Mon, 27 Sep 2010 23:34:22 -0500
From: John Bokma <john@castleamber.com>
Subject: Re: toy list processing problem: collect similar terms
Message-Id: <874odajxkh.fsf@castleamber.com>
Seebs <usenet-nospam@seebs.net> writes:
fup set to poster
> On 2010-09-28, John Bokma <john@castleamber.com> wrote:
>> Seebs <usenet-nospam@seebs.net> writes:
>>> On 2010-09-26, J?rgen Exner <jurgenex@hotmail.com> wrote:
>>>> It was livibetter who without any motivation or reasoning posted Python
>>>> code in CLPM.
>
>>> Not exactly; he posted it in a crossposted thread, which happened to include
>>> CLPM and other groups, including comp.lang.python.
>
>>> It is quite possible that he didn't know about the crossposting.
>
>> Oh, he does. It has been Xah's game for years.
>
> But did "livibetter" know about it? I wasn't defending Xah, who is indeed
> at the very least clueless and disruptive.
Heh, he's not clueless, the problem is that he knows exactly what he's
doing. And like most spammers, very hard to get rid off.
> But I was sort of defending
> the poster who was accused of posting Python code in CLPM, because that
> poster may not have understood the game.
Ah, clear. Well, the problem is somewhat also in CLPM where people
somehow have to reply to messages like this :-(. And I am sure Xah
laughes his ass off each time it happens.
--
John Bokma j3b
Blog: http://johnbokma.com/ Facebook: http://www.facebook.com/j.j.j.bokma
Freelance Perl & Python Development: http://castleamber.com/
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 3150
***************************************
