[32256] in Perl-Users-Digest
Perl-Users Digest, Issue: 3523 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 19 16:09:53 2011
Date: Wed, 19 Oct 2011 13:09:37 -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, 19 Oct 2011 Volume: 11 Number: 3523
Today's topics:
Re: File Rotation <bugbear@trim_papermule.co.uk_trim>
Re: File Rotation <ben@morrow.me.uk>
Re: File Rotation <bugbear@trim_papermule.co.uk_trim>
Re: File Rotation <ben@morrow.me.uk>
File::Copy::copy With File Handles <hsomob1999@yahoo.com>
Re: File::Copy::copy With File Handles <ben@morrow.me.uk>
Re: File::Copy::copy With File Handles <hsomob1999@yahoo.com>
Re: help with pipe dihedral88888@googlemail.com
Imager module to resize a GIF <jwcarlton@gmail.com>
Re: Imager module to resize a GIF <ben@morrow.me.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
search counterpart to sort? <bugbear@trim_papermule.co.uk_trim>
Re: search counterpart to sort? <jurgenex@hotmail.com>
we also want to do... <r@thevoid1.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 17 Oct 2011 15:28:59 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: File Rotation
Message-Id: <_ICdnd-7jNQ2pgHTnZ2dnUVZ7sWdnZ2d@brightview.co.uk>
1dg618 wrote:
> On Oct 16, 11:26 am, 1dg618<1dg...@gmail.com> wrote:
>> On Oct 16, 11:10 am, Henry Law<n...@lawshouse.org> wrote:
>>
>>
>>
>>
>>
>>> On 16/10/11 15:43, 1dg618 wrote:
>>
>>>> Is there a way to rotate the log files each time the process runs
>>>> using the existing functionality via the configuration? If the process
>>>> has issues, the most recent log file logged the information. I can't
>>>> find a way, but, I assume, others have found a way?
>>
>>> Newsgroups these days are infested with posts which contain
>>> randomly-chosen words which mean nothing. I thought this was one of
>>> them initially but maybe it isn't.
>>
>>> Mr/Ms 1dg618 (May I call you "One d" for short?) for us to help you're
>>> going to need to be much more precise about what you're trying to do and
>>> what's not happening the way you want it to.
>>
>>> For a start, Perl programs (this is a Perl group) don't write log files
>>> unless you tell them to. Once they're written they're the property of
>>> the operating system, which may provide log-rotation functionality (UNIX
>>> does, for example).
>>
>>> And when you say "the existing functionality via the configuration",
>>> which functionality and which configuration? (And of what?)
>>
>>> CPAN contains many modules which have "log file" in their descriptive
>>> text. It's possible that one of those may do exactly what you want, but
>>> until you make clear what it is that you want we can't help you further.
>>
>>> --
>>
>>> Henry Law Manchester, England
>>
>> Sorry, using Log4Perl. I'll look for a Log4Perl user group.- Hide quoted text -
>>
>> - Show quoted text -
>
> My Log4Perl configuration rotates the log files daily. Using the
> DatePattern I can get that down to minutes. How do you get the log
> files to rotate everytime the process runs? Is there a way to do it in
> Log4Perl?
>
> my $log_conf = q/
> log4perl.category = INFO, Logfile
> log4perl.appender.Logfile=Log::Dispatch::FileRotate
> log4perl.appender.Logfile.max=10
> log4perl.appender.Logfile.mode=append
> log4perl.appender.Logfile.filename=sub { return get_log_fn(); }
> log4perl.appender.Logfile.DatePattern=yyyy-MM-dd
> log4perl.appender.Logfile.TZ=CST
>
> log4perl.appender.Logfile.layout=Log::Log4perl::Layout::PatternLayout
> log4perl.appender.Logfile.layout.ConversionPattern=%d %M %L> %p -
> %m%n
> /;
>
> Otherwise, I'll have to use Herny's suggestion and write my own code
> to do it.
If you just want a log file for each run (process id) you could use
Log::Log4perl::Appender::File and set the filename to $$.log or similar.
BugBear
------------------------------
Date: Mon, 17 Oct 2011 18:56:29 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: File Rotation
Message-Id: <pqadnZRWdrMwXQHTnZ2dnUVZ7ridnZ2d@bt.com>
Quoth bugbear <bugbear@trim_papermule.co.uk_trim>:
> 1dg618 wrote:
> >
> > My Log4Perl configuration rotates the log files daily. Using the
> > DatePattern I can get that down to minutes. How do you get the log
> > files to rotate everytime the process runs? Is there a way to do it in
> > Log4Perl?
> >
> > my $log_conf = q/
> > log4perl.category = INFO, Logfile
> > log4perl.appender.Logfile=Log::Dispatch::FileRotate
> > log4perl.appender.Logfile.max=10
> > log4perl.appender.Logfile.mode=append
> > log4perl.appender.Logfile.filename=sub { return get_log_fn(); }
> > log4perl.appender.Logfile.DatePattern=yyyy-MM-dd
> > log4perl.appender.Logfile.TZ=CST
> >
> > log4perl.appender.Logfile.layout=Log::Log4perl::Layout::PatternLayout
> > log4perl.appender.Logfile.layout.ConversionPattern=%d %M %L> %p -
> > %m%n
> > /;
> >
> > Otherwise, I'll have to use Herny's suggestion and write my own code
> > to do it.
>
> If you just want a log file for each run (process id) you could use
> Log::Log4perl::Appender::File and set the filename to $$.log or similar.
Process ids are not unique once your process has exitted. If you want a
guaranteed unique name you need "$$." . time() followed by sleeping for a
second, but names like that aren't exactly human-friendly. There are
other forms of name that are reliably unique, such as UUIDs (if you
generate them right), but none are terribly pretty.
If you can rely on O_EXCL working properly you can simply start at 0.log
and keep opening files with O_EXCL (and *without* O_CREAT) until you get
one that succeeds. Once you've 'claimed' that filename you can even
close the file and let Log4Perl reopen it, though it would probably be
easier to just pass the handle to Log::Dispatch::Handle.
If you can't the problem isn't soluble in general, without races, unless
you use guaranteed-unique names like those above. Neither readdir nor
stat are helpful for deciding if a filename has already been used since
there's a race between checking and creating. Locking doesn't help since
you need other instances to leave your logfile alone even after you've
exitted. The best you can do is have every instance lock a single
(permanently empty) lockfile while it pokes about deciding on a
filename, which is terribly hard work.
Ben
------------------------------
Date: Tue, 18 Oct 2011 10:00:54 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: File Rotation
Message-Id: <FqqdnUcmasna3QDTnZ2dnUVZ7r-dnZ2d@brightview.co.uk>
Ben Morrow wrote:
>
> Quoth bugbear<bugbear@trim_papermule.co.uk_trim>:
>> 1dg618 wrote:
>>>
>>> My Log4Perl configuration rotates the log files daily. Using the
>>> DatePattern I can get that down to minutes. How do you get the log
>>> files to rotate everytime the process runs? Is there a way to do it in
>>> Log4Perl?
>>>
>>> my $log_conf = q/
>>> log4perl.category = INFO, Logfile
>>> log4perl.appender.Logfile=Log::Dispatch::FileRotate
>>> log4perl.appender.Logfile.max=10
>>> log4perl.appender.Logfile.mode=append
>>> log4perl.appender.Logfile.filename=sub { return get_log_fn(); }
>>> log4perl.appender.Logfile.DatePattern=yyyy-MM-dd
>>> log4perl.appender.Logfile.TZ=CST
>>>
>>> log4perl.appender.Logfile.layout=Log::Log4perl::Layout::PatternLayout
>>> log4perl.appender.Logfile.layout.ConversionPattern=%d %M %L> %p -
>>> %m%n
>>> /;
>>>
>>> Otherwise, I'll have to use Herny's suggestion and write my own code
>>> to do it.
>>
>> If you just want a log file for each run (process id) you could use
>> Log::Log4perl::Appender::File and set the filename to $$.log or similar.
>
> Process ids are not unique once your process has exitted.
Good point.
> If you want a
> guaranteed unique name you need "$$." . time() followed by sleeping for a
> second, but names like that aren't exactly human-friendly.
Ah - or use hires time, and a short sleep?
Or (if you're that way inclined) just stick a random number on.
That would make a clash "unlikely"
This is a debugging requiremnt, not real time unattended medical software,
so "gold plated" functionality isn't needed.
BugBear
------------------------------
Date: Tue, 18 Oct 2011 11:31:09 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: File Rotation
Message-Id: <6_OdnapVg4ZQNADTnZ2dnUVZ8lCdnZ2d@bt.com>
Quoth bugbear <bugbear@trim_papermule.co.uk_trim>:
> Ben Morrow wrote:
> >
> > Process ids are not unique once your process has exitted.
>
> Good point.
>
> > If you want a
> > guaranteed unique name you need "$$." . time() followed by sleeping for a
> > second, but names like that aren't exactly human-friendly.
>
> Ah - or use hires time, and a short sleep?
Yes, though that's making the already-nasty name even longer. Strictly
speaking you don't have to sleep for a second either, you just have to
make sure your process doesn't exit for at least a second. In perl you
could do something like
my $stamp = $^T;
sleep 1 unless time() - $^T > 1;
> Or (if you're that way inclined) just stick a random number on.
>
> That would make a clash "unlikely"
>
> This is a debugging requiremnt, not real time unattended medical software,
> so "gold plated" functionality isn't needed.
Yes, you can get good-enough-from-now-until-the-end-of-the-Universe
uniqueness with a surprisingly little amount of decent randomness.
(That's what secure checksums are based on, after all.) It's still worth
being careful and using O_CREAT|O_EXCL, though, just because you *know*
the one time it goes wrong will be the log you really needed to see...
(My previous post had an error: you *must* use O_CREAT, not must not.)
Ben
------------------------------
Date: Tue, 18 Oct 2011 13:08:47 -0700 (PDT)
From: MaggotChild <hsomob1999@yahoo.com>
Subject: File::Copy::copy With File Handles
Message-Id: <965453fe-a869-4576-a599-251533712299@27g2000prq.googlegroups.com>
The documentation for File::Copy warns against using file handles as
arguments:
Note that passing in files as handles instead of names may lead
to
loss of information on some operating systems; it is
recommended
that you use file names whenever possible.
Does this refer to handles created with the older FileHandle module
(which is used in the module's synopsis), IO::Handle subclasses, or
both?
In either case what's the issue with handles that may lead to data
loss?
------------------------------
Date: Tue, 18 Oct 2011 16:39:54 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: File::Copy::copy With File Handles
Message-Id: <kuadna6P9Iy3bwDTnZ2dnUVZ8i6dnZ2d@bt.com>
Quoth MaggotChild <hsomob1999@yahoo.com>:
> The documentation for File::Copy warns against using file handles as
> arguments:
>
> Note that passing in files as handles instead of names may lead
> to
> loss of information on some operating systems; it is
> recommended
> that you use file names whenever possible.
>
> Does this refer to handles created with the older FileHandle module
> (which is used in the module's synopsis), IO::Handle subclasses, or
> both?
Both, or indeed any other way of creating a filehandle.
> In either case what's the issue with handles that may lead to data
> loss?
On non-Unix systems (more specifically, on Win32 and I believe VMS)
File::Copy calls the system file-copy routine (CopyFile on Win32) if you
pass it filenames. This will preserve things like ACLs, extended
attributes, NTFS streams, and so on. If you pass it handles it can't do
that, so it only preserves the Unixy permission bits you get from stat.
Ben
------------------------------
Date: Wed, 19 Oct 2011 10:19:57 -0700 (PDT)
From: MaggotChild <hsomob1999@yahoo.com>
Subject: Re: File::Copy::copy With File Handles
Message-Id: <b14dfad7-201b-4f3e-ba45-022a07d8e10c@p27g2000prp.googlegroups.com>
On Oct 18, 2:39=A0pm, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth MaggotChild <hsomob1...@yahoo.com>:
>
> > The documentation for File::Copy warns against using file handles as
> > arguments:
>
> > =A0 =A0 =A0 =A0Note that passing in files as handles instead of names m=
ay lead
> > to loss of information
> On non-Unix systems (more specifically, on Win32 and I believe VMS)
> File::Copy calls the system file-copy routine (CopyFile on Win32) if you
> pass it filenames. This will preserve things like ACLs, extended
> attributes, NTFS streams, and so on.
I had ignored the obvious and interpreted "loss of information" to
mean loss of the file's data, not necessarily metadata. Which lead to
me to believe that for some subtle reason File::Copy couldn't be used
reliably copy data streams. Thanks for the clarification.
------------------------------
Date: Mon, 17 Oct 2011 07:12:01 -0700 (PDT)
From: dihedral88888@googlemail.com
Subject: Re: help with pipe
Message-Id: <22925238.1535.1318860721937.JavaMail.geo-discussion-forums@prng5>
I am wondering if the compression zlib in python could be upgraded to the iterable input and output for different compression algorithm experiments that will outperform the speed of pipelines for all i/o of big chunks.
This is my suggestion. Maybe this is good for talented young to try to gain insights in python modules by just improving an existed one.
------------------------------
Date: Tue, 18 Oct 2011 22:58:34 -0700 (PDT)
From: Jason C <jwcarlton@gmail.com>
Subject: Imager module to resize a GIF
Message-Id: <3578932.997.1319003914911.JavaMail.geo-discussion-forums@yqja14>
I have a web script that resizes images uploaded by the site visitor to predetermined dimensions. This works fine for JPG and PNG, but not for GIF.
I've just about copied the script verbatim from CPAN for testing, but getwidth(), etc, all return nothing:
#!/usr/bin/perl
#
use CGI::Carp qw(fatalsToBrowser);
use Imager;
use strict;
use warnings;
my $img = Imager->new();
$img->open(file=>'/home/myacct/www/myimage.gif', type=>'gif')
or die "not read";
print "Content-type: text/html\n\n";
if (-e "/home/myacct/www/myimage.gif") {
print "Image information:\n";
print " Width: ". $img->getwidth() ."\n";
print " Height: ". $img->getheight() ."\n";
print " Type: ". $img->type() ."\n";
}
else { print "not found"; }
exit;
http://search.cpan.org/~tonyc/Imager-0.85/lib/Imager/ImageTypes.pod
It prints "Image information", etc, so the image is found... it's just not being read.
I do have giflib installed on the server. I wasn't sure if I installed it before or after Imager, though, so I uninstalled Imager and reinstalled it, but that had no impact.
If any of you are familiar with Imager, is there something else that I need to do in order to get it to recognize GIF files?
------------------------------
Date: Wed, 19 Oct 2011 07:20:50 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Imager module to resize a GIF
Message-Id: <opidnS4sYKg_XQPTnZ2dnUVZ8tGdnZ2d@bt.com>
Quoth comp.lang.perl.misc@googlegroups.com:
> I have a web script that resizes images uploaded by the site visitor to
> predetermined dimensions. This works fine for JPG and PNG, but not for
> GIF.
>
> I've just about copied the script verbatim from CPAN for testing, but
> getwidth(), etc, all return nothing:
>
> #!/usr/bin/perl
> #
> use CGI::Carp qw(fatalsToBrowser);
> use Imager;
> use strict;
> use warnings;
>
> my $img = Imager->new();
> $img->open(file=>'/home/myacct/www/myimage.gif', type=>'gif')
> or die "not read";
>
> print "Content-type: text/html\n\n";
>
> if (-e "/home/myacct/www/myimage.gif") {
> print "Image information:\n";
> print " Width: ". $img->getwidth() ."\n";
> print " Height: ". $img->getheight() ."\n";
> print " Type: ". $img->type() ."\n";
> }
>
> else { print "not found"; }
> exit;
>
> http://search.cpan.org/~tonyc/Imager-0.85/lib/Imager/ImageTypes.pod
>
> It prints "Image information", etc, so the image is found... it's just
> not being read.
>
> I do have giflib installed on the server. I wasn't sure if I installed
> it before or after Imager, though, so I uninstalled Imager and
> reinstalled it, but that had no impact.
>
> If any of you are familiar with Imager, is there something else that I
> need to do in order to get it to recognize GIF files?
What you have there works for me, here. Do you, in fact, have a .pm and
a .so for Imager::File::GIF? If you run ldd against the .so (which
should be somewhere like /usr/local/lib/perl5/site_perl/5.12.4/
amd64-freebsd/auto/Imager/File/GIF/GIF.so) are all the libraries it
needs found?
Is there something wrong with your gif file? There is a file called
GIF/testimg/expected.gif in the Imager distribution; since that's the
file Imager uses to make sure giflib works, you could try that (it
should be 16x16px).
Ben
------------------------------
Date: Tue, 18 Oct 2011 02:27:36 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <4tudncgNj_b1twDTnZ2dnUVZ5sCdnZ2d@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: Tue, 18 Oct 2011 11:03:37 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: search counterpart to sort?
Message-Id: <QuudnQP375hk0wDTnZ2dnUVZ7r6dnZ2d@brightview.co.uk>
Perl (for ages) has had a helpful sort function
built in, based on a comparison subroutine.
Is there a corresponding search function, either as core,
or a commonly available module?
I've looked around, but come up empty, which I
find surprising.
And, yes, I could code binary search myself. ;-)
BugBear
------------------------------
Date: Tue, 18 Oct 2011 03:13:58 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: search counterpart to sort?
Message-Id: <22kq97pirrdds3h007kr6nbevulskrknid@4ax.com>
bugbear <bugbear@trim_papermule.co.uk_trim> wrote:
>Perl (for ages) has had a helpful sort function
>built in, based on a comparison subroutine.
>
>Is there a corresponding search function, either as core,
>or a commonly available module?
How about grep()? Just like sort() it takes a list and an
expression/block as arguments and returns a list which contains all the
sorted elements resp. all the 'found' elements.
jue
------------------------------
Date: Mon, 17 Oct 2011 18:32:02 -0600
From: robin <r@thevoid1.net>
Subject: we also want to do...
Message-Id: <j7ihe6$43f$1@speranza.aioe.org>
support the u.s. government suppive thereof protests.
:-)
sdfjklsdfjklsdcf
-r
------------------------------
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 3523
***************************************
