[32097] in Perl-Users-Digest
Perl-Users Digest, Issue: 3361 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 22 09:09:25 2011
Date: Fri, 22 Apr 2011 06: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 Fri, 22 Apr 2011 Volume: 11 Number: 3361
Today's topics:
Re: FAQ 4.44 How do I test whether two arrays or hashes <zjsmallz@os2world.net>
Re: grabbing a facebook group <Uno@example.invalid>
Re: grabbing a facebook group <tadmc@seesig.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Web Scraping Proxy <*@eli.users.panix.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 22 Apr 2011 05:09:44 -0500
From: "John Small" <zjsmallz@os2world.net>
Subject: Re: FAQ 4.44 How do I test whether two arrays or hashes are equal?
Message-Id: <4rkzjBzzMnpe-pn2-Wu02Qm4Torrp@x.y.z>
On Thu, 21 Apr 2011 12:36:25 UTC, Tad McClellan <tadmc@seesig.invalid>
wrote:
> John Small <zjsmallz@os2world.net> wrote:
> > On Wed, 20 Apr 2011 10:00:01 UTC, PerlFAQ Server
> ><brian@theperlreview.com> wrote:
> >
> >> 4.44: How do I test whether two arrays or hashes are equal?
> >
> > I am new to Perl and, faced with comparing arrays, I came up with:
> >
> > if ("@array1" eq "@array2") ...
> >
> > This seems to work for me. But in light of this FAQ posting I have to
> > wonder:
> > 1) Are there flaws in the code above?
>
>
> Most certainly.
>
> It says that these 2 arrays are equal:
>
> my @array1 = ('john small', 'john', 'small');
> my @array2 = ('john', 'small', 'john small');
>
> so are these 2, which don't even have the same number of elements:
>
> my @array1 = ('a b c');
> my @array2 = ('a', 'b', 'c');
>
>
> > 2) Are there advanatges to the FAQ code below?
>
>
> It gives the Right Answer, which is a big advantage :-)
Thanks. I can see now how my "@array1" eq "@array2" would not work
correctly all the time and how the FAQ code is a more generally
reliable way to compare arrays.
But all the elements in the arrays being compared in this particular
program are all single "words". For this situation "@array1" eq
"@array2" does seem to work. Is there any reason to think "@array1" eq
"@array2" would not work under these conditions?
--
John Small
------------------------------
Date: Fri, 22 Apr 2011 01:48:07 -0600
From: Uno <Uno@example.invalid>
Subject: Re: grabbing a facebook group
Message-Id: <91cq5oFsvvU1@mid.individual.net>
On 04/21/2011 08:01 PM, Uri Guttman wrote:
> please don't let the keyboard smack you on the way out.
>
> you have been one of the dumbest posters here in a very long time. and
> that includes quite a few people. you still don't even realize that perl
> was never the problem and the space was the problem. until you get that,
> you will never learn more coding.
>
> uri
So, Uri, what do you think of your contribution to my thread:
> $ perl client9.pl
Path: uni-berlin.de!fu-berlin.de!news.albasani.net!.POSTED!not-for-mail
From: "Uri Guttman" <uri@StemSystems.com>
Newsgroups: comp.lang.perl.misc
Subject: Re: grabbing a facebook group
Date: Mon, 18 Apr 2011 23:38:38 -0400
Organization: albasani.net
Lines: 31
Message-ID: <878vv67vwh.fsf@quad.sysarch.com>
References: <90pnbtFgimU1@mid.individual.net>
<D6ydnWlowJWmnTXQnZ2dnUVZ7vCdnZ2d@brightview.co.uk>
<90stu4FhtlU1@mid.individual.net> <86wriur3nn.fsf@gareth.avalon.lan>
<90t5alF6n5U1@mid.individual.net> <86sjtiqnlc.fsf@gareth.avalon.lan>
<90uqnlF53iU1@mid.individual.net>
<slrniqkpkq.98r.tadmc@tadbox.sbcglobal.net>
<914ao7FjtqU1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.albasani.net
uZg0sRTSVwhvfUpqpzaTQdNP80uin284aU4nyrr1DF0x7r6pFrCUQk6CJ+/JkiwVCkeHmFpv+mBczedlVlN/WyOtmgzq7Wp4wsjFXpmilOyefM1y+TaSJkL39WtD/Uzi
NNTP-Posting-Date: Tue, 19 Apr 2011 03:38:38 +0000 (UTC)
Injection-Info: news.albasani.net;
logging-data="BXlaDux2oKTIOy4DaesmMBB866os9PkmSXwAxQLfBw+cvVYgfrJknig3SYnPDPM32ikBgBYrpK++JrLF5ErEMIOZc402UPPAnL7/n20s7vIWD+XStxHujR6k2gPWRpkq";
mail-complaints-to="abuse@albasani.net"
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
Cancel-Lock: sha1:2y5i7SQqB1OsWnzJw2eECT2ZuQk=
sha1:gLSUanaDV16/hkxurRPXaM6Xnw4=
Xref: uni-berlin.de comp.lang.perl.misc:663114
>>>>> "U" == Uno <Uno@example.invalid> writes:
U> $ cat fb1.pl
U> #!/usr/bin/perl
U> use strict;
U> Are you stoned? Tad, if either being correct or promoting the
U> discussion in c.l.p.misc is part of your job description, I think you
U> need to resign.
wow. you win the prize for the thickest head i have seen here since
moronzilla graced us with its smell.
do you even understand how unix run script programs? or what the #!
means? or where it MUST be in the file to work? read the man pages on
exec and its cousins (the unix system calls, not perl's). then come back
on your knees and beg for forgiveness. whatever babbling you may do, it
is obvious that the bug you had there IS NOT A PERL PROBLEM. perl never
even gets to see that file. so how could it be a perl problem?
sorry, i used logic on you. i won't make that mistake again as it
doesn't penetrate.
wow.
uri
--
Uri Guttman ------ uri@stemsystems.com --------
http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support
------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com
---------
Path: uni-berlin.de!fu-berlin.de!news.albasani.net!.POSTED!not-for-mail
From: "Uri Guttman" <uri@StemSystems.com>
Newsgroups: comp.lang.perl.misc
Subject: Re: grabbing a facebook group
Date: Tue, 19 Apr 2011 02:36:30 -0400
Organization: albasani.net
Lines: 43
Message-ID: <87liz6693l.fsf@quad.sysarch.com>
References: <90pnbtFgimU1@mid.individual.net>
<D6ydnWlowJWmnTXQnZ2dnUVZ7vCdnZ2d@brightview.co.uk>
<90stu4FhtlU1@mid.individual.net> <86wriur3nn.fsf@gareth.avalon.lan>
<90t5alF6n5U1@mid.individual.net> <86sjtiqnlc.fsf@gareth.avalon.lan>
<90uqnlF53iU1@mid.individual.net>
<slrniqkpkq.98r.tadmc@tadbox.sbcglobal.net>
<914ao7FjtqU1@mid.individual.net> <878vv67vwh.fsf@quad.sysarch.com>
<86k4eqrfin.fsf@gareth.avalon.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.albasani.net
q22I5R9I2VPtQ55YlenH5PoaH4qtwNJ8eYcqTCNCy7ZJMo2bNpivpsnrweTg5lUQ8/FEUjzeJwpKwISJm3Rq/7eoyXDfi61qxe7gxVMSqsdQihMngEqsCmg/CD/L5T5o
NNTP-Posting-Date: Tue, 19 Apr 2011 06:36:30 +0000 (UTC)
Injection-Info: news.albasani.net;
logging-data="fsFzPt3DVHDIptAP9ketVVfsUGel6Y9+gEHe8x0V0V/yIoTrIPOp4CEAMyjzDgJIGqy5izSoXzmpbxlJoBLH63PSTYHRkd6VKzhUcm+EFKkxiRZp/l1NWz2kfCBWkebL";
mail-complaints-to="abuse@albasani.net"
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
Cancel-Lock: sha1:u3mZO2o8AfEkaeEmSRtUBKhJZvM=
sha1:VQKwEGzDQxrGRnKIwKeG+gDjYZg=
Xref: uni-berlin.de comp.lang.perl.misc:663119
>>>>> "MvdW" == Mart van de Wege <mvdwege@mail.com> writes:
MvdW> "Uri Guttman" <uri@StemSystems.com> writes:
>>>>>>> "U" == Uno <Uno@example.invalid> writes:
>>
U> $ cat fb1.pl
U> #!/usr/bin/perl
U> use strict;
>>
U> Are you stoned? Tad, if either being correct or promoting the
U> discussion in c.l.p.misc is part of your job description, I think you
U> need to resign.
>>
>> wow. you win the prize for the thickest head i have seen here since
>> moronzilla graced us with its smell.
>>
>> do you even understand how unix run script programs? or what the #!
>> means?
MvdW> No he doesn't. Not even after he had it explained to him in what I
MvdW> *think* was fairly lucid English.
it was. shebang is a dud to him! :)
what i find amusing was in my days when i ported unix (bsd 4.1) i had
delved into the very kernel exec code that looked at the first two bytes
of a file for #! and then did the script exec instead of a binary
one. the concept of first two bytes seems very lost here and spaces do
count!
MvdW> I say, plonk the guy. He is a cargo cult coder who expends *no*
effort
MvdW> in understanding what he is copy/pasting, which means that it
requires
MvdW> double the effort to make him understand. It's not worth it.
i don't plonk in general but i can ignore him easily. i do like to read
idiotic posts for the amusement value.
uri
--
Uri Guttman ------ uri@stemsystems.com --------
http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support
------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com
---------
Path: uni-berlin.de!fu-berlin.de!news.albasani.net!.POSTED!not-for-mail
From: "Uri Guttman" <uri@StemSystems.com>
Newsgroups: comp.lang.perl.misc
Subject: Re: grabbing a facebook group
Date: Tue, 19 Apr 2011 03:17:53 -0400
Organization: albasani.net
Lines: 66
Message-ID: <87fwpe676m.fsf@quad.sysarch.com>
References: <90pnbtFgimU1@mid.individual.net>
<D6ydnWlowJWmnTXQnZ2dnUVZ7vCdnZ2d@brightview.co.uk>
<90stu4FhtlU1@mid.individual.net> <86wriur3nn.fsf@gareth.avalon.lan>
<90t5alF6n5U1@mid.individual.net> <86sjtiqnlc.fsf@gareth.avalon.lan>
<90uqnlF53iU1@mid.individual.net>
<slrniqkpkq.98r.tadmc@tadbox.sbcglobal.net>
<914ao7FjtqU1@mid.individual.net> <878vv67vwh.fsf@quad.sysarch.com>
<86k4eqrfin.fsf@gareth.avalon.lan> <87liz6693l.fsf@quad.sysarch.com>
<914q0kFmm2U1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.albasani.net
ilxOwvPEUYlK1yIOqA/Ua0Nsq5pOk4nCThFAYCIngqlR4S25ZD3AkingtzU64Vy7tZ+uCJXfhMxp59bJCcJlSg==
NNTP-Posting-Date: Tue, 19 Apr 2011 07:17:53 +0000 (UTC)
Injection-Info: news.albasani.net;
logging-data="IPTyUjpf9ePZTPg0gGsvwH00+JV5VHtLF1OG+ym9z2xxC6rAXa2CxwAgeoPcH2lB57K60rVkFNog5sMdTBeJPpjK3SKsumMhWldrdUsUusSXhw94bdboKA+85w8abVVm";
mail-complaints-to="abuse@albasani.net"
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
Cancel-Lock: sha1:RuozO3NwXZQPlE/2mSHrGf9Iu2c=
sha1:UqT9YWBPX6Y3El9R5poNk2IsxY0=
Xref: uni-berlin.de comp.lang.perl.misc:663122
>>>>> "U" == Uno <Uno@example.invalid> writes:
U> On 04/19/2011 12:36 AM, Uri Guttman wrote:
>>>>>>> "MvdW" == Mart van de Wege<mvdwege@mail.com> writes:
>>
MvdW> "Uri Guttman"<uri@StemSystems.com> writes:
>> >>>>>>> "U" == Uno<Uno@example.invalid> writes:
>> >>
U> $ cat fb1.pl
U> #!/usr/bin/perl
U> use strict;
>> >>
U> Are you stoned? Tad, if either being correct or promoting the
U> discussion in c.l.p.misc is part of your job description, I think you
U> need to resign.
>> >>
>> >> wow. you win the prize for the thickest head i have seen here
since
>> >> moronzilla graced us with its smell.
>> >>
>> >> do you even understand how unix run script programs? or what
the #!
>> >> means?
>>
MvdW> No he doesn't. Not even after he had it explained to him in what I
MvdW> *think* was fairly lucid English.
>>
>> it was. shebang is a dud to him! :)
>>
>> what i find amusing was in my days when i ported unix (bsd 4.1) i had
>> delved into the very kernel exec code that looked at the first two
bytes
>> of a file for #! and then did the script exec instead of a binary
>> one. the concept of first two bytes seems very lost here and spaces do
>> count!
>>
MvdW> I say, plonk the guy. He is a cargo cult coder who expends *no*
effort
MvdW> in understanding what he is copy/pasting, which means that it
requires
MvdW> double the effort to make him understand. It's not worth it.
>>
>> i don't plonk in general but i can ignore him easily. i do like to
read
>> idiotic posts for the amusement value.
>>
>> uri
>>
U> So you came on to my thread with multiplicity to tell me that you're
U> ignoring me?
i do it as a warning to others that you are a doofus. and that is
putting it mildly.
U> You are the smallest of creatures in the open source movement,
U> because I think you're a con man.
wow, you claim you think. i disagree. your turn to prove you
think. think hard about that. oops. that must hurt you a lot. don't
think so hard then, it is more your style.
as for perl vs shebang, that should be put on thedailywtf.com. i am sure
it would be accepted and shoot to the top of the charts. one the the
dumbest comments on perl vs shell vs shebang i have ever seen.
uri
--
Uri Guttman ------ uri@stemsystems.com --------
http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support
------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com
---------
Path: uni-berlin.de!fu-berlin.de!news.albasani.net!.POSTED!not-for-mail
From: "Uri Guttman" <uri@StemSystems.com>
Newsgroups: comp.lang.perl.misc
Subject: Re: grabbing a facebook group
Date: Thu, 21 Apr 2011 22:01:37 -0400
Organization: albasani.net
Lines: 38
Message-ID: <87pqofdoxq.fsf@quad.sysarch.com>
References: <90pnbtFgimU1@mid.individual.net>
<D6ydnWlowJWmnTXQnZ2dnUVZ7vCdnZ2d@brightview.co.uk>
<90stu4FhtlU1@mid.individual.net> <86wriur3nn.fsf@gareth.avalon.lan>
<90t5alF6n5U1@mid.individual.net> <86sjtiqnlc.fsf@gareth.avalon.lan>
<90uqnlF53iU1@mid.individual.net>
<slrniqkpkq.98r.tadmc@tadbox.sbcglobal.net>
<914ao7FjtqU1@mid.individual.net>
<m2ipuani21.fsf@sherm.shermpendley.com> <91c0qbFv83U1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.albasani.net
IEiG4ZD5D1fen/DtU727lDASsZVbYWJPKvbkm2tIGbpFP+eg5Mb0T3ddQkechxReZdQQF2d7N/3Q+AFjY43OoKikfbmwKplnd/HpF2zmSJTyudG3D6UUaeOZnk0a+eYh
NNTP-Posting-Date: Fri, 22 Apr 2011 02:01:37 +0000 (UTC)
Injection-Info: news.albasani.net;
logging-data="yC1lf9HNL7I7aOx3/yZy7nDDrv2CnF6HgxB4Rr3dVE65+0YewJvcFryD8R2zndCFMvaVLmD2cXuSgkl1U/HZK9dTmAdDW9Haerzrr2r9s22BTj9MgHqE+vqVPt+ge5IH";
mail-complaints-to="abuse@albasani.net"
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
Cancel-Lock: sha1:fq922jwB0mPAS7GWW8EZZdBPCWE=
sha1:PC1K7ygBd8TK7vtsGdKftHcYg9U=
Xref: uni-berlin.de comp.lang.perl.misc:663197
>>>>> "U" == Uno <Uno@example.invalid> writes:
U> On 04/19/2011 01:43 PM, Sherm Pendley wrote:
>> Uno<Uno@example.invalid> writes:
>>
>>> $ cat fb1.pl
>>> #!/usr/bin/perl
>>> use strict;
>>>
>>> Are you stoned? Tad, if either being correct or promoting the
>>> discussion in c.l.p.misc is part of your job description, I think you
>>> need to resign.
>>
>> "Uno," get a grip. The space before the #! caused the OS to run
the file
>> as a *shell script*. Once that happened, Perl wasn't involved at all.
>>
>> I'd like to help you, but you're about one ill-informed rant away from
>> being permanently ignored here.
>>
>> sherm--
>>
U> You know, sherm, I've decided that c.l.p.misc has problems I don't
U> want to be a part of. Thanks for all your help.
please don't let the keyboard smack you on the way out.
you have been one of the dumbest posters here in a very long time. and
that includes quite a few people. you still don't even realize that perl
was never the problem and the space was the problem. until you get that,
you will never learn more coding.
uri
--
Uri Guttman ------ uri@stemsystems.com --------
http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support
------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com
---------
$
You are a counter-example to the professed ethic of the open-source
movement and perl culture.
--
Uno
------------------------------
Date: Fri, 22 Apr 2011 07:38:16 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: grabbing a facebook group
Message-Id: <slrnir2tcu.53p.tadmc@tadbox.sbcglobal.net>
Uno <Uno@example.invalid> wrote:
> On 04/21/2011 08:01 PM, Uri Guttman wrote:
>> you still don't even realize that perl
>> was never the problem and the space was the problem.
> So, Uri, what do you think of your contribution to my thread:
It is clearly just frustration that a poster who demonstrates
that he doesn't know something would be so determined to maintain
that ignorance.
Let's recap. You wrote:
Uno> $ ./fb1.pl
Uno> ./fb1.pl: line 2: use: command not found
Uno> ./fb1.pl: line 3: use: command not found
Uno> ./fb1.pl: line 5: use: command not found
Uno> ./fb1.pl: line 7: syntax error near unexpected token `('
Uno> ./fb1.pl: line 7: ` my $fb = Facebook->new('
Uno> $ cat fb1.pl
Uno> #!/usr/bin/perl
^^
^^ note two space characters there
Those are not messages from perl (you can tell because they do
not appear in perldiag.pod, where all of the messages that perl
might issue are documented).
Those are messages from the shell.
Uno> How does my interpreter all of a sudden not know what I mean
Uno> when I say "use?"
By "my interpreter" you meant the perl interpreter.
Then several good folks pointed out that the perl interpreter
was never invoked. The shell interpreter was invoked instead.
Then you wrote:
Uno> I find that white space is not your friend in perl.
Which makes no sense, because perl **never saw the offending whitespace**.
A response that indicated an understanding of what had happened
might have been something like:
I find that whitespace is not your friend in the *nix kernel.
So it was clear that you had not gotten the point yet, so several
more good people tried yet again to help you learn what you did not
know.
Your responses indicated that you *still* had not learned what
you did not know.
At which point many folks deemed you unwilling to learn or
unteachable, and gave up on helping you.
All of the angst in this thread was a reponse to your actions.
To find the cause of "c.l.p.misc's problems", look in the mirror.
As a parting shot, I'll offer you a 3rd chance to learn what
you did not know:
http://en.wikipedia.org/wiki/Magic_number_%28programming%29
Unix script files usually start with a shebang, "#!" (23 21)
followed by the path to an interpreter.
Your file did NOT start with a shebang, so a path to an interpreter
did not exist.
When an interpreter cannot be determined, it defaults to using
the sh interpreter.
--
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: Fri, 22 Apr 2011 02:14:44 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <0sednQ-PAPt5tyzQnZ2dnUVZ5gWdnZ2d@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: Fri, 22 Apr 2011 05:36:41 +0000 (UTC)
From: Eli the Bearded <*@eli.users.panix.com>
Subject: Re: Web Scraping Proxy
Message-Id: <eli$1104220132@qz.little-neck.ny.us>
In comp.lang.perl.misc, Wes Groleau <Groleau+nntp@FreeShell.org> wrote:
> OK, I think you are suggesting that the delay of FF asking me what to do
> about the cert is being interpreted by WSP as an "aborted browser
> request" ?
Yes. Firefox aborts the request while waiting for input.
> And then the reason I can't get FF to accept the cert is
> that the provider of the cert is no longer running?
In this case, the provider of the cert is the proxy program itself.
In order to save pages it needs to decrypt all the requests and then
reencrypt them with it's own key.
> Sad, but understandable. Then your suggested workaround also makes
> sense. Thanks.
Basically just keep restarting it until you get Firefox to accept
the certificate. And if you check "permanently add exception" then
it probably becomes a one time problem.
Elijah
------
private mode or other cache clearing might make it less "permanently"
------------------------------
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 3361
***************************************
