[23278] in Perl-Users-Digest
Perl-Users Digest, Issue: 5498 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Sep 13 18:05:40 2003
Date: Sat, 13 Sep 2003 15:05:08 -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 Sat, 13 Sep 2003 Volume: 10 Number: 5498
Today's topics:
Re: $SIG{__DIE__} doesn't make sense when using CGI::Ca <johanoberm@gmx.de>
Re: Compress/Zip a String <wwonko@rdwarf.com>
Is the ithreads implementation safe? (David Morel)
Re: Is the ithreads implementation safe? <l0g0m0tion@earthlink.net>
killfiling (was Re: Perl DBMS) (Tad McClellan)
Re: killfiling (was Re: Perl DBMS) <ge0rge@Talk21.com>
Re: killfiling (was Re: Perl DBMS) (Tad McClellan)
Re: Matching { } braces ??? <REMOVEsdnCAPS@comcast.net>
Re: Matching { } braces ??? (Tad McClellan)
Re: Matching { } braces ??? <jwillmore@cyberia.com>
Re: Perl DBMS (Tad McClellan)
Re: Perl DBMS <flavell@mail.cern.ch>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 13 Sep 2003 15:39:42 +0200
From: Jo Oberman <johanoberm@gmx.de>
Subject: Re: $SIG{__DIE__} doesn't make sense when using CGI::Carp
Message-Id: <jd76mvcua2k2i92db7280as6vgjeijqoqv@4ax.com>
>To me this seems alright: the exception is _raised_
>( by calling die()) in Carp.pm, but it is still
>_your_ handler that is called.
>
>Or am I wrong?
Sorry, you are wrong.
I'm reasing the exception in my example. The message should
be something like
ERROR-Message: I'm dying. Please help! at
d:/dev_soft/myDir/Perl/example.pl line 19
>Jo Oberman wrote:
>
>> When running the skript I get the following message (notice the wrong
>> module and line number)
>>
>> Just some text
>> ERROR-Message: I'm dying. Please help! at
>> d:/dev_soft/apache/Perl/lib/CGI/Carp.pm line 301.
>
>To me this seems alright: the exception is _raised_
>( by calling die()) in Carp.pm, but it is still
>_your_ handler that is called.
>
>Or am I wrong?
>
>Amir
>
------------------------------
Date: Sat, 13 Sep 2003 19:07:19 +0000 (UTC)
From: Louis Erickson <wwonko@rdwarf.com>
Subject: Re: Compress/Zip a String
Message-Id: <bjvpt7$r9j$1@holly.rdwarf.com>
"Jurgen Exner <jurgenex@hotmail.com> wrote:
: http://edealseek.com/newsgroup.html wrote:
:> I need to convert a string, an URI/EmailAddress based string into a
:> letter/number only string.
: It appears you are looking for uuencode/uudecode.
Or base64. It's just as clen, and generally smaller.
Either will still expand the string. However, compressing it will almost
certainly produce binary data, and render goal of letters and numbers only
to be moot.
Could this be an XY problem?
--
Louis Erickson - wwonko@rdwarf.com - http://www.rdwarf.com/~wwonko/
Better dead than mellow.
------------------------------
Date: 13 Sep 2003 11:38:46 -0700
From: altalingua@hotmail.com (David Morel)
Subject: Is the ithreads implementation safe?
Message-Id: <60c4a7b1.0309131038.1dd1ae04@posting.google.com>
According to Network Programming with Perl, "the 5.005 thread
implementation has known bugs that can lead to mysterious crashes ...
in fact, the Perl thread documentation warns that multithreading
should not be used in production systems."
What about the newer ithreads implementation? Is it safe? Would you
use it in mission critical systems? Finally, what do you think about
the safety/reliability of the Thread::Pool module?
-- David Morel
------------------------------
Date: Sat, 13 Sep 2003 20:42:48 GMT
From: Christopher Shatto <l0g0m0tion@earthlink.net>
Subject: Re: Is the ithreads implementation safe?
Message-Id: <cjL8b.2309$Aq2.1069@newsread1.news.atl.earthlink.net>
Check the documentation on the 'threads' pragma for details on the 5.8
threads implementation. 5.8 threads are acceptably stable. I
personally have never experienced issues with them on Red Hat Linux,
Windows XP, WinNT, or FreeBSD.
David Morel wrote:
> According to Network Programming with Perl, "the 5.005 thread
> implementation has known bugs that can lead to mysterious crashes ...
> in fact, the Perl thread documentation warns that multithreading
> should not be used in production systems."
>
> What about the newer ithreads implementation? Is it safe? Would you
> use it in mission critical systems? Finally, what do you think about
> the safety/reliability of the Thread::Pool module?
>
> -- David Morel
------------------------------
Date: Sat, 13 Sep 2003 10:18:20 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: killfiling (was Re: Perl DBMS)
Message-Id: <slrnbm6d9s.2jg.tadmc@magna.augustmail.com>
ge0rge <ge0rge@Talk21.com> wrote:
><OT>
But it isn't.
Where else but clpmisc would be appropriate for discussing
the goings-on in clpmisc?
Such "administration" threads are annoying/wasteful, but not off-topic.
> "Alan J. Flavell" <flavell@mail.cern.ch> wrote in message
> news:Pine.LNX.4.53.0309130126160.5502@lxplus002.cern.ch...
>> On Fri, Sep 12, ge0rge inscribed on the eternal scroll:
[snip: about top-posting]
>> Indeed. The advice is to do it not because the FAQ or RFC says you
>> must, but because the body of other serious participants expect it,
>> and when they killfile you for ignoring the social mores of the group,
>> you'll be lucky if one of them bothers to tell you about it.
>
> Well, that would be a bit of an overkill. Don't you think so?
Whether it is "right" or "best" is irrelevant (unless you think
you can change everyone's mind).
What matters in a pragmatic sense is that it happens here.
So if you want the widest readership for articles posted here, it
is worth a bit of effort to avoid stepping on killfile "mines".
Using an upside-down posting style is but one variety of mine.
The Posting Guidelines attempt to steer folks away from
many of the most common varieties...
> Killfiling
> someone because (s)he top post!
I have:
% Jeopardists
Score:: -9998
< 37 addresses so far >
None of them for top-posting once or twice.
All of them people who complain about it once corrected, or
insisted on continuing with reversing time.
>> Did I mention that the best adjunct to participating in usenet is a
>> well-tended killfile?
>
> Whoaa! That's a bit below the belt.
I don't know what you saw there, but I don't see a "blow"
landed anywhere.
Did you see something personal there?
Sounds like merely a description of clpmisc reality to me...
> It was just a bit of harmless banter to
> test the water in this NG.
If you slap a junk yard dog to see if he is mean, you should be
prepared to pay with your hand (or worse). :-)
> BTW, I think the whole idea of a killfile is another OTT response to
How to not be ignored in clpmisc is on-topic for clpmisc.
> Now, time for me to shut up and start lurking awhile in this NG
Perhaps you cannot understand the wide spread use of killfiles
because your experiences are different from the killfiler's
experiences.
Lurking for a few years will help give you insight there. :-)
Most of the frequent-answers are busy folks. That's how they gain
enough expertise to be able to answer questions!
They undoubtedly have a "Perl time" budget and clpmisc is likely
only one of the (less-important) places that that time is spent. They're
busy writing modules, reading mailing lists, etc as well as
donating time here.
When they get in a budget crunch, they can stop reading clpmisc
or they can find a way to spend less time while reading clpmisc.
Many wonderful question-answerers have already chosen the
former approach. :-(
I've had my code corrected here by Larry Wall himself. That won't
be happening anymore. :-( :-(
So, these type of people who _are_ still here, are very likely to
have implemented the later approach, ie. they use heuristics
(scorefiles) to help reduce their workload.
This is a high traffic newsgroup, often 200 posts a day.
Nobody reads all of them, so they must "filter" them somehow.
Whether they do it manually or automatically does not make much
difference, they must be skipping a whole lot of articles either way.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 13 Sep 2003 19:42:35 +0100
From: "ge0rge" <ge0rge@Talk21.com>
Subject: Re: killfiling (was Re: Perl DBMS)
Message-Id: <bjvof2$o0vfa$1@ID-175222.news.uni-berlin.de>
"Tad McClellan" <tadmc@augustmail.com> wrote in message
news:slrnbm6d9s.2jg.tadmc@magna.augustmail.com...
...
> I don't know what you saw there, but I don't see a "blow"
> landed anywhere.
> Did you see something personal there?
> Sounds like merely a description of clpmisc reality to me...
Did you not see him hit me with a feather? ... where's your sense of humour?
Relax, be flippant. Have a sense of irony. Don't take things literally.
(murmuring to myself - bloody hell! what the matter with these yanks? Is
their sense of humour really that different?)
> > It was just a bit of harmless banter to
> > test the water in this NG.
>
> If you slap a junk yard dog to see if he is mean, you should be
> prepared to pay with your hand (or worse). :-)
There you go again - I said banter and you come up with a horror scenario.
...
> Perhaps you cannot understand the wide spread use of killfiles
> because your experiences are different from the killfiler's
> experiences.
> Lurking for a few years will help give you insight there. :-)
Years? what are you, nuts? (Gawd! maybe I shouldn't make such a flippant
remark)
...
> This is a high traffic newsgroup, often 200 posts a day.
> Nobody reads all of them, so they must "filter" them somehow.
> Whether they do it manually or automatically does not make much
> difference, they must be skipping a whole lot of articles either way.
Agree. (at last! Quick -Down to the pub now.)
ge0rge
--
I know you think you thought you knew what you thought I said,
but I'm not sure you understood what you thought I meant.
------------------------------
Date: Sat, 13 Sep 2003 15:19:21 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: killfiling (was Re: Perl DBMS)
Message-Id: <slrnbm6uu8.33o.tadmc@magna.augustmail.com>
ge0rge <ge0rge@Talk21.com> wrote:
> "Tad McClellan" <tadmc@augustmail.com> wrote in message
> news:slrnbm6d9s.2jg.tadmc@magna.augustmail.com...
>> Did you see something personal there?
> Relax, be flippant. Have a sense of irony. Don't take things literally.
I missed the smiley you put in to indicate that it wasn't
to be taken too seriously...
> (murmuring to myself - bloody hell! what the matter with these yanks? Is
> their sense of humour really that different?)
No, it's just that we don't _have_ a sense of humour.
We have a sense of humor.
We're saving some vowels for a "rainy day".
>> Perhaps you cannot understand the wide spread use of killfiles
>> because your experiences are different from the killfiler's
>> experiences.
>> Lurking for a few years will help give you insight there. :-)
>
> Years? what are you, nuts?
(it appears my "perhaps" might have been a lucky guess then...)
No, that was my estimate of how long it takes to get fed up
enough to resort to using a scorefile. We're not naturally
exclusionary, we became that way over (a long, hopefully) time.
I lasted about 3 or 4 years without one.
Then I used only general-purpose heuristics for a while
(eg. Subject: Perl question), and consciously avoided
making entries for individual addresses.
Then I started using individual addresses, and reviewing/cleaning
them out every 3 months.
Then I stopped spending (yet more) time cleaning them out.
Nowadays, entries go in, but they don't come out, and there
is _still_ more visible articles than I care to read, ie. I still
have manual filtering to perform.
( And somewhere in there, I also became a "domainist". )
I'm sure I've thrown out some babies with the bathwater, but
the alternative is to just leave the newsgroup altogether.
With a carefully tuned killfile, I'll still be answering _some_
questions, rather than zero answers with the alternative.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 13 Sep 2003 09:12:12 -0500
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: Matching { } braces ???
Message-Id: <Xns93F567EE63746sdn.comcast@206.127.4.25>
Bob Walton <bwalton@rochester.rr.com> wrote in
news:3F62A4D4.30607@rochester.rr.com:
> ... There is a saying that
> "only Perl can parse Perl".
Actually, the saying is "Only perl can parse Perl." Subtle difference.
--
Eric
$_ = reverse sort $ /. r , qw p ekca lre uJ reh
ts p , map $ _. $ " , qw e p h tona e and print
------------------------------
Date: Sat, 13 Sep 2003 09:28:07 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Matching { } braces ???
Message-Id: <slrnbm6abn.2jg.tadmc@magna.augustmail.com>
James Willmore <jwillmore@cyberia.com> wrote:
> The number one error that crops up in programming is the dreded syntax
> error.
In the universe of all potential programmer's errors, a
"syntax error" is the *most welcome* of all possible errors!
Because they are the easiest to find. So easy that even a
machine can find them.
It is those pesky "semantic errors" that are dreaded.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 13 Sep 2003 17:00:13 GMT
From: James Willmore <jwillmore@cyberia.com>
Subject: Re: Matching { } braces ???
Message-Id: <20030913130022.49ac8514.jwillmore@cyberia.com>
On Sat, 13 Sep 2003 09:28:07 -0500
tadmc@augustmail.com (Tad McClellan) wrote:
> James Willmore <jwillmore@cyberia.com> wrote:
>
> > The number one error that crops up in programming is the dreded
> > syntax error.
>
>
> In the universe of all potential programmer's errors, a
> "syntax error" is the *most welcome* of all possible errors!
>
> Because they are the easiest to find. So easy that even a
> machine can find them.
>
> It is those pesky "semantic errors" that are dreaded.
True. I sit corrected - too lazy to stand ;)
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
It wasn't that she had a rose in her teeth, exactly. It was more
like the rose and the teeth were in the same glass.
------------------------------
Date: Sat, 13 Sep 2003 09:35:22 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Perl DBMS
Message-Id: <slrnbm6apa.2jg.tadmc@magna.augustmail.com>
Dave <dave334234@inter.com> wrote:
> "Eric Bohlman" <ebohlman@earthlink.net> wrote in message
> news:Xns93F4CDEB8C228ebohlmanomsdevcom@130.133.1.4...
>> "Dave" <dave334234@inter.com> wrote in
>> news:8as8b.1005$WI3.13044@newsfep4-glfd.server.ntli.net:
>>
>> > #!/usr/bin/perl
>>
>> Name the two things missing here...
>
> I guess u mean -w ??
The warnings pragma is better than the command line switch variety.
The two things are:
use strict;
use warnings;
Have you seen the Posting Guidelines that are posted here frequently?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Sat, 13 Sep 2003 19:11:48 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: Perl DBMS
Message-Id: <Pine.LNX.4.53.0309131850380.4388@lxplus078.cern.ch>
On Sat, Sep 13, ge0rge inscribed on the eternal scroll:
> > and when they killfile you for ignoring the social mores of the group,
> > you'll be lucky if one of them bothers to tell you about it.
>
> Well, that would be a bit of an overkill. Don't you think so? Killfiling
> someone because (s)he top post!
Have another read of what you quoted:
| killfile you for ignoring the social mores of the group
TOFU-posting is just one of the symptoms. Those who've been here a
while know that it's highly correlated with several other symptoms of
advanced cluelessness. Almost all of which could be avoided by first
becoming aware of the accepted customs and practices on technical
big-8 usenet newsgroups in general, and on this specific newsgroup in
particular (actually there's very little difference between the
general and the specific, aside from a few Perl-related differences).
> Can't understand why people (meaning us all, I guess) are so accommodating
> with MS and are prepared to make excuses or go through all sort of
> contortions to work with their software when clearly it is a stupid idea to
> place the cursor at the top.
I don't agree. Most MS software that's meant to get anywhere close to
the Internet is rubbish for many different reasons, and I've no
intention of "accommodating to" its misbehaviour, but putting the
cursor in the right place for starting to snip quotage isn't one of
them.
> > Did I mention that the best adjunct to participating in usenet is a
> > well-tended killfile?
>
> Whoaa! That's a bit below the belt.
If you take it in that way, then maybe a little self-examination is in
order. If I said the same to e.g Tad I'm sure he wouldn't feel I was
throwing the punch at him, but rather he would probably agree with me
(well, he uses scoring, which is a more sophisticated version of the
general idea).
> BTW, I think the whole idea of a killfile is another OTT response to
> something not worth a second thought...
You can think what you like about it, but when you've been on usenet
for a few years you'll wonder how you ever got along without one.
> but then again there's no accounting for what people feel passionate
> about.
You still don't get it. If there was any passion involved, you'd
already be in the killfile - without knowing it.
--
Procrastination gives you something to look forward
to putting off tomorrow. -spotted on ahbou
------------------------------
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.
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 5498
***************************************
