[25702] in Perl-Users-Digest
Perl-Users Digest, Issue: 7943 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 5 03:05:31 2005
Date: Tue, 5 Apr 2005 00:05:11 -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, 5 Apr 2005 Volume: 10 Number: 7943
Today's topics:
Re: [BEGINNER} Question <spamtrap@dot-app.org>
Re: Perl Embed in C++ Problem -> Urgent, please help! <jurgenex@hotmail.com>
Re: Perl Embed in C++ Problem -> Urgent, please help! sleepymish@gmail.com
Re: Perl Embed in C++ Problem -> Urgent, please help! <1usa@llenroc.ude.invalid>
Re: Perl Embed in C++ Problem -> Urgent, please help! sleepymish@gmail.com
Re: Perl Embed in C++ Problem -> Urgent, please help! <1usa@llenroc.ude.invalid>
Re: Perl Embed in C++ Problem -> Urgent, please help! <1usa@llenroc.ude.invalid>
Re: Perl Embed in C++ Problem <tadmc@augustmail.com>
Re: Please help package Search::VectorSpace; problem <tadmc@augustmail.com>
Re: Please help package Search::VectorSpace; problem <1usa@llenroc.ude.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: recursivity axel@white-eagle.invalid.uk
Regular expression question. (MENTAT)
Shell Commands (Getting PID and Timing Them) <hal@thresholddigital.com>
Re: Shell Commands (Getting PID and Timing Them) axel@white-eagle.invalid.uk
Re: Shell Commands (Getting PID and Timing Them) <joe@inwap.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 04 Apr 2005 22:54:02 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: [BEGINNER} Question
Message-Id: <voadnTevrNFWYMzfRVn-sA@adelphia.com>
soup_or_power@yahoo.com wrote:
>>>sub new {
>>> my ($self, $hash) = @_;
>>>
>>> # ------------------------------------------------------
>>> # Create new hash ref/obj ref (Copy Constructor)
>>> # ------------------------------------------------------
>>>
>>> my $type = ref($self) || $self;
>>> my $obj = ( ref $self ) ? &Storable::dclone( $self ) : { };
>>> my $new = bless $obj, $type;
>>>
>>> # ------------------------------------------------------
>>> # Initialize properties (copy $hash into $new)
>>> # ------------------------------------------------------
>>>
>>> if ($hash && ref $hash) {
>>> while ( my ($key, $value) = each %$hash ) {
>>> $new->{$key} = $value if ! ref $value;
>>> }
>>> }
>>>
>>> return $new;
>>>}
> difficult to digest the posted code. I wonder why the object is being
> cloned.
Essentially, it's a dual-purpose constructor. If it's called as a class
method, it creates a new object. If it's called as instance method, it
creates a copy of itself.
You'll find a *lot* of people who don't care much for this technique. As
you've found out, it can be confusing. It's clearer to write two methods
- a class method new() for creating new objects, and an instance method
copy() for making copies.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Tue, 05 Apr 2005 01:31:56 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <gUl4e.7137$pU5.1209@trnddc06>
sleepymish@gmail.com wrote:
> Thanks for the advice,
What advice? Please quote enough context such that people know what you are
talking about.
> but I can't edit that title now.
Has it been entered in the Library of Congress already or will you be sued
if you change the title? (Title of what BTW?)
jue
------------------------------
Date: 4 Apr 2005 18:54:13 -0700
From: sleepymish@gmail.com
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <1112666053.244718.252350@l41g2000cwc.googlegroups.com>
I was referring to what Tad McClellan said.
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Putting "urgent" in your Subject is counter-productive, it
results in *less* people seeing your question.
ie. It hurts (not helps) your chances of getting help.
--
Tad McClellan SGML consulting
t...@augustmail.com Perl programming
Fort Worth, Texas
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Anyway I found another post where someone compiled perl with C++ as
followed (below), I tried it with my code and still got the same error.
Now I'm wondering if it's a Perl problem or my compiler. Looks like
there is a C and C++ linkage problem. Anyone seen this problem before?
Here's the output from my compiling:
$ g++ -g -o p1v1 p1v1.cpp `perl -MExtUtils::Embed -e ccopts -e ldopts`
p1v1.cpp:1: error: syntax error before `{' token
In file included from /usr/lib/perl5/5.8/cygwin/CORE/perl.h:2838,
from p1v1.cpp:6:
/usr/include/ieeefp.h:185: error: previous declaration of `int
isnan(double)'
with C++ linkage
/usr/include/math.h:125: error: conflicts with new declaration with C
linkage
/usr/include/ieeefp.h:186: error: previous declaration of `int
isinf(double)'
with C++ linkage
/usr/include/math.h:126: error: conflicts with new declaration with C
linkage
/usr/include/ieeefp.h:187: error: previous declaration of `int
finite(double)'
with C++ linkage
/usr/include/math.h:127: error: conflicts with new declaration with C
linkage
/usr/include/ieeefp.h:191: error: previous declaration of `int
isnanf(float)'
with C++ linkage
/usr/include/math.h:240: error: conflicts with new declaration with C
linkage
/usr/include/ieeefp.h:192: error: previous declaration of `int
isinff(float)'
with C++ linkage
/usr/include/math.h:241: error: conflicts with new declaration with C
linkage
/usr/include/ieeefp.h:193: error: previous declaration of `int
finitef(float)'
with C++ linkage
/usr/include/math.h:242: error: conflicts with new declaration with C
linkage
In file included from p1v1.cpp:12:
helpers.h: In function `void wget_file(char*, char*)':
helpers.h:6: error: invalid conversion from `void*' to `char*'
helpers.h: In function `int get_v(int, char**, char**, char*, int*)':
helpers.h:74: error: invalid conversion from `void*' to `char*'
helpers.h:75: error: invalid conversion from `void*' to `char*'
helpers.h: In function `int get_AvgDocLen(int, int, char**, char**)':
helpers.h:345: error: invalid conversion from `void*' to `char*'
helpers.h:368: error: invalid conversion from `void*' to `char*'
helpers.h:370: error: invalid conversion from `void*' to `int*'
p1v1.cpp: In function `int main(int, char**, char**)':
p1v1.cpp:40: error: invalid conversion from `void*' to `char*'
p1v1.cpp:42: error: invalid conversion from `void*' to `char*'
p1v1.cpp:43: error: invalid conversion from `void*' to `int*'
------------------------------
Date: Tue, 05 Apr 2005 02:26:10 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <Xns962EE43C52ECAasu1cornelledu@127.0.0.1>
sleepymish@gmail.com wrote in
news:1112666053.244718.252350@l41g2000cwc.googlegroups.com:
> I was referring to what Tad McClellan said.
>
> """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Please do not make up weird quoting styles.
> Anyway I found another post where someone compiled perl with C++ as
> followed (below),
Why are you compiling Perl with C++?
I am a little baffled.
I had never tried this before, so I decided to give it a shot.
I went to the following section in the ExtUtils::Embed documentation:
http://search.cpan.org/~nwclark/perl-
5.8.6/pod/perlembed.pod#Adding_a_Perl_interpreter_to_your_C_program
I took the source code from that section, and made a minor modification
(after all, you are compiling C++, but C linkage is appropriate for Perl
code):
/* embed.cc */
#ifdef __cplusplus
extern "C" {
#include <EXTERN.h>
#include <perl.h>
static PerlInterpreter *my_perl;
}
#endif
int main(int argc, char **argv, char **env)
{
PERL_SYS_INIT3(&argc,&argv,&env);
my_perl = perl_alloc();
perl_construct(my_perl);
PL_exit_flags |= PERL_EXIT_DESTRUCT_END;
perl_parse(my_perl, NULL, argc, argv, (char **)NULL);
perl_run(my_perl);
perl_destruct(my_perl);
perl_free(my_perl);
PERL_SYS_TERM();
}
and then compiled using
asu1@Aardvark ~/src/embed
$ gcc -o embed embed.cc `perl -MExtUtils::Embed -e ccopts -e ldopts`
asu1@Aardvark ~/src/embed
$ ./embed -v
This is perl, v5.8.6 built for cygwin-thread-multi-64int
I am not sure what your problem is.
/* snipped a bunch of error messages regarding C++ linkage */
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: 4 Apr 2005 19:38:41 -0700
From: sleepymish@gmail.com
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <1112668721.379536.56680@g14g2000cwa.googlegroups.com>
A. Sinan Unur wrote:
> sleepymish@gmail.com wrote in
> news:1112666053.244718.252350@l41g2000cwc.googlegroups.com:
>
> > I was referring to what Tad McClellan said.
> >
> > """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
>
> Please do not make up weird quoting styles.
Sorry about that, I'm new to posting in google.
> /* embed.cc */
>
> #ifdef __cplusplus
> extern "C" {
> #include <EXTERN.h>
> #include <perl.h>
> static PerlInterpreter *my_perl;
> }
> #endif
>
This worked! I included the #ifdef...#endif block in my code and
everything compiled!
Thanks!
------------------------------
Date: Tue, 05 Apr 2005 02:57:51 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <Xns962EE99A813CFasu1cornelledu@127.0.0.1>
sleepymish@gmail.com wrote in news:1112668721.379536.56680
@g14g2000cwa.googlegroups.com:
>
> A. Sinan Unur wrote:
>> sleepymish@gmail.com wrote in
>> news:1112666053.244718.252350@l41g2000cwc.googlegroups.com:
>>
>> > I was referring to what Tad McClellan said.
>> >
>> > """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
>>
>> Please do not make up weird quoting styles.
>
> Sorry about that, I'm new to posting in google.
That's OK.
Google's is fairly annoying.
Thank you very much for fixing the quoting style. It is definitely
appreciated.
>> /* embed.cc */
>>
>> #ifdef __cplusplus
>> extern "C" {
>> #include <EXTERN.h>
>> #include <perl.h>
>> static PerlInterpreter *my_perl;
>> }
>> #endif
>>
>
> This worked! I included the #ifdef...#endif block in my code and
> everything compiled!
I am glad. As I said, I was a little baffled at first, because I had
never used any of these features, so mine was a complete shot in the
dark. Glad it somehow ended up being useful
Good luck.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Tue, 05 Apr 2005 03:55:38 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Perl Embed in C++ Problem -> Urgent, please help!
Message-Id: <Xns962EF36704EA8asu1cornelledu@127.0.0.1>
"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in
news:Xns962EE99A813CFasu1cornelledu@127.0.0.1:
> Google's is fairly annoying.
Hmmm ... That should have been:
Google's interface is fairly annoying.
One more *sigh*.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Mon, 4 Apr 2005 21:36:13 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Perl Embed in C++ Problem
Message-Id: <slrnd53uct.34v.tadmc@magna.augustmail.com>
sleepymish@gmail.com <sleepymish@gmail.com> wrote:
> Thanks for the advice,
In case you want to maximize your chances of getting a useful answer
in the future, you should have a look at the Posting Guidelines
that are posted here frequently.
> but I can't edit that title now.
Why not?
I can. :-)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Mon, 4 Apr 2005 23:59:25 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Please help package Search::VectorSpace; problem
Message-Id: <slrnd546pd.34v.tadmc@magna.augustmail.com>
Ohm <sams@freeddns.org> wrote:
> Appreciate any help here, as Iam not very good in Perl.
Have you seen the Posting Guidelines that are posted here frequently?
> Use of uninitialized value in subroutine entry at
> C:/Perl/site/lib/Search/Vector
> Space.pm line 175, <DATA> line 584.
You really expect potential answerers to count down to
figure out which is line number 175?
Have you looked at line number 584 of your input data to see if it
contains something your program is not prepared to deal with?
Looks like a blank line to me...
> my @docs = {'doc1.txt', 'doc2.txt'};
Why are you storing a single hash ref in @docs with a key
of 'doc1.txt' and a value of 'doc2.txt' ?
my @docs = ('doc1.txt', 'doc2.txt');
Curliness matters. <g>
[snip a whole lotta code]
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Tue, 05 Apr 2005 04:13:01 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Please help package Search::VectorSpace; problem
Message-Id: <Xns962F235BE981asu1cornelledu@127.0.0.1>
"Ohm" <sams@freeddns.org> wrote in news:1112662679.982208.296940
@z14g2000cwz.googlegroups.com:
> Iam tring to create a search tool using PDL andVectorSpace.
> doc1.txt and doc2.txt are files with some text in it.
> Appreciate any help here, as Iam not very good in Perl.
Please do read the posting guidelines for this group.
Why do you think it is useful to post the code for Search::VectorSpace?
Why do you think anyone would be willing to read 870 lines?
> Can't locate object method "set_threshold" via package
> "Search::VectorSpace" at
When I look at the documentation for Search::VectorSpace, I do not see a
method set_threshold as part of the public interface of the module.
Instead, it looks like you have to specify the threshold in the
constructor invocation.
How is this error unexpected?
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: 05 Apr 2005 06:22:25 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <42522ea0$0$25885$8b463f8a@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
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://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Mon, 04 Apr 2005 23:16:13 -0500
From: axel@white-eagle.invalid.uk
Subject: Re: recursivity
Message-Id: <kdCdnVooNceQjM_fRVn-1Q@adelphia.com>
John W. Krahn <someone@example.com> wrote:
> This may work better (untested):
The lack of testing shows.
> opendir DIR, $dir or die "Couldnt open $dir - $!\n";
The variable $var is never declared.
> opendir DIR, $dir or die "Couldnt open $dir - $!\n";
>
> { local @ARGV = grep -f, map "$dir/$_", readdir DIR;
>
> while ( <> ) {
> if ( $. == 1 ) {
> open OUT, '>', "out_$ARGV.txt" or die "Cannot open out_$ARGV.txt:
You have mapped the filenames to include the directory, so e.g. if $ARGV
here is 'foo/bar' you are trying to write to the file 'bar' in the
directory 'out_foo'.
Axel
------------------------------
Date: 4 Apr 2005 23:35:14 -0700
From: chaitanyag@hotmail.com (MENTAT)
Subject: Regular expression question.
Message-Id: <5a286c02.0504042235.5eb485e@posting.google.com>
Hi,
I have a log file that looks something like this
2005-03-29 17:17:11.293|DEBUG|Line 1|
>>>>>>>
Actual Log output line 1
Actual Log output line 2
Actual Log output line 3
Actual Log output line ...
<<<<<<<
2005-03-29 17:17:11.293|DEBUG|Line 9|
>>>>>>>
Actual Log output line 1
Actual Log output line 2
Actual Log output line 3
Actual Log output line ...
<<<<<<<
2005-03-29 17:17:11.309|INFO|Line 4|
>>>>>>>
Actual Log output line 1
Actual Log output line 2
Actual Log output line 3
Actual Log output line ...
<<<<<<<
2005-03-29 17:17:11.319|DEBUG|Line 9|
>>>>>>>
Actual Log output line 1
Actual Log output line 2
Actual Log output line 3
Actual Log output line ...
<<<<<<<
I am trying to write a regular expression that extracts all the log
entries for a given value of "Line".
So if I wanted to look at the entries for Line 4 I want the output to
look something like
2005-03-29 17:17:11.309|INFO|Line 4|
>>>>>>>
Actual Log output line 1
Actual Log output line 2
Actual Log output line 3
Actual Log output line ...
<<<<<<<
Note that I want everything in the line before the "Line 4" text as
well, such as time.
I tried using "<<<<<<<(.*?\|Line 4.*?)>>>>>>>(.*?)<<<<<<<" as the
regular expression (with the ms global modifiers), but the problem is
it matches everything from the beginning of the file (basically the
first <<<<<<<) to the "Line 4". Making .* non-greedy doesn't help
because after it finds the first <<<<<<< the non-greedy match goes all
the way upto the first "Line 4".
Replacing <<<<<<< with the beginning of line (^) doesn't make any
difference either because after the start of the first line, the .*?
still matches everything until "Line 4".
I tried using lookahead and lookbehind assertions as well, but to no
avail. This "<<<<<<<$\(.(?!$)*\|Line 4.*?)>>>>>>>(.*?)<<<<<<<" doesn't
match anything.
Ofcourse, if i remove the s global modifier, i can easily match it
using "(^.*\|Line 4.*)", but then I can't get all the (variable) lines
between <<<<<<< and >>>>>>>. The .* won't match across new line.
Any idea how this problem could be solved? Any help is much
appreciated.
Thanks in advance.
------------------------------
Date: Tue, 05 Apr 2005 01:24:28 -0400
From: Hal Vaughan <hal@thresholddigital.com>
Subject: Shell Commands (Getting PID and Timing Them)
Message-Id: <zeOdnSCQu6aXvM_fRVn-rA@comcast.com>
There may be a better way to do what I want to do, so I'm open to
suggestions.
I want to run a shell command to record sound, and kill it after x seconds.
If I were writing a Bash script, I'd run the command in the background, get
the PID, use a sleep statement, then kill the first command after the sleep
statement. In Perl I know how to fork and get a PID, and I know how to use
`command` to get a commands output, but I can't find a way to run a command
from Perl and get the PID so I can kill it when I want.
Is there a way to get the PID? (I'd rather not use a 2nd script in bash to
do it.)
If there's another way to execute a shell command from Perl, then after x
seconds kill it, I'm open to it.
Thanks!
Hal
------------------------------
Date: Tue, 05 Apr 2005 01:57:08 -0500
From: axel@white-eagle.invalid.uk
Subject: Re: Shell Commands (Getting PID and Timing Them)
Message-Id: <I_qdnYLAkJ1Zq8_fRVn-gg@adelphia.com>
Hal Vaughan <hal@thresholddigital.com> wrote:
> I want to run a shell command to record sound, and kill it after x seconds.
> If I were writing a Bash script, I'd run the command in the background, get
> the PID, use a sleep statement, then kill the first command after the sleep
> statement. In Perl I know how to fork and get a PID, and I know how to use
> `command` to get a commands output, but I can't find a way to run a command
> from Perl and get the PID so I can kill it when I want.
> Is there a way to get the PID? (I'd rather not use a 2nd script in bash to
> do it.)
> If there's another way to execute a shell command from Perl, then after x
> seconds kill it, I'm open to it.
Something like...
my $pid = open (PIPE, "-|") || exec("/what/ever");
# Read from PIPE, have a cup of coffee, sleep
my $kesult = kill 9, $pid;
Axel
------------------------------
Date: Tue, 05 Apr 2005 00:00:57 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: Shell Commands (Getting PID and Timing Them)
Message-Id: <POudnfXkrJQxqs_fRVn-ig@comcast.com>
Hal Vaughan wrote:
> In Perl I know how to fork and get a PID, and I know how to use
> `command` to get a commands output, but I can't find a way to run a command
> from Perl and get the PID so I can kill it when I want.
my $child_pid = fork();
die unless defined $child_pid;
if ($child_pid) { # Parent
sleep $sleep_time;
kill 2,$child_pid;
} else { # Child
exec "command </dev/null >/dev/null 2>&1";
die "Could not run 'command'";
}
-Joe
------------------------------
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 V10 Issue 7943
***************************************
