[22841] in Perl-Users-Digest
Perl-Users Digest, Issue: 5062 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri May 30 06:05:43 2003
Date: Fri, 30 May 2003 03:05:05 -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, 30 May 2003 Volume: 10 Number: 5062
Today's topics:
Re: A bug in perl? <mordor@fly.srk.fer.hr>
Re: Comments/Help on Ring Element Id Subroutine? <email_entropy123@yahoo.com>
Re: Efficient Date Sorting <nobody@noplace.com>
Re: Efficient Date Sorting <nobody@noplace.com>
Re: Filling an array from another array <graham.drabble@lineone.net>
Re: Filling an array from another array <graham.drabble@lineone.net>
Re: Form script changes <john.thetenant-s@moving-picture.com>
Re: Form script changes <john.thetenant-s@moving-picture.com>
Re: How can I get XML::RSS? (ActivePerl) <singleantler-news@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: uninitialized value in eval block? <spam.me.senseless@sitting.duck>
Want to call a counter. <mail@annuna.com>
Re: Want to call a counter. <nobody@noplace.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 30 May 2003 09:42:52 +0000 (UTC)
From: Zeljko Vrba <mordor@fly.srk.fer.hr>
Subject: Re: A bug in perl?
Message-Id: <slrnbde9ss.6c1.mordor@fly.srk.fer.hr>
In article <slrnbdc206.33o.tadmc@magna.augustmail.com>, Tad McClellan wrote:
> Zeljko Vrba <mordor@fly.srk.fer.hr> wrote:
>
>> Is there any reason the following wouldn't work:
>>
>> @{$stud->{'col1', 'col2', 'col3'}} = map { $_ || "" } ($col1, $col2, $col3);
>
>
> Yes.
>
> It appears you were trying to get a hash slice on the LHS, but
> that isn't what you have.
>
Wow.. I'm a long-time perl user and still (although rarely) fall into its
traps :)
>
> You could have made it easier for us to help you (which increases
> your chances of _getting_ help) by providing a short and complete
> program that we can run, as suggested in the Posting Guidelines:
>
OK, I'll do it next time. Thanks for help!
------------------------------
Date: Fri, 30 May 2003 04:25:10 -0500
From: "ent123" <email_entropy123@yahoo.com>
Subject: Re: Comments/Help on Ring Element Id Subroutine?
Message-Id: <pan.2003.05.30.09.24.58.616927@yahoo.com>
Ok,
I de-cuted the code and ran a ?simple? example -> Hope this makes it easier to help me out. Thanks!
##First the code:
foreach $first_node (@plus_degree) {#@plus_degree: each atom in ring with
>2 connections
@path =(); #This array tracks the path taken from $firstnode, prevent
backtrack
push (@path, $first_node);
$last_node=$first_node;
#The neighbor looks at neighboring molecules and, if the exist, adds them
to an array.
&the_neighbor(\%ehash, $first_node, $last_node, \@ring_atoms, \@path);
}
sub the_neighbor {
my ($connect_node, $first_n, $last_n, $ring_atoms, $path) = @_;
my $neighbor;
foreach $neighbor (@$ring_atoms) {
#consider each atom in the ring_atom list a possible neighbor
if ((exists ($connect_node->{ $last_n }->{ $neighbor })) && (&n_exists_element($neighbor, @$path))) {
#if a bond/edge occurs between $last_n and $neighbor && $neighbor has not been looked at before
push(@$path, $neighbor);
push (@$first_n, $neighbor);
#add $neighbor to @$path and @$first_n
print "$first_n: @$first_n\n";
if ((exists ($connect_node->{ $first_n }->{ $neighbor })) && ( $last_n ne $first_n )) {
#if a bond/edge occurs between first and neighbor and last is not the same as first
push (@$first_n, $first_n);
print "Possible Ring here: $first_n: @$first_n\n";
print "Path 2 Atom: @$path\n";
@$first_n = ();
}
$last_n = $neighbor;
&the_neighbor($connect_node, $first_n, $last_n, $ring_atoms, $path);
#go find another neighbor which is not a) the first atom or b) the last one
}
}
}
For the input previously given me in the dfs routine this is the
input/output: If I have anything left tomorrow after class I will get a
molecule with ~20 atoms...
# H H H H
# | | | |
# C - C - C - C - C
# \ / \ /
# C C
# | |
# H H
my %graph2 = ( C1=>{H1=>1, C2=>1}, C2=>{H2=>1, C3=>1},
C3=>{H3=>1, C1=>1, C4=>1}, C4=>{C5=>1}, C5=>{H4=>1, C6=>1},
C6=>{H5=>1,C7=>1}, C7=>{H6=>1, C5=>1});
atoms_in_rings:C6 C5 C3 C7 C2 C1
Most Heavily Connected:C3
All Atoms In Rings:C6 C5 C7 C1 C2
C1 C3 are connected
C3 C1 C2 are connected
program ends without finding a ring. I'm not sure how my program would
handle hydrogens so I'll take a closer look in the am (is 4am now..)
------------------------------
Date: Fri, 30 May 2003 08:08:22 GMT
From: "Gregory Toomey" <nobody@noplace.com>
Subject: Re: Efficient Date Sorting
Message-Id: <01c32684$599b62c0$f5498a90@gmtoomey>
Matthew Braid <mbear@uq.net.au> wrote in article
<bb6ucb$87n$1@bunyip.cc.uq.edu.au>...
> Hi all,
>
> I have to write a coderef to pass to sort so that it takes a list of
> 'human-readable' dates. I can't preparse the list in any way first as it
> is being used as part of a Tk widget (Tk::MListbox), so I can't do any
> groovy map-sort-map tricks.
Why not? Try the Schwartzian transform:
http://prometheus.frii.com/~gnat/yapc/2000-stages/slide40.html
Then getting your dates into some canonical form such as YYYYMMDDHHMMSS
(eg 12:59 am on Mon 31/12/2003 becomes "300423422359")
so you can do a simple string compasrision in the sort.
gtoomey
------------------------------
Date: Fri, 30 May 2003 08:13:30 GMT
From: "Gregory Toomey" <nobody@noplace.com>
Subject: Re: Efficient Date Sorting
Message-Id: <01c32685$10df95a0$f5498a90@gmtoomey>
Gregory Toomey <nobody@noplace.com> wrote in article
<01c32684$599b62c0$f5498a90@gmtoomey>...
> (eg 12:59 am on Mon 31/12/2003 becomes "300423422359")
Err "20031231125900" looks better
GT
------------------------------
Date: Fri, 30 May 2003 10:46:13 +0100
From: Graham Drabble <graham.drabble@lineone.net>
Subject: Re: Filling an array from another array
Message-Id: <Xns938B6D8FBD28Cgrahamdrabblelineone@ID-77355.user.dfncis.de>
On 29 May 2003 "Michael P. Broida" <michael.p.broida@boeing.com>
wrote in news:3ED67F56.30D5AB8F@boeing.com:
> Graham Drabble wrote:
>> then how can I make
>>
>> @all_possible_choices = ('a a a',
>> 'a a b',
>> 'a a c',
>> 'a b a',
>> 'a b b',
>> .... all the rest,
>> 'c c c',)
> There may very well be more "elegant" Perl methods,
> but I would use simple nested loops:
>
> UNTESTED AIR-CODE:
>
> foreach $val_1 (@choices)
> {
> foreach $val_2 (@choices)
> {
> foreach $val_3 (@choices)
> {
> push @all_possible_choices, "$val_1 $val_2
> $val_3";
> }
> }
> }
It does work but I was looking for a way that would scale easily with
different values of $depth.
--
Graham Drabble
If you're interested in what goes on in other groups or want to find
an interesting group to read then check news.groups.reviews for what
others have to say or contribute a review for others to read.
------------------------------
Date: Fri, 30 May 2003 10:48:32 +0100
From: Graham Drabble <graham.drabble@lineone.net>
Subject: Re: Filling an array from another array
Message-Id: <Xns938B6DF453109grahamdrabblelineone@ID-77355.user.dfncis.de>
On 29 May 2003 "Christian Winter" <thepoet@nexgo.de> wrote in
news:3ed679b5$0$18810$9b4e6d93@newsread2.arcor-online.net:
> If you want to make a program that fits a variable
> number of choices and result depths, take a recursive
> approach:
Thanks. I had wondered about that but couldn't get my head round how to
do it (this is normal with me and recursion). Looks like this could
well be what I want. Thanks.
--
Graham Drabble
If you're interested in what goes on in other groups or want to find
an interesting group to read then check news.groups.reviews for what
others have to say or contribute a review for others to read.
------------------------------
Date: Fri, 30 May 2003 10:45:17 +0100
From: John Strauss <john.thetenant-s@moving-picture.com>
Subject: Re: Form script changes
Message-Id: <20030530104517.1bfcc10e.john.thetenant-s@moving-picture.com>
On 29 May 2003 14:36:37 -0700
techadmin@shaw.ca (Steve) wrote:
> John Strauss <john.thetenant-s@moving-picture.com> wrote in message news:<20030529170640.27025d13.john.thetenant-s@moving-picture.com>...
> > On 29 May 2003 08:39:03 -0700
> > techadmin@shaw.ca (Steve) wrote:
> > >
> > > I have a simple perl script running to process form input (bnbform
> > > version 4.0?)(The forms are all html). Right now the form returns all
> > > the values that are available on the form in the form of a list, a=,
> > > b=, c=. If you enter into the form the value for a as ABC then you
> > > reveive, a=abc,b=,c= etc. I would like to recode it so that the only
> > > values returned are those input values used. so in fact b= and c=,
> > > would not show in the e-amil as there was no input value assigned. I
> > > hope this all makes sence.
> > > My knowledge of perl is limited to none but follow instruction well.
> >
> > replace
> > @pairs=split(/&/,$temp);
> >
> > with
> > @pairs=grep(/=.+/,split(/&/,$temp));
> >
> >
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > drop the .thetenant to get me via mail
>
> Sorry but after making both of these changes it does not do as
> intended i still receive all entries filled or not.
>
> Any ideas? do you wish to see the code? It big as you know.
>
> Thanks, Steve
>
>
(note: please don't top-post. i've rearrainged your post accordingly.)
bnbform wants you to register your data fields in the
data_order hidden field on your form. it populates
@sortlist from the $content of the data_order $key.
bnbform uses @sortlist in the "thank you" page and
in the email. you want to remove items from @sortlist
which had no content. bnbform also populates %fields,
which you can use to wrangle @sortlist.
drop all previous suggestions; none will do what you need.
instead, after this block:
foreach $item(@pairs) {
...
}
add this line:
@sortlist = grep ($fields{$_} ne '', @sortlist);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drop the .thetenant to get me via mail
------------------------------
Date: Fri, 30 May 2003 10:57:19 +0100
From: John Strauss <john.thetenant-s@moving-picture.com>
Subject: Re: Form script changes
Message-Id: <20030530105719.4fe0ce47.john.thetenant-s@moving-picture.com>
On 29 May 2003 13:51:12 -0700
techadmin@shaw.ca (Steve) wrote:
>
> John Strauss <john.thetenant-s@moving-picture.com> wrote in message news:<20030529170640.27025d13.john.thetenant-s@moving-picture.com>...
> > On 29 May 2003 08:39:03 -0700
> > techadmin@shaw.ca (Steve) wrote:
> > >
> > > I have a simple perl script running to process form input (bnbform
> > > version 4.0?)(The forms are all html). Right now the form returns all
> > > the values that are available on the form in the form of a list, a=,
> > > b=, c=. If you enter into the form the value for a as ABC then you
> > > reveive, a=abc,b=,c= etc. I would like to recode it so that the only
> > > values returned are those input values used. so in fact b= and c=,
> > > would not show in the e-amil as there was no input value assigned. I
> > > hope this all makes sence.
> > > My knowledge of perl is limited to none but follow instruction well.
> >
> > replace
> > @pairs=split(/&/,$temp);
> >
> > with
> > @pairs=grep(/=.+/,split(/&/,$temp));
> >
> >
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > drop the .thetenant to get me via mail
>
> Thanks, for the fast response.
> What I am understanding is that as long as I don't return a value of
> '0' for a check box then I should be ok.
> What about a '0' in a text box? although I don't think that would
> happen.
> Could you please give a quick explanation of what each line is doing
> this way I can better understand what I am typing.
> Thanks for all your help. Steve
@pairs=grep(/=.+/,split(/&/,$temp));
what this means (right to left):
- split $temp into a list of strings tokenized by '&'
- the grep weeds out items from the given list which don't
match the regexp /=.+/.
- the regexp /=.+/ means match if there is a "=" followed
by at least one character.
- the list returned by grep is placed into @pairs.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drop the .thetenant to get me via mail
------------------------------
Date: Fri, 30 May 2003 10:08:49 +0100
From: Paul Silver <singleantler-news@hotmail.com>
Subject: Re: How can I get XML::RSS? (ActivePerl)
Message-Id: <0r7edv8b3v7nb9j6fiabej4g4j05d1cdra@4ax.com>
On Thu, 29 May 2003 21:27:49 -0500, "Randy Kobes" wrote:
>"Paul Silver" wrote in message
> news:2m7cdv40ruuulki9n8lt48538kcrplktl1@4ax.com...
>> I'm trying to get XML::RSS working in ActivePerl, but the readme says
>> I need to compile it. Unfortunately I have no C compiler.
>>
>> Does anyone know where I can get a packaged version of XML::RSS that
>> ppm will be able to cope with? Or any other ideas about getting it
>> working?
>
>We have a ppm package at http://theoryx5.uwinnipeg.ca/ppms/
>for ActivePerl 8xx and http://theoryx5.uwinnipeg.ca/ppmpackages/
>for 6xx.
Thanks Randy, that's just what I needed.
I had a bit of trouble installing it, but that turned out to be
another repository getting in the way and now things are working.
Thanks again
Paul.
--
Please remove '-news' from address to send e-mail.
http://www.g2blue.co.uk
------------------------------
Date: Fri, 30 May 2003 02:24:47 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <KbqdnfcWvJWimkqjXTWcqg@august.net>
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.4 $)
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.
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://mail.augustmail.com/~tadmc/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
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_group_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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 30 May 2003 08:40:13 +0100
From: SeeMySig <spam.me.senseless@sitting.duck>
Subject: Re: uninitialized value in eval block?
Message-Id: <Y7FLMhAdrw1+EwI1@nildram.co.uk>
In message <1bff1830.0305292155.304f8b84@posting.google.com>, Bryan
Castillo <rook_5150@yahoo.com> writes
>> >Yes this is a known problem with CGI.pm. It uses a kind of weird
>> >autoload mechanism that uses eval EXPR (not eval BLOCK). The problem
>> >is that if an error or warning occurs in code that results from an
>> >eval EXPR the location information is cyrptic.
>> You mean I have been tearing out what little hair I have left for no
>> good reason :-(
>
>Isn't learning a good reason? Don't you know more about eval and
>interpreting warning messages than you use to?
Yes, very much so to both questions. But it seems a long way still to go
yet ;-)
--
RA Jones
ra(dot)jones(at)dpw(dot)clara(dot)net
------------------------------
Date: Fri, 30 May 2003 03:16:09 -0500
From: Joe Creaney <mail@annuna.com>
Subject: Want to call a counter.
Message-Id: <3ED71349.9030708@annuna.com>
I wrote a counter in perl but I can't access it from my page. I can
only run the counter if I put the cgi location from my browser. I have
seen an example in a book but it dosnt work.
------------------------------
Date: Fri, 30 May 2003 08:10:20 GMT
From: "Gregory Toomey" <nobody@noplace.com>
Subject: Re: Want to call a counter.
Message-Id: <01c32684$9fb23220$f5498a90@gmtoomey>
Joe Creaney <mail@annuna.com> wrote in article
<3ED71349.9030708@annuna.com>...
> I wrote a counter in perl but I can't access it from my page. I can
> only run the counter if I put the cgi location from my browser. I have
> seen an example in a book but it dosnt work.
See http://perl.about.com/library/weekly/aa080901a.htm
gtoomey
------------------------------
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 5062
***************************************
