[31327] in Perl-Users-Digest
Perl-Users Digest, Issue: 2572 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Aug 28 06:09:41 2009
Date: Fri, 28 Aug 2009 03:09:06 -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, 28 Aug 2009 Volume: 11 Number: 2572
Today's topics:
Re: DBI (with Oracle) 'out of memory' error <dn.perl@gmail.com>
differences between find2perl and find <gerhard_ulrike@yahoo.de>
Re: help on regular expression <derykus@gmail.com>
Re: help on regular expression sln@netherlands.com
Re: help on regular expression <jurgenex@hotmail.com>
Re: help on regular expression <pathexplorer@gmail.com>
Re: help on regular expression <uri@StemSystems.com>
Re: help on regular expression <uri@StemSystems.com>
Re: help on regular expression <tadmc@seesig.invalid>
Re: help on regular expression <jurgenex@hotmail.com>
Re: help on regular expression <someone@example.com>
Re: help on regular expression <derykus@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Test::Simple etc ... do you leave them in the finished <news@lawshouse.org>
Re: Test::Simple etc ... do you leave them in the finis <smallpond@juno.com>
Re: Test::Simple etc ... do you leave them in the finis <glex_no-spam@qwest-spam-no.invalid>
Re: Test::Simple etc ... do you leave them in the finis <news@lawshouse.org>
Re: windows one liner to output unix line feed <shambo_p@yahoo.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 28 Aug 2009 00:55:09 -0700 (PDT)
From: "dn.perl@gmail.com" <dn.perl@gmail.com>
Subject: Re: DBI (with Oracle) 'out of memory' error
Message-Id: <059afc4e-98dc-4943-9d51-e9bfe2a10fa9@l35g2000pra.googlegroups.com>
On Aug 27, 10:21=A0am, "Peter J. Holzer" <hjp-usen...@hjp.at> wrote:
> On 2009-08-27 09:12, dn.p...@gmail.com <dn.p...@gmail.com> wrote:
>
> Hashes need a lot of memory. With 280k hash keys, I estimate that your
> hash needs at least 60 MB. If your hash has multiple levels, it can be a
> lot more.
>
> How much memory does your script use just before it runs out of memory?
> Is it near the available virtual memory? Do you have any resource limits
> set?
>
I do not know how much memory my script was using before crashing, and
do not even know how to find it out. But your answer helped because I
was using a hash with 300,000 keys and each key had sub-levels.
$$rh_result{from_queue001}{to_queue}{admin_name}{count} =3D 4
... to ...
$$rh_result{from_queue300_001}{to_queue}{admin_name}{count} =3D 10.
Now I am deleting a key after its relevance is over.
And the script is not crashing.
> > What might be wrong? If I can keep the hash-size down (deal with a
> > key, complete all calculations assoiated with that key, then undef
> > it), will it help?
>
> Yes, that will help. But if you can process your data one key at a time,
> why store them in a hash in the first place?
>
Because each from_queue may have more than one entries assigned to it
and I can do calculations about that queue only after all the entries
are read. And I just prefer to store the data in a hash rather than
array.
my last_queue =3D "" ;
while(my @row =3D fetchrow_array) {
my $current_queue =3D $row[0] ;
populate $$rh_result($current_queue) ;
if( $current_queue ne $last_queue and $last_queue ne "" ) {
do-stuff about $$rh_result($last_queue) ;
NOW added: delete $$rh_result($current_queue) ;
}
$last_queue =3D $current_queue ;
}
do-stuff about $last_queue if $last_queue ne "" ;
The script was working without a hitch for 2-3 months before the
recent crash. But such problems help in understanding better how the
whole thing works.
Thanks for the responses.
------------------------------
Date: Thu, 27 Aug 2009 23:53:55 -0700 (PDT)
From: GU <gerhard_ulrike@yahoo.de>
Subject: differences between find2perl and find
Message-Id: <bfc2e6d4-cc2e-4c1b-b00c-97f9cddabc81@d38g2000yqi.googlegroups.com>
first of all i don't know if this is the proper group to discuss this
problem, but i can't find a better one.....
I'm using "SunOS h213 5.9 Generic_122300-29 sun4u sparc SUNW,Sun-
Fire-15000" (uname -a) and perl v5.6.1 and want to copy a lot of files
to a remote host. So i'm looking up for those files using find:
rsync -avz `find * -prune -type d -mtime -30|grep -v archive`
user@remote:dir
To add some funtionality (logging, mail if completed e.g) i'd like to
do this with perl.
Now i gonna try to convert find to a perl script using find2perl.....
and will have some problems:
gm@h213:/tmp ># redirect STDERR to avoid warnings caused by
permissions
gm@h213:/tmp >find * -prune -type d -mtime -30 2>/dev/null | tail -2
tmpdir.21790
tmpdir.27721
gm@h213:/tmp >
gm@h213:/tmp >find2perl -prune -type d -mtime -30 | perl
Found = in conditional, should be == at - line 26.
gm@h213:/tmp >
line 26 is that one with prune-check, but if using only -prune those
error does not occur (but i still have different results)
gm@h213:/tmp >find * -prune 2>/dev/null | tail -2
wkz_adj_maf
wkz_adj_rep.csv
gm@h213:/tmp >find2perl -prune | perl
gm@h213:/tmp >
One solution for me is to glob "*". As far as i can see glob "*" and
`find * -prune` will produce the same output. So i will be able to
find the files i need by 'grep {(-d $_ && (int(-M $_) <30))} glob "*"'
But that's not that what i want to use. If i've tools like find2perl i
wanna use those ones.
So what's the problem and how can i use the find2perl-result.
Do you know what's to do?
Thanks
gerhard
p.s. enclose the output of 'find2perl * -prune -type d -mtime -30'
gm@h213:/tmp >find2perl * -prune -type d -mtime -30
#! /usr/local/bin/perl -w
eval 'exec /usr/local/bin/perl -S $0 ${1+"$@"}'
if 0; #$running_under_some_shell
use strict;
use File::Find ();
# Set the variable $File::Find::dont_use_nlink if you're using AFS,
# since AFS cheats.
# for the convenience of &wanted calls, including -eval statements:
use vars qw/*name *dir *prune/;
*name = *File::Find::name;
*dir = *File::Find::dir;
*prune = *File::Find::prune;
# Traverse desired filesystems
File::Find::find({wanted => \&wanted}, **** list of files **** );
exit;
sub wanted {
my ($dev,$ino,$mode,$nlink,$uid,$gid);
($File::Find::prune = 1) &&
(($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
-d _ &&
(int(-M _) < 30);
}
gm@h213:/tmp >
------------------------------
Date: Thu, 27 Aug 2009 12:37:16 -0700 (PDT)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: help on regular expression
Message-Id: <f162152d-bc44-4091-b0e1-9a77fae646ea@y10g2000prg.googlegroups.com>
On Aug 26, 10:36=C2=A0pm, Tao Li <pathexplo...@gmail.com> wrote:
> I have been thinking the problem for a while, please help me.
>
> There is a log file. Its format is like this:
>
> send ........
> send ........
> ................
> ............
> send..........
> ...................
> ................
> send..........
> heartbeat..........
> ...............
> send........
> ...........
> .........
> send..........
> send.........
> send..........
> heartbeat..........
> ....
> send...
> .....
> heatbeat....
> ....
>
> I want to find all the "send line" before "heartbeat line"=EF=BC=8C
>
> send...
> send...
> heartbeat...
>
> doesn't include anything like this:
>
> send...
> .....
> send...
> heartbeat..........
If you don't mind capturing hits from the bottom of the
log first, you could use File::ReadBackwards (which is o
ften useful for reading logfiles):
use File::ReadBackwards;
my $bw =3D File::ReadBackwards->new('/path/filename' )
or die $!;
my $heartbeat;
while ( $_ =3D $bw->readline ) {
/^heartbeat/ and $heartbeat =3D 1 and next;
($heartbeat and /^send/ and print) or $heartbeat =3D 0;
}
--
Charles DeRykus
------------------------------
Date: Thu, 27 Aug 2009 13:58:50 -0700
From: sln@netherlands.com
Subject: Re: help on regular expression
Message-Id: <kqsd95prvf8pcdei13n8n1f7n2u2qln184@4ax.com>
On Wed, 26 Aug 2009 22:37:31 -0700 (PDT), Tao Li <pathexplorer@gmail.com> wrote:
>if you can do it with one-liner, that would be wonderful.
>
>On Aug 27, 12:36 am, Tao Li <pathexplo...@gmail.com> wrote:
>> I have been thinking the problem for a while, please help me.
>>
>> There is a log file. Its format is like this:
>>
>> send ........
>> send ........
>> ................
>> ............
>> send..........
>> ...................
>> ................
>> send..........
>> heartbeat..........
>> ...............
>> send........
>> ...........
>> .........
>> send..........
>> send.........
>> send..........
>> heartbeat..........
>> ....
>> send...
>> .....
>> heatbeat....
>> ....
>>
>> I want to find all the "send line" before "heartbeat line"?
>>
>> send...
>> send...
>> heartbeat...
>>
>> doesn't include anything like this:
>>
>> send...
>> .....
>> send...
>> heartbeat..........
print "\n",$cnt++,"\n",@{[split /send/]},"\n" for $data=~/((?:^send.*?\n)+(?=heartbeat))/mg;
-sln
------------------------------
Date: Thu, 27 Aug 2009 16:27:30 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: help on regular expression
Message-Id: <bf5e955arsnujp904il5pk5o0i3p77ongr@4ax.com>
"C.DeRykus" <derykus@gmail.com> wrote:
>On Aug 26, 10:36 pm, Tao Li <pathexplo...@gmail.com> wrote:
>> There is a log file. Its format is like this:
[...]
>> I want to find all the "send line" before "heartbeat line"?
>
>If you don't mind capturing hits from the bottom of the
>log first, you could use File::ReadBackwards (which is o
>ften useful for reading logfiles):
Neat idea!
And if the sequence is important and the hit list not too large, then he
could store all hits in an array and then reverse() the array before
printing it. Or printing the array from the rear.
jue
------------------------------
Date: Thu, 27 Aug 2009 16:29:46 -0700 (PDT)
From: Tao Li <pathexplorer@gmail.com>
Subject: Re: help on regular expression
Message-Id: <1e6fbd46-c3e1-408d-910f-a2d1958bf159@24g2000yqm.googlegroups.com>
Thanks for all of your replies.
I found the RE solution,
#!/usr/bin/perl
undef $/;
while ( <> ) {
while ( /(^send(.*)\n)+(^heartbeat(.*)\n)/mg ) {
print $&;
}
}
However I think John's solution is much more decent. Thank you.
On Aug 27, 1:18 am, "John W. Krahn" <some...@example.com> wrote:
> Tao Li wrote:
> > I have been thinking the problem for a while, please help me.
>
> > There is a log file. Its format is like this:
>
> > send ........
> > send ........
> > ................
> > ............
> > send..........
> > ...................
> > ................
> > send..........
> > heartbeat..........
> > ...............
> > send........
> > ...........
> > .........
> > send..........
> > send.........
> > send..........
> > heartbeat..........
> > ....
> > send...
> > .....
> > heatbeat....
> > ....
>
> > I want to find all the "send line" before "heartbeat line",
>
> > send...
> > send...
> > heartbeat...
>
> > doesn't include anything like this:
>
> > send...
> > .....
> > send...
> > heartbeat..........
>
> perl -ne'
> if ( /^send/ ) { push @buff, $_ }
> elsif ( /^heartbeat/ ) { print @buff, $_ }
> else { @buff = () }
> '
>
> John
> --
> Those people who think they know everything are a great
> annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Thu, 27 Aug 2009 20:08:11 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: help on regular expression
Message-Id: <87vdk8ztp0.fsf@quad.sysarch.com>
>>>>> "JE" == Jürgen Exner <jurgenex@hotmail.com> writes:
JE> "C.DeRykus" <derykus@gmail.com> wrote:
>> On Aug 26, 10:36 pm, Tao Li <pathexplo...@gmail.com> wrote:
>>> There is a log file. Its format is like this:
JE> [...]
>>> I want to find all the "send line" before "heartbeat line"?
>>
>> If you don't mind capturing hits from the bottom of the
>> log first, you could use File::ReadBackwards (which is o
>> ften useful for reading logfiles):
JE> Neat idea!
JE> And if the sequence is important and the hit list not too large, then he
JE> could store all hits in an array and then reverse() the array before
JE> printing it. Or printing the array from the rear.
why reverse? instead of pushing, use unshift.
uri (author of File::ReadBackwards).
PS. amusing that i still have never used that module but it is popular!
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Thu, 27 Aug 2009 20:12:48 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: help on regular expression
Message-Id: <87r5uwzthb.fsf@quad.sysarch.com>
>>>>> "TL" == Tao Li <pathexplorer@gmail.com> writes:
TL> Thanks for all of your replies.
TL> I found the RE solution,
TL> undef $/;
bah!
TL> while ( <> ) {
that while is useless as it just reads the whole file into $_ the first time.
TL> while ( /(^send(.*)\n)+(^heartbeat(.*)\n)/mg ) {
don't grab when you mean to only group.
TL> print $&;
learn about why $& is bad for your perl speed.
you wanted a one liner.
(untested)
use File::Slurp ;
print read_file( shift @ARGV ) =~ /((?:^send.*)\n)+^heartbeat.*\n)/mg ;
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Thu, 27 Aug 2009 19:22:02 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: help on regular expression
Message-Id: <slrnh9e86d.33k.tadmc@tadmc30.sbcglobal.net>
Tao Li <pathexplorer@gmail.com> wrote:
> undef $/;
>
> while ( <> ) {
How many iterations to you expect from that loop?
A loop that must iterate exactly one time is an unlooping loop!
You are loopy to write such code...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 27 Aug 2009 17:34:00 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: help on regular expression
Message-Id: <0f9e959l5r8m5c25lmv4kacaikmb6adia5@4ax.com>
"Uri Guttman" <uri@StemSystems.com> wrote:
>>>>>> "JE" == Jürgen Exner <jurgenex@hotmail.com> writes:
>
> JE> "C.DeRykus" <derykus@gmail.com> wrote:
> >> On Aug 26, 10:36 pm, Tao Li <pathexplo...@gmail.com> wrote:
> >>> There is a log file. Its format is like this:
> JE> [...]
> >>> I want to find all the "send line" before "heartbeat line"?
> >>
> >> If you don't mind capturing hits from the bottom of the
> >> log first, you could use File::ReadBackwards (which is o
> >> ften useful for reading logfiles):
>
> JE> Neat idea!
>
> JE> And if the sequence is important and the hit list not too large, then he
> JE> could store all hits in an array and then reverse() the array before
> JE> printing it. Or printing the array from the rear.
>
>why reverse? instead of pushing, use unshift.
True, that's even better.
jue
------------------------------
Date: Thu, 27 Aug 2009 18:49:18 -0700
From: "John W. Krahn" <someone@example.com>
Subject: Re: help on regular expression
Message-Id: <tIGlm.75455$sC1.57757@newsfe17.iad>
Tad J McClellan wrote:
> Tao Li <pathexplorer@gmail.com> wrote:
>
>> undef $/;
>>
>> while ( <> ) {
>
>
> How many iterations to you expect from that loop?
Depends on how many file names are in @ARGV. :-)
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
Date: Thu, 27 Aug 2009 22:13:57 -0700 (PDT)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: help on regular expression
Message-Id: <655e2f70-ae93-4ae3-88a5-dcbf18e7795e@b25g2000prb.googlegroups.com>
On Aug 27, 4:27=A0pm, J=FCrgen Exner <jurge...@hotmail.com> wrote:
> "C.DeRykus" <dery...@gmail.com> wrote:
> >On Aug 26, 10:36=A0pm, Tao Li <pathexplo...@gmail.com> wrote:
> >> There is a log file. Its format is like this:
> [...]
> >> I want to find all the "send line" before "heartbeat line"?
>
> >If you don't mind capturing hits from the bottom of the
> >log first, you could use File::ReadBackwards (which is o
> >ften useful for reading logfiles):
>
> Neat idea!
>
> And if the sequence is important and the hit list not too large, then he
> could store all hits in an array and then reverse() the array before
> printing it. Or printing the array from the rear.
Thanks, I've found Uri's module useful several times.
--
Charles DeRykus
------------------------------
Date: Fri, 28 Aug 2009 02:20:10 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <f8ednZufn5m3GArXnZ2dnUVZ_j2dnZ2d@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.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 27 Aug 2009 23:07:57 +0100
From: Henry Law <news@lawshouse.org>
Subject: Test::Simple etc ... do you leave them in the finished program?
Message-Id: <gemdnanudrQmngrXnZ2dnUVZ8n2dnZ2d@giganews.com>
I've searched and read and faq'd and found all sorts of useful stuff on
writing test statements for Test::Simple and Test::More and I reckon I
know how to do that. The thing I can't find is the strategy for using
them.
I can put "use Test::whichever;" at the top of my program and lard it,
and the modules, with the relevant "ok" statements: but do I leave them
there when the program's debugged and ready for deployment? If not, how
do I disable them? Surely I don't have to cut them all out, with the
risk of introducing bugs (and put them all back in again in version 2?
Nah, doesn't make sense).
Would someone point me in the right direction please?
--
Henry Law Manchester, England
------------------------------
Date: Thu, 27 Aug 2009 18:32:21 -0400
From: Steve C <smallpond@juno.com>
Subject: Re: Test::Simple etc ... do you leave them in the finished program?
Message-Id: <h771i9$i8f$1@news.eternal-september.org>
Henry Law wrote:
> I've searched and read and faq'd and found all sorts of useful stuff on
> writing test statements for Test::Simple and Test::More and I reckon I
> know how to do that. The thing I can't find is the strategy for using
> them.
>
> I can put "use Test::whichever;" at the top of my program and lard it,
> and the modules, with the relevant "ok" statements: but do I leave them
> there when the program's debugged and ready for deployment? If not, how
> do I disable them? Surely I don't have to cut them all out, with the
> risk of introducing bugs (and put them all back in again in version 2?
> Nah, doesn't make sense).
>
> Would someone point me in the right direction please?
>
Download almost any of the source modules from CPAN and unpack it.
You will find a subdirectory 't' with the test code in it separate
from the production code. Generally, the test code wraps around the
production code when 'make test' runs.
------------------------------
Date: Thu, 27 Aug 2009 17:33:22 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Test::Simple etc ... do you leave them in the finished program?
Message-Id: <4a96ff01$0$1324$815e3792@news.qwest.net>
Henry Law wrote:
> I've searched and read and faq'd and found all sorts of useful stuff on
> writing test statements for Test::Simple and Test::More and I reckon I
> know how to do that. The thing I can't find is the strategy for using
> them.
>
> I can put "use Test::whichever;" at the top of my program and lard it,
> and the modules, with the relevant "ok" statements: but do I leave them
> there when the program's debugged and ready for deployment? If not, how
> do I disable them? Surely I don't have to cut them all out, with the
> risk of introducing bugs (and put them all back in again in version 2?
> Nah, doesn't make sense).
>
> Would someone point me in the right direction please?
>
You create the test scripts and include them with your distribution.
Typically you'd use ExtUtils::MakeMaker, put the test scripts
in ./t, and after building your Makefile (perl Makefile.PL) your
test programs will be executed when you run a 'make test'. You
don't put Test::Simple into your programs/modules, only in your tests.
The tests would 'use YourModule', instantiate things, call methods, make
sure get/set works, etc. When a 'make install' is performed, the
various modules/programs are installed and the test scripts don't
get installed.
------------------------------
Date: Fri, 28 Aug 2009 09:28:54 +0100
From: Henry Law <news@lawshouse.org>
Subject: Re: Test::Simple etc ... do you leave them in the finished program?
Message-Id: <ZY-dneOWobjZCArXnZ2dnUVZ8s2dnZ2d@giganews.com>
J. Gleixner wrote:
> Henry Law wrote:
>> The thing I can't find is the strategy
>> for using them.
> The tests would 'use YourModule', instantiate things, call methods, make
Thank you (and also thanks to Steve C); I understand now. I had the
wrong idea altogether, and was thinking of "ok" as a kind of "assert"
statement which was included inline in the code.
One last point of clarification. Am I right then in thinking that I can
use Test::whatever for _modules_ that I write, but not for the mainline
code which uses them? If so that looks like something of a limitation.
--
Henry Law Manchester, England
------------------------------
Date: Thu, 27 Aug 2009 11:58:06 -0700 (PDT)
From: boman <shambo_p@yahoo.com>
Subject: Re: windows one liner to output unix line feed
Message-Id: <26617df5-9170-4b5c-82d3-0a641315fbdc@p15g2000vbl.googlegroups.com>
Chris's suggestion worked:
perl -pi.orig -e "binmode(ARGVOUT); s|foo|bar|g" myfile.txt
The original line endings are Unix, and when the file is run thru this
oneliner on Windows, the line endings remain as Unix.
According to perl -v on my system, I'm running v5.8.8 built for
MSWin32-x86-multi-thread.
I appreciate the amount of attention this little issue received, I
certainly have learned a lot from this discussion.
My sincere thanks to you all.
best,
Bo
------------------------------
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.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
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 V11 Issue 2572
***************************************
