[32182] in Perl-Users-Digest
Perl-Users Digest, Issue: 3447 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jul 20 06:09:21 2011
Date: Wed, 20 Jul 2011 03:09:04 -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 Wed, 20 Jul 2011 Volume: 11 Number: 3447
Today's topics:
=?UTF-8?Q?Re=3A_a_little_parsing_challenge_=E2=98=BA?= <dr.mtarver@gmail.com>
Re: a little parsing challenge =?UTF-8?B?4pi6?= <shortcutter@googlemail.com>
Re: a little parsing challenge ? sln@netherlands.com
Re: Cpan problem XML::LibXML with Ubuntu <goldtech@worldpost.com>
Re: Cpan problem XML::LibXML with Ubuntu <jimsgibson@gmail.com>
Re: Cpan problem XML::LibXML with Ubuntu <tadmc@seesig.invalid>
Re: Cpan problem XML::LibXML with Ubuntu <peter@makholm.net>
Re: Cpan problem XML::LibXML with Ubuntu <mvdwege@mail.com>
global variable scope in perl <eswar.kodati@gmail.com>
Re: Perl Multitasking Question <edgrsprj@ix.netcom.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 19 Jul 2011 22:43:42 -0700 (PDT)
From: Mark Tarver <dr.mtarver@gmail.com>
Subject: =?UTF-8?Q?Re=3A_a_little_parsing_challenge_=E2=98=BA?=
Message-Id: <189130e4-9feb-4d4a-8c31-0e6778b7bba0@15g2000vbw.googlegroups.com>
On Jul 17, 8:47=C2=A0am, Xah Lee <xah...@gmail.com> wrote:
> 2011-07-16
>
> folks, this one will be interesting one.
>
> the problem is to write a script that can check a dir of text files
> (and all subdirs) and reports if a file has any mismatched matching
> brackets.
>
> =E2=80=A2 The files will be utf-8 encoded (unix style line ending).
>
> =E2=80=A2 If a file has mismatched matching-pairs, the script will displa=
y the
> file name, and the =C2=A0line number and column number of the first
> instance where a mismatched bracket occures. (or, just the char number
> instead (as in emacs's =E2=80=9Cpoint=E2=80=9D))
>
> =E2=80=A2 the matching pairs are all single unicode chars. They are these=
and
> nothing else: () {} [] =E2=80=9C=E2=80=9D =E2=80=B9=E2=80=BA =C2=AB=C2=BB=
=E3=80=90=E3=80=91 =E3=80=88=E3=80=89 =E3=80=8A=E3=80=8B =E3=80=8C=E3=80=
=8D =E3=80=8E=E3=80=8F
> Note that =E2=80=98single curly quote=E2=80=99 is not consider matching p=
air here.
>
> =E2=80=A2 You script must be standalone. Must not be using some parser to=
ols.
> But can call lib that's part of standard distribution in your lang.
>
> Here's a example of mismatched bracket: ([)], (=E2=80=9C[[=E2=80=9D), ((,=
=E3=80=91etc. (and
> yes, the brackets may be nested. There are usually text between these
> chars.)
>
> I'll be writing a emacs lisp solution and post in 2 days. =CE=99 welcome
> other lang implementations. In particular, perl, python, php, ruby,
> tcl, lua, Haskell, Ocaml. I'll also be able to eval common lisp
> (clisp) and Scheme lisp (scsh), Java. Other lang such as Clojure,
> Scala, C, C++, or any others, are all welcome, but i won't be able to
> eval it. javascript implementation will be very interesting too, but
> please indicate which and where to install the command line version.
>
> I hope you'll find this a interesting =E2=80=9Cchallenge=E2=80=9D. This i=
s a parsing
> problem. I haven't studied parsers except some Wikipedia reading, so
> my solution will probably be naive. I hope to see and learn from your
> solution too.
>
> i hope you'll participate. Just post solution here. Thanks.
>
> =C2=A0Xah
Parsing technology based on BNF enables an elegant solution. First
take a basic bracket balancing program which parenthesises the
contents of the input. e.g. in Shen-YACC
(defcc <br>
"(" <br> ")" <br$> :=3D [<br> | <br$>];
<item> <br>;
<e> :=3D [];)
(defcc <br$>
<br>;)
(defcc <item>
-*- :=3D (if (element? -*- ["(" ")"]) (fail) [-*-]);)
Given (compile <br> ["(" 1 2 3 ")" 4]) the program produces [[1 2 3]
4]. When this program is used to parse the input, whatever residue is
left indicates where the parse has failed. In Shen-YACC
(define tellme
Stuff -> (let Br (<br> (@p Stuff []))
Residue (fst Br)
(if (empty? Residue)
(snd Br)
(error "parse failure at position ~A~%"
(- (length Stuff) (length Residue))))))
e.g.
(tellme ["(" 1 2 3 ")" "(" 4])
parse failure at position 5
(tellme ["(" 1 2 3 ")" "(" ")" 4])
[[1 2 3] [] 4]
The extension of this program to the case described is fairly simple.
Qi-YACC is very similar.
Nice problem.
I do not have further time to correspond right now.
Mark
------------------------------
Date: Wed, 20 Jul 2011 08:23:09 +0200
From: Robert Klemme <shortcutter@googlemail.com>
Subject: Re: a little parsing challenge =?UTF-8?B?4pi6?=
Message-Id: <98naiiFlf4U1@mid.individual.net>
On 18.07.2011 16:39, Xah Lee wrote:
>
> On Jul 17, 12:47 am, Xah Lee<xah...@gmail.com> wrote:
>> 2011-07-16
>>
>> folks, this one will be interesting one.
>>
>> the problem is to write a script that can check a dir of text files
>> (and all subdirs) and reports if a file has any mismatched matching
>> brackets.
>> =E2=80=A6
>
> Ok, here's my solution (pasted at bottom). I haven't tried to make it
> elegant or terse, yet, seeing that many are already much elegent than
> i could possibly do so with my code.
>
> my solution basically use a stack. (i think all of us are doing
> similar) Here's the steps:
>
> =E2=80=A2 Go thru the file char by char, find a bracket char.
> =E2=80=A2 check if the one on stack is a matching opening char. If so r=
emove
> it. Else, push the current onto the stack.
> =E2=80=A2 Repeat the above till end of file.
> =E2=80=A2 If the stack is not empty, then the file got mismatched brack=
ets.
> Report it.
> =E2=80=A2 Do the above on all files.
Small correction: my solution works differently (although internally the =
regexp engine will roughly do the same). So, my approach summarized
- traverse a directory tree
- for each found item of type "file"
- read the whole content
- throw it at a regexp which is anchored at the beginning
and does the recursive parsing
- report file if the match is shorter than the file
Note: special feature for recursive matching is used which Perl's regexp =
engine likely can do as well but many others don't.
Cheers
robert
--=20
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
------------------------------
Date: Mon, 18 Jul 2011 12:34:45 -0700
From: sln@netherlands.com
Subject: Re: a little parsing challenge ?
Message-Id: <482927hpr2mr4au3c0f98rkaghnna9230q@4ax.com>
On Sun, 17 Jul 2011 00:47:42 -0700 (PDT), Xah Lee <xahlee@gmail.com> wrote:
>2011-07-16
>
>folks, this one will be interesting one.
>
>the problem is to write a script that can check a dir of text files
>(and all subdirs) and reports if a file has any mismatched matching
>brackets.
>
[snip]
>i hope you'll participate. Just post solution here. Thanks.
>
I have to hunt for a job so I'm not writing a solution for you.
Here is a thin regex framework that may get you started.
-sln
---------------------
use strict;
use warnings;
my @samples = qw(
A98(y[(np)r]x)tp[kk]a.exeb
A98(y[(np)r]x)tp[kk]a}.exeb
A98(‹ynprx)tpk›ka.mpeg
‹A98(ynprx)tpk›ka
“A9«8(yn«pr{{[g[x].}*()+}»)tpkka».”
“A9«8(yn«pr{{[g[x].]}*()+}»)tpkka».”
“A9«8(yn«pr»)tpkka».”
“A9«8(yn«pr»)»”t(()){}[a[b[d]{}]pkka.]“«‹“**^”{[()]}›»”
“A9«8(yn«pr»)”t(()){}[a[b[d]{}]pkka.]“«‹“**^”{[()]}›»”
);
my $regex = qr/
^ (?&FileName) $
(?(DEFINE)
(?<Delim>
\( (?&Content) \)
| \{ (?&Content) \}
| \[ (?&Content) \]
| \“ (?&Content) \”
| \‹ (?&Content) \›
| \« (?&Content) \»
# add more here ..
)
(?<Content>
(?: (?> [^(){}\[\]“”‹›«»]+ ) # add more here ..
| (?&Delim)
)*
)
(?<FileName>
(?&Content)
)
)
/x;
for (@samples)
{
print "$_ - ";
if ( /$regex/ ) {
print "passed \n";
}
else {
print "failed \n";
}
}
__END__
Output:
A98(y[(np)r]x)tp[kk]a.exeb - passed
A98(y[(np)r]x)tp[kk]a}.exeb - failed
A98(‹ynprx)tpk›ka.mpeg - failed
‹A98(ynprx)tpk›ka - passed
“A9«8(yn«pr{{[g[x].}*()+}»)tpkka».” - failed
“A9«8(yn«pr{{[g[x].]}*()+}»)tpkka».” - passed
“A9«8(yn«pr»)tpkka».” - passed
“A9«8(yn«pr»)»”t(()){}[a[b[d]{}]pkka.]“«‹“**^”{[()]}›»” - passed
“A9«8(yn«pr»)”t(()){}[a[b[d]{}]pkka.]“«‹“**^”{[()]}›»” - failed
------------------------------
Date: Mon, 18 Jul 2011 16:46:02 -0700 (PDT)
From: goldtech <goldtech@worldpost.com>
Subject: Re: Cpan problem XML::LibXML with Ubuntu
Message-Id: <561d5577-2c54-4f0f-afda-2a40de640c9a@v12g2000vby.googlegroups.com>
Or here...or here?
So CPAN does not take care of dependencies?
------------------------------
Date: Mon, 18 Jul 2011 17:39:03 -0700
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: Cpan problem XML::LibXML with Ubuntu
Message-Id: <180720111739036230%jimsgibson@gmail.com>
In article
<561d5577-2c54-4f0f-afda-2a40de640c9a@v12g2000vby.googlegroups.com>,
goldtech <goldtech@worldpost.com> wrote:
> Or here...or here?
>
> So CPAN does not take care of dependencies?
CPAN has a shell ('cpan' or 'perl -MCPAN -e shell') that will take care
of dependencies to other CPAN modules. If a module requires a non-CPAN
library, the CPAN shell won't install it.
--
Jim Gibson
------------------------------
Date: Mon, 18 Jul 2011 21:17:43 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Cpan problem XML::LibXML with Ubuntu
Message-Id: <slrnj29psg.ppq.tadmc@tadbox.sbcglobal.net>
goldtech <goldtech@worldpost.com> wrote:
> Or here...or here?
Where or where?
--
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: Tue, 19 Jul 2011 07:23:19 +0200
From: Peter Makholm <peter@makholm.net>
Subject: Re: Cpan problem XML::LibXML with Ubuntu
Message-Id: <87pql6vo6w.fsf@vps1.hacking.dk>
goldtech <goldtech@worldpost.com> writes:
> So CPAN does not take care of dependencies?
CPAN (the module) only takes care of dependencies of perl modules. In
some cases there exists modules in the Alien:: namespace which can take
care of installing external libraries.
//Makholm
------------------------------
Date: Tue, 19 Jul 2011 08:40:29 +0200
From: Mart van de Wege <mvdwege@mail.com>
Subject: Re: Cpan problem XML::LibXML with Ubuntu
Message-Id: <86pql6ydr6.fsf@gareth.avalon.lan>
goldtech <goldtech@worldpost.com> writes:
> Or here...or here?
>
> So CPAN does not take care of dependencies?
Again, as suggested, use your system package manager.
Why are you building XML::LibXML yourself instead of using a
distribution package? And if you really have to build it yourself, why
not use the dh-make-perl tool? That will at least give the correct
package names of the missing dependencies, so you can install them using
APT (Assuming Ubuntu hasn't broken dh-make-perl; my experience with Ubuntu
development tools is sadly not good).
You should always go for an existing deployment mechanism before
building from upstream source. After all, I assume your software is
going to be deployed beyond your own development environment, right?
Mart
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
------------------------------
Date: Wed, 20 Jul 2011 02:21:29 -0700 (PDT)
From: Eswar <eswar.kodati@gmail.com>
Subject: global variable scope in perl
Message-Id: <c7ac6e62-3e3e-4aee-935e-9e184433d0e9@r5g2000prf.googlegroups.com>
I need to move couple of functions from one perl file to another. In
this course the global variables that are used in the functions also
moved. I declared the global variables as 'our'. I am updating the
global variable in (1st)one function and using the same in
(Second)another function. when I print the variable in the secong
function, its printing null. But before the moment of the functions,
its printing the updated value int he 1st functions. I dont know why
its not printing after the movement. My friend suggested me to use
declare the variable as $::, then it looks fine. I wanted to know the
difference between our and $:: and why this dint work with our. If
anybody helps, I am very thankful.
------------------------------
Date: Tue, 19 Jul 2011 17:33:09 -0500
From: "E.D.G." <edgrsprj@ix.netcom.com>
Subject: Re: Perl Multitasking Question
Message-Id: <cfOdndSVXOu1m7vTnZ2dnUVZ_tGdnZ2d@earthlink.com>
"Ralph Malph" <ralph@happydays.com> wrote in message
news:ac682$4e246f9d$ce534406$2510@news.eurofeeds.com...
> Well, the "classic" solution to this is to used shared memory.
> Since you are on Windows of course you can't use a real SysV IPC type
> solution(i.e. IPC::Shareable) but you can use this
> http://search.cpan.org/~roger/Win32-MMF-0.09e/MMF.pm
Thanks for the information. I took a quick look at the module and
plan to look at it in more detail later.
Using shared memory was actually the an option that was discussed a
while back in one of the Windows Newsgroups. The goal with that particular
effort was to learn how to create a shared memory area that both Perl and
the Gnuplot plotting program could use to exchange information. But at the
time, developing the necessary Windows code appeared to be too complicated.
I am only an intermediate level programmer.
PROPOSED WEB SITE
An effort is underway to create a Web site where a variety of
humanitarian projects would be worked on. I am presently holding
discussions with a group that I am hoping will initially serve as the
official "owner" of the Web site and domain name. I could easily create
such a Web site and pay for the cost of running it myself. So funding for
it won't be a problem.
Science experts would be doing the actual research at the site.
However, if the Web site development effort is a success we will probably
try to locate some experienced computer programmers who could help with both
developing computer code that would run on home computers, with developing
CGI code for use on Web site computers, and with developing regular HTML and
perhaps PHP code etc. for individual Web pages. Scientist researchers
including myself very often don't have the necessary programming skills to
be able to do all of those types of things.
Regards to all,
E.D.G.
------------------------------
Date: Tue, 19 Jul 2011 02:17:21 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <vuSdnczDVpMcsrjTnZ2dnUVZ5qqdnZ2d@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: 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 3447
***************************************
