[32249] in Perl-Users-Digest
Perl-Users Digest, Issue: 3516 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 11 06:09:25 2011
Date: Tue, 11 Oct 2011 03:09:09 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 11 Oct 2011 Volume: 11 Number: 3516
Today's topics:
Re: Help me to Improve <sssdevelop@gmail.com>
Re: Help me to Improve <whynot@pozharski.name>
Re: Help me to Improve <rweikusat@mssgmbh.com>
Re: Help me to Improve xhoster@gmail.com
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 9 Oct 2011 23:36:17 -0700 (PDT)
From: SSS Develop <sssdevelop@gmail.com>
Subject: Re: Help me to Improve
Message-Id: <cb515742-856e-48ed-8f40-4e6859536cfa@f6g2000vbm.googlegroups.com>
Very healthy discussions ! thanks everyone for participating !
(will post the final version soon :))
thank you,
sssdevelop
On Oct 10, 5:09=A0am, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth Rainer Weikusat <rweiku...@mssgmbh.com>:
>
>
>
>
>
>
>
>
>
> > Ben Morrow <b...@morrow.me.uk> writes:
>
> > > It's best to avoid dative method syntax (METHOD OBJECT ARGS or METHOD
> > > CLASS ARGS), at least in part because it encourages the idea that the=
re
> > > is something special about the 'new' method.
>
> > > =A0 =A0 my $pm =3D Parallel::ForkManager->new($MAX_PROC);
>
> > > (Yes, I know you just copied that from the documentation. Unfortunate=
ly
> > > a lot of CPAN documentation uses older, now-discouraged idioms in the
> > > examples.)
>
> > In this particular case, the 'indirect object' syntax is actually even
> > 'discouraged' by the corresponding Perl documentation. More generally,
> > however, the sentence above parses as "a lot of people who wrote
> > useful code disagreed with some (or all) opinions
> > $random_people_on_usenet had regarding what they should have done".
>
> I know. I was aware when I wrote that paragraph that I was weaselling
> out of properly explaining what's wrong with the dative syntax, and the
> reason I was doing that was that I can never remember an example of
> where it goes wrong :). I can give you *lots* of examples where Perl
> assumes I'm making a dative method call when I didn't want it to, but
> that's a reason for not putting it in the language at all, rather than
> one for not using it if its there.
>
> I believe the canonical example is
>
> =A0 =A0 my $rv =3D method $obj;
>
> with a 'sub method' in the current package. While that is a problem
> (since it will parse differently depending on the presence of the sub)
> it is easily disambiguated:
>
> =A0 =A0 my $rv =3D method $obj ();
>
> So, can anyone remind me of when this actually goes wrong?
>
>
>
>
>
>
>
>
>
> > >> my $cnfhs =3D get_configurations();
>
> > >> foreach my $key ( keys %$cnfhs ) {
>
> > >> =A0 =A0 my $conf =3D $cnfhs->{$key};
>
> > > You can write that loop as
>
> > > =A0 =A0 while (my ($key, $conf) =3D each %$cnfhs) {
>
> > > and it'll even be more efficient on really large hashes. (Not enough
> > > people remember about 'each'.)
>
> > Except in case of insanely large hashes (> 500,000 keys, according to
> > some tests I did a while back), getting the list of keys and
> > traversing the hash 'open coded' will be faster than calling Perl
> > subroutine per key. OTOH, the latter should need less memory.
>
> Interesting. The efficiency wasn't the point, of course. The point was
> to get key and value in one go.
>
> When you say 'calling Perl subroutine per key' do you mean just the call
> to 'each'? 'each' isn't a subroutine, of course, but the while loop does
> have to run some Perl every iteration rather than just popping the
> stack.
>
>
>
>
>
>
>
>
>
> > > <snip>
> > >> sub logger {
> > >> =A0 =A0 my $logfilename =3D shift;
> > >> =A0 =A0 $LOGFILE{file} =3D $logfilename;
> > >> =A0 =A0 my $conf =3D q(
> > >> =A0 =A0 =A0 =A0 log4perl.logger =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0=3D INFO, FileApp
> > >> =A0 =A0 =A0 =A0 log4perl.appender.FileApp =A0 =A0 =A0 =A0 =A0=3D
> > >> Log::Log4perl::Appender::File
> > >> =A0 =A0 =A0 =A0 log4perl.appender.FileApp.filename =3D sub {getLogfi=
lename();}
>
> > > <...later...>
> > >> sub getLogfilename {
>
> > >> =A0 =A0 return "$APP_HOME/$HTTPRESP/logs/" . $LOGFILE{file} . ".log"=
;
>
> > >> }
>
> > > It's not really clear to me what you're trying to do here with
> > > $LOGFILE{file}, but it can almost certainly be done less confusingly.
> > > Since you don't appear to use it anywhere else, is there any reason n=
ot
> > > to just put the correct filename straight in the log4perl config?
>
> > The subroutine above is a specific algorithm with a generic name and
> > the usual reason for functional decomposition (didn't someboday claim
> > that was acutally used in practice not that long ago) is that it
> > simplifies the code at each level abstraction by moving details
> > which are not relevant for the present algorithm elsewhere.
>
> For there to be any merit to that argument, getLogFilename would have to
> be independant of logger. Since logger sets a global read by
> getLogFilename, this obviously isn't the case. If you were to rewrite
> the code so it looked like
>
> =A0 =A0 sub logger {
> =A0 =A0 =A0 =A0 my $logfilename =3D shift;
> =A0 =A0 =A0 =A0 my $logpath =A0 =A0 =3D getLogFilename($logfilename);
> =A0 =A0 =A0 =A0 my $conf =A0 =A0 =A0 =A0=3D qq(
> =A0 =A0 =A0 =A0 =A0 =A0 ...filename =3D $logpath
>
> I would consider that a sensible arrangement. You can argue about
> whether or not the mapping from basename to full path should be a
> separate function: in this case, since it's neither particularly
> complicated nor something that can be changed at runtime ISTM better to
> put the expression inline, but it makes little difference.
>
> What I was complaining about was the extremely convoluted data path that
> went like this:
>
> =A0 =A0 - stuff a value into (the sole element of) a global;
> =A0 =A0 - create a string containing the Perl code for a sub call;
> =A0 =A0 - pass that string to a method, which will
> =A0 =A0 =A0 =A0 - parse out the sub call;
> =A0 =A0 =A0 =A0 - call the sub, which will
> =A0 =A0 =A0 =A0 =A0 =A0 - pull the value out of the global;
> =A0 =A0 =A0 =A0 =A0 =A0 - interpolate it into a path;
> =A0 =A0 =A0 =A0 =A0 =A0 - return that path;
> =A0 =A0 =A0 =A0 - use the returned value as a log filename.
>
> I was recommending something more like
>
> =A0 =A0 - interpolate the basename into a path;
> =A0 =A0 - interpolate that path into a config string;
> =A0 =A0 - pass that string to a method, which will
> =A0 =A0 =A0 =A0 - use it as a log filename.
>
> Whether the first step is a sub call or a direct expression is
> irrelevant.
>
> Ben
------------------------------
Date: Mon, 10 Oct 2011 10:01:11 +0300
From: Eric Pozharski <whynot@pozharski.name>
Subject: Re: Help me to Improve
Message-Id: <slrnj9561n.cbr.whynot@orphan.zombinet>
with <nZOdnQ0guILouA_TnZ2dnUVZ8hCdnZ2d@bt.com> Ben Morrow wrote:
>
> Quoth Tad McClellan <tadmc@seesig.invalid>:
>> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>> > Ben Morrow <ben@morrow.me.uk> writes:
*SKIP*
>>> Using double-quotes means the compiler has to analyze the string order
>>> to determine if and how something needs to be interpolated into
>>> it. Otherwise, this effort can be avoided and also the effort the next
>>> person who looks at the code needs to come to the same result.
*SKIP*
>> I, errr, agree with Rainer here, more for his second reason
>> that for his first.
>>
>> I am always looking to optimize for maintenance.
>>
>> Using double quotes when nothing is intended to be interpolated
>> is in _bad_ taste. :-)
>
> Well, at least I'm not alone:
So the double-quote-war has begun? Let me introduce some fuel to that
so far ceased fire
my $aa;
my $ab = 'abc';
$aa = eval q|"$ab"|
$aa = eval q|'$ab'|
$aa = eval q|"\\$ab"|
$aa = eval q|'def'|
#!/usr/bin/perl
use strict;
use warnings;
use Benchmark qw{ cmpthese timethese };
my $aa;
my $ab = 'abc';
cmpthese timethese -5, {
code00 => sub { $aa = eval q|"$ab"| },
code01 => sub { $aa = eval q|'$ab'| },
code02 => sub { $aa = eval q|"\\$ab"| },
code03 => sub { $aa = eval q|'def'| },
};
__END__
Benchmark: running code00, code01, code02, code03 for at least 5 CPU seconds...
code00: 6 wallclock secs ( 5.00 usr + 0.02 sys = 5.02 CPU) @ 64101.99/s (n=321792)
code01: 6 wallclock secs ( 5.18 usr + 0.00 sys = 5.18 CPU) @ 96095.95/s (n=497777)
code02: 6 wallclock secs ( 5.24 usr + 0.00 sys = 5.24 CPU) @ 69054.58/s (n=361846)
code03: 5 wallclock secs ( 5.34 usr + 0.00 sys = 5.34 CPU) @ 94380.15/s (n=503990)
Rate code00 code02 code03 code01
code00 64102/s -- -7% -32% -33%
code02 69055/s 8% -- -27% -28%
code03 94380/s 47% 37% -- -2%
code01 96096/s 50% 39% 2% --
Hopefully, I did leaning sticks correctly in 'code02'.
*CUT*
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Mon, 10 Oct 2011 19:35:09 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Help me to Improve
Message-Id: <874nzgy9sy.fsf@sapphire.mobileactivedefense.com>
Jürgen Exner <jurgenex@hotmail.com> writes:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>Ben Morrow <ben@morrow.me.uk> writes:
>>> Passing a value into a sub in a file-scoped global is always worth
>>> avoiding if you can. In this case it's easy: pass it in as a real
>>> parameter instead.
>>
>>Doing something because it can be done is just about the most awful
>>reason for doing it which can be imagined, especially in code where
>>more or less everything can be done.
>
> Are you arguing in favour of or against global variables?
I'm arguing against 'do this whenever you can' 'design recipes'. As to
'global variables': A (non OO) module composed of some subroutines and
some shared state variables these subroutines work with is
structurally similar/ identical (isomorph) to an object with some
instance variables and some methods working with these. Programs can
often be decomposed into relatively independent functional units
providing services to each other by invoking interface routines. These
independent functional units will usually be stateful, meaning, they
will have a set of internal variables with 'state information'. I see
no ground for an argument 'for' or 'against' something except maybe at
the completely different level of 'should computer programs work like
other, complex real-world objects', IOW, have state which changes over
time, or should fat runtimes be used to provide the illusion that it
wasn't in this way.
------------------------------
Date: 11 Oct 2011 00:37:45 GMT
From: xhoster@gmail.com
Subject: Re: Help me to Improve
Message-Id: <20111010203745.445$qh@newsreader.com>
Tad McClellan <tadmc@seesig.invalid> wrote:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
> > Ben Morrow <ben@morrow.me.uk> writes:
> >
> > [...]
> >
> >> I see Tad's already mentioned you're using 'our' where you could be
> >> using 'my'. I would add that there's no need for concatentation when
> >> you can interpolate, and that you can assign directly to a hash too:
> >>
> >> my $APP_HOME = '/usr/local/application';
> >> my $HTTPRESP = 'httpresp';
> >> my %LOGFILE = (
> >> file => "$APP_HOME/$HTTPRESP/logs/generic.log",
> >> );
> >>
> >> (Whether to use single or double quotes when nothing will be
> >> interpolated is a matter of taste.
> >
> > Using double-quotes means the compiler has to analyze the string order
> > to determine if and how something needs to be interpolated into
> > it.
Sure, but who cares?
> > Otherwise, this effort can be avoided and also the effort the next
> > person who looks at the code needs to come to the same result.
Why would the person need to do that? I find it more common that I need to
interpolate where I (or someone) didn't before, and now I have to inspect
the whole string to find out what it was that motivated the person to make
it a single quote rather than double in the first place, only to find out
there was no reason for it.
>
> The Moon is blue...
>
> I, errr, agree with Rainer here, more for his second reason
> that for his first.
>
> I am always looking to optimize for maintenance.
Using single quotes because the content does not *currently* require
interpolation is not optimizing for maintenance. Optimizing for
maintenance would require you to predict how the usage is likely to change
in the future, and using whatever style of quotes is less likely to need to
change under that theory of the future.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Tue, 11 Oct 2011 02:26:48 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <ZoKdnYWiWp0lcg7TnZ2dnUVZ5jGdnZ2d@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 3516
***************************************
