[22722] in Perl-Users-Digest
Perl-Users Digest, Issue: 4943 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue May 6 03:47:59 2003
Date: Tue, 6 May 2003 00:05:07 -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, 6 May 2003 Volume: 10 Number: 4943
Today's topics:
Re: Can't write a LOG file, please help <grazz@pobox.com>
Re: creating class hierarchies with h2xs <jasonp@uq.net.au>
Re: escape sequencing problem in Perl (Prakash)
Re: escape sequencing problem in Perl <kasp@epatra.com>
Re: escape sequencing problem in Perl <josef.moellers@fujitsu-siemens.com>
Re: In search of elegant code - parameter in grep? <krahnj@acm.org>
Re: In search of elegant code - parameter in grep? <tassilo.parseval@rwth-aachen.de>
NET::SMTP Mail not sent- Queued mail for delivery (Michael)
Re: NET::SMTP Mail not sent- Queued mail for delivery <thepoet@nexgo.de>
Re: perl form validation <koos_pol@NO.nl.JUNK.compuware.MAIL.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
shipping perl (Prashanth)
Re: shipping perl <tassilo.parseval@rwth-aachen.de>
Re: string substitutions with an array <tassilo.parseval@rwth-aachen.de>
Re: Why is POE idle most of the time? (jtd)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 06 May 2003 05:31:00 GMT
From: Steve Grazzini <grazz@pobox.com>
Subject: Re: Can't write a LOG file, please help
Message-Id: <oMHta.38$b91.161603@twister.nyc.rr.com>
Gino Vives <gino_vives@yahoo.com> wrote:
> I wrote a little programe in perl and I haven't be able to write
> wa log file, first I use the shell comand: "programe >> logfile"
> and using lines like: print "Some text over here";
>
> As it didn't work I chage the print lines to: (befor I wrote "open
> (LOG ...);")
> print LOG "Some text over here";
Presumably the open() failed. If you add some error-checking
you'll at least know why:
open LOG, '>> ../logfile' or die "open: ../logfile: $!";
And an absolute path to the logfile would be safer.
> Neither of theses solutions wrote into a file, but the first one
> (if I just esecute "programe") does write in the screen (STDOUT???)
Didn't you get a shell error when you redirect the first one
to a file?
> while ("1") {
> open (LOG , ">> ../logfile");
> #Vemos la fecha:
>
> @fecha = `date`;
You forgot to "use strict;" and you might want some error-checking
here as well. (And an absolute path to /bin/date.)
> $i=0;
>
> while (<@fecha>) {
You're mixing idioms here. These angle-brackets do a glob(), and
you want a foreach().
foreach (@fecha) {
Or, since you're using an index variable:
for my $i (0..$#fecha) {
HTH
--
Steve
------------------------------
Date: Tue, 06 May 2003 00:54:49 -0400
From: Jason Parker-Burlingham <jasonp@uq.net.au>
Subject: Re: creating class hierarchies with h2xs
Message-Id: <87brygsmhy.fsf@freezer.burling>
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) writes:
> Quite. Try ExtUtils::ModuleMaker from CPAN, which allows to create
> the structure for more than on module in one go.
That's what I hit on after checking with Perlmonks.org; I've used it
and it appears to work very well (although using Test::More increases
the number of modules I'll have to install on the client's host).
> You still have to have your modules planned out from the start. If
> you later think you need another module in your project and run
> ModuleMaker again, it will overwrite your work up to then, no
> questions asked.
My one try at adding a module afterward by hand seemed to indicate
that I could just create directories and add .pm files as necessary.
Do I need to update MANIFEST on my own or is it somehow done for me?
--
``Oooh! A gingerbread house! Hansel and Gretel are set for life!''
------------------------------
Date: 5 May 2003 22:43:32 -0700
From: prakashpms@hotmail.com (Prakash)
Subject: Re: escape sequencing problem in Perl
Message-Id: <afc6e663.0305052143.2946247f@posting.google.com>
"Kasp" <kasp@epatra.com> wrote in message news:<b966db$afq$1@newsreader.mailgate.org>...
> Yes, there is more than one way of doing it.
>
> May I point the OP to quotemeta function which I find particularly useful
> but less talked about.
The problem I am facing is that one of the programs returns something
like this string with lots of "\" characters. I want to store them in
a variable and process it as such. But, when I store and use the
variable, I get only half the number of "\"es what the program
returned. I do not want perl to escape sequence the variable. One
workaround I can think of is I can write the output of the program
into a file. When I read each line of the file and use $_, it retains
all the "\"es and works properly. I am wondering is there any other
simpler way than writing into a file and reading.
Thanks
Prakash
------------------------------
Date: Tue, 6 May 2003 12:21:19 +0530
From: "Kasp" <kasp@epatra.com>
Subject: Re: escape sequencing problem in Perl
Message-Id: <b97m5j$3mj$1@newsreader.mailgate.org>
> The problem I am facing is that one of the programs returns something
> like this string with lots of "\" characters. I want to store them in
> a variable and process it as such. But, when I store and use the
> variable, I get only half the number of "\"es what the program
> returned. I do not want perl to escape sequence the variable.
try this
my $var = quotemeta( foo() );
Where foo() is your funtion returning string with lots of '\'
--
"Accept that some days you are the pigeon and some days the statue."
"A pat on the back is only a few inches from a kick in the butt." - Dilbert.
------------------------------
Date: Tue, 06 May 2003 08:57:20 +0200
From: Josef =?iso-8859-1?Q?M=F6llers?= <josef.moellers@fujitsu-siemens.com>
Subject: Re: escape sequencing problem in Perl
Message-Id: <3EB75CD0.6E4588A9@fujitsu-siemens.com>
Prakash wrote:
> =
> "Kasp" <kasp@epatra.com> wrote in message news:<b966db$afq$1@newsreader=
=2Emailgate.org>...
> > Yes, there is more than one way of doing it.
> >
> > May I point the OP to quotemeta function which I find particularly us=
eful
> > but less talked about.
> =
> The problem I am facing is that one of the programs returns something
> like this string with lots of "\" characters. I want to store them in
> a variable and process it as such. But, when I store and use the
> variable, I get only half the number of "\"es what the program
> returned. I do not want perl to escape sequence the variable. One
> workaround I can think of is I can write the output of the program
> into a file. When I read each line of the file and use $_, it retains
> all the "\"es and works properly. I am wondering is there any other
> simpler way than writing into a file and reading.
This sounds strange.
If a variable contains a string with 8 consecutive backslashes, then
there should be no more processing of these meta characters:
Try
$x =3D <STDIN>; print $x;
and enter \\\\\\\\a
So the problem is where they are generated.
-- =
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Tue, 06 May 2003 05:46:43 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: In search of elegant code - parameter in grep?
Message-Id: <3EB74C2B.378EEDF4@acm.org>
David Filmer wrote:
>
> I can do this:
>
> my $category = param('category');
> print grep (/$category/, @LIST);
>
> (where 'param' is a CGI.pm type object)
>
> but I don't like creating the variable $category.
>
> What I would rather do is:
>
> print grep(/param('category')/, @LIST);
>
> but that doesn't seem to work...
>
> Does anyone know what syntax I need to do the grep without creating an
> intermediate variable?
print grep( /${\(param('category'))}/, @LIST );
John
--
use Perl;
program
fulfillment
------------------------------
Date: 6 May 2003 06:41:04 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: In search of elegant code - parameter in grep?
Message-Id: <b97le0$qps$1@nets3.rz.RWTH-Aachen.DE>
Also sprach John W. Krahn:
> David Filmer wrote:
>>
>> I can do this:
>>
>> my $category = param('category');
>> print grep (/$category/, @LIST);
>>
>> (where 'param' is a CGI.pm type object)
>>
>> but I don't like creating the variable $category.
>>
>> What I would rather do is:
>>
>> print grep(/param('category')/, @LIST);
>>
>> but that doesn't seem to work...
>>
>> Does anyone know what syntax I need to do the grep without creating an
>> intermediate variable?
>
>
> print grep( /${\(param('category'))}/, @LIST );
Hrrh, or even:
print grep /(??{ param('category') })/, @LIST;
I think the OP is best advised to use a temporary variable here. It'll
be more efficient than evaluating the same code over and over again for
each element of @LIST.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: 5 May 2003 23:07:39 -0700
From: info@massap.com (Michael)
Subject: NET::SMTP Mail not sent- Queued mail for delivery
Message-Id: <ca40fa08.0305052207.59031836@posting.google.com>
Dear all,
1. Recently I had installed ActivePerl 5.6.9 in our NT server.
2. We have succesfully been able to send out email with the online
form thru ASP scripts.
3. We badly needed to do the same for perl scripts, and NET::SMTP came
very highly recommended.
4. However we have problem getting the mail sent and we are at a total
lost.
5. We got a "Queued mail for delivery", but the email was never
delivered.
6. We would very much appreciate your kindness in advising us to solve
the problem.
Our script
==========
#!/usr/local/bin/perl
use Net::SMTP;
$mailhost = "localhost";
$smtp = Net::SMTP->new($mailhost, Hello => $mailhost, Debug =>
1); # connect to an SMTP server
$smtp->mail( 'info@cashflowclub.org' ); # use the sender's
address here
$smtp->to('michael@cashflowclub.org'); # recipient's
address
$smtp->data(); # Start the mail
# Send the header.
$smtp->datasend("To: Michael\n");
$smtp->datasend("From: Info\n");
$smtp->datasend("Subject: Mail Test\n");
$smtp->datasend("\n");
# Send the body.
$smtp->datasend("Hello, World!\n");
$smtp->dataend(); # Finish sending the mail
$smtp->quit;
Debugging print-out
===================
Net::SMTP: Net::SMTP(2.15)
Net::SMTP: Net::Cmd(2.18)
Net::SMTP: Exporter(5.562)
Net::SMTP: IO::Socket::INET(1.25)
Net::SMTP: IO::Socket(1.26)
Net::SMTP: IO::Handle(1.21)
Net::SMTP=GLOB(0x17f2ebc)<<< 220 STSI10 Microsoft ESMTP MAIL Service,
Version: 5.0.2195.5329 ready at Mon, 5 May 2003 17:03:23 +0800
Net::SMTP=GLOB(0x17f2ebc)>>> EHLO localhost
Net::SMTP=GLOB(0x17f2ebc)<<< 250-STSI10 Hello [127.0.0.1]
Net::SMTP=GLOB(0x17f2ebc)<<< 250-AUTH GSSAPI NTLM LOGIN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-AUTH=LOGIN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-TURN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-ATRN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-SIZE 2097152
Net::SMTP=GLOB(0x17f2ebc)<<< 250-ETRN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-PIPELINING
Net::SMTP=GLOB(0x17f2ebc)<<< 250-DSN
Net::SMTP=GLOB(0x17f2ebc)<<< 250-ENHANCEDSTATUSCODES
Net::SMTP=GLOB(0x17f2ebc)<<< 250-8bitmime
Net::SMTP=GLOB(0x17f2ebc)<<< 250-BINARYMIME
Net::SMTP=GLOB(0x17f2ebc)<<< 250-CHUNKING
Net::SMTP=GLOB(0x17f2ebc)<<< 250-VRFY
Net::SMTP=GLOB(0x17f2ebc)<<< 250 OK
Net::SMTP=GLOB(0x17f2ebc)>>> MAIL FROM:<info@cashflowclub.org>
Net::SMTP=GLOB(0x17f2ebc)<<< 250 2.1.0 info@cashflowclub.org....Sender
OK
Net::SMTP=GLOB(0x17f2ebc)>>> RCPT TO:<tech@cashflowclub.org>
Net::SMTP=GLOB(0x17f2ebc)<<< 250 2.1.5 tech@cashflowclub.org
Net::SMTP=GLOB(0x17f2ebc)>>> DATA
Net::SMTP=GLOB(0x17f2ebc)<<< 354 Start mail input; end with
<CRLF>.<CRLF>
Net::SMTP=GLOB(0x17f2ebc)>>> To: Michael
Net::SMTP=GLOB(0x17f2ebc)>>> From: Info
Net::SMTP=GLOB(0x17f2ebc)>>> Subject: Mail Test
Net::SMTP=GLOB(0x17f2ebc)>>>
Net::SMTP=GLOB(0x17f2ebc)>>> Hello, World!
Net::SMTP=GLOB(0x17f2ebc)>>> .
Net::SMTP=GLOB(0x17f2ebc)<<< 250 2.6.0
<STSI10IpB5uT4JKoA3v0000002d@STSI10> Queued mail for delivery
Net::SMTP=GLOB(0x17f2ebc)>>> QUIT
Net::SMTP=GLOB(0x17f2ebc)<<< 221 2.0.0 STSI10 Service closing
transmission channel
Many Thanks,
Michael
------------------------------
Date: Tue, 6 May 2003 08:40:09 +0200
From: "Christian Winter" <thepoet@nexgo.de>
Subject: Re: NET::SMTP Mail not sent- Queued mail for delivery
Message-Id: <3eb758ca$0$22392$9b4e6d93@newsread4.arcor-online.net>
"Michael" <info@massap.com> wrote:
[...]
> 5. We got a "Queued mail for delivery", but the email was never
> delivered.
[...]
Hi,
your problem lies with the mail server,
your perl code is working fine. Maybe
the server has a problem with missing
adresses in the "From:" and "To:" headers
of the mail? You have to enable debug logging
on the mail server and look inside your
event log to see the failure reasons.
HTH
-Christian
------------------------------
Date: Tue, 06 May 2003 07:49:37 +0200
From: Koos Pol <koos_pol@NO.nl.JUNK.compuware.MAIL.com>
Subject: Re: perl form validation
Message-Id: <newscache$puageh$o6b$1@news.emea.compuware.com>
g wrote (Tuesday 06 May 2003 00:31):
> What is the best way to validate a form in perl using perl? I done
> something similar using JavaScript, I have tried implementing that in
> perl:
>
> Title <input type="text" name="Title" size="8" maxlength="16"/>
> <input type="submit" name="Sub" value="Add Details" onlclick="return
> &validate />
CGI::FormBuilder can validate many fields automatically (email, zipcode,
phone number, etc)
--
KP
------------------------------
Date: Tue, 06 May 2003 02:22:29 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <BhicnUVAF8Ao_yqjXTWcpQ@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"Jeopardy" (because the answer comes before the question), or
"TOFU".
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: 5 May 2003 23:13:51 -0700
From: npengr@yahoo.com (Prashanth)
Subject: shipping perl
Message-Id: <fff5a729.0305052213.57a16a1d@posting.google.com>
Hi,
I want to ship perl with our software (my employer's; not mine :) ),
as our software has a perl script and we don't want to rely on our
customer to have a Perl installation; but, I don't want to ship entire
Perl installation. Here are my doubts:
1. The perl script in our software, does not have any 'use', 'do EXPR'
or 'require' constructs. So I don't want to ship any modules. Will
this be OK?
2. The things which we are going to ship are,
i) Perl interpreter - perl.
ii) Copy of Artistic license.
iii) Copy of "Copying".
Is this OK? Should I include anything more?
3. I would like to ship perl built on Solaris 32 bit platform, for
Solaris 64 bit platform also. Will this cause any problem?
It will be very helpful, if you people can clear my doubts.
Thank you,
Prashanth.
------------------------------
Date: 6 May 2003 07:09:56 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: shipping perl
Message-Id: <b97n44$s3a$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Prashanth:
> I want to ship perl with our software (my employer's; not mine :) ),
> as our software has a perl script and we don't want to rely on our
> customer to have a Perl installation; but, I don't want to ship entire
> Perl installation. Here are my doubts:
>
> 1. The perl script in our software, does not have any 'use', 'do EXPR'
> or 'require' constructs. So I don't want to ship any modules. Will
> this be OK?
>
> 2. The things which we are going to ship are,
> i) Perl interpreter - perl.
> ii) Copy of Artistic license.
> iii) Copy of "Copying".
> Is this OK? Should I include anything more?
As I understand the Artistic license, this is ok. Major Linux
distributions are doing the same. Debian for instance has a perl-base
package that excludes some of the standard modules.
> 3. I would like to ship perl built on Solaris 32 bit platform, for
> Solaris 64 bit platform also. Will this cause any problem?
Could cause problems, but I don't know for sure.
> It will be very helpful, if you people can clear my doubts.
Have you actually tried to use PAR for the above (from the CPAN)? It can
bundle up a Perl script with the required runtime files and make it
appears as though it were an executable (well, it is one actually).
Again I have no idea how compatible such an archive is a 64bit Solaris
when built on a 32bit one. But perhaps you find a way to parcel it up on
the target machine.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: 6 May 2003 06:34:12 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: string substitutions with an array
Message-Id: <b97l14$qeu$1@nets3.rz.RWTH-Aachen.DE>
Also sprach AGoodGuyGoneBad:
[ finding best match ]
> Anyone know an easy way to do this ?
>
> here's an example.
>
> $tray[0]="ijklmno";
> $tray[1]="cdefghi";
> $tray[2]="bcdefg";
> $tray[3]="abcde";
> $tray[4]="ghij";
> $tray[5]="pqrst";
> $tray[6]="abcd";
> $tray[7]="efgh";
> $tray[8]="ijkl";
>
> $buf1="abcdefghijklmnopq";
>
> print "buffer is $buf1\n";
> for ($i=0; $i < 9; $i++) {
> $buf1=~ s/$tray[$i]/($i)/g
> }
> print "buffer is $buf1\n";
>
> this prints a(2)h(0)pq
> but I need it to be
> (6)(7)(0)pq
What you have here is actually a 'hard problem' in terms of computer
science. It requires to match in sequence any permutation of @tray
against $buf1 and determine which of the match is optimal according to
your requirements (minimal number of word-characters left). There are n!
permutations for a list of length n so for nine patterns this may still
be practical, but for 10 there are already 3,628,800 permutations. This
is a numers that grows very fast.
Here is a solution that uses Algorithm::FastPermute. It's not a pretty
solution:
#! /usr/bin/perl -w
use strict;
use Algorithm::FastPermute;
my @tray = qw(ijklmno cdefghi bcdefg abcde ghij
pqrst abcd efgh ijkl);
my %map;
$map{ $tray[$_] } = $_ for 0 .. $#tray;
my $buf = "abcdefghijklmnopq";
my $min_num_chars = length($buf); # initially set to maximum
my %histo; # store new strings; hash-keys are the number of chars left
permute {
my $tmp = $buf;
do_match($tmp, @tray);
my $num_chars = $tmp =~ tr/A-Za-z//;
$min_num_chars = $num_chars if $num_chars < $min_num_chars;
push @{ $histo{ $num_chars } }, $tmp;
} @tray;
print "best match: $histo{ $min_num_chars }->[0]\n";
sub do_match {
my (undef, @pat) = @_;
$_[0] =~ s/$pat[$_]/($map{$pat[$_]})/ for 0 .. $#pat;
}
__END__
best match: (6)(7)(0)pq
What it does is basically iterating over all permutations of @tray and
matching them linearily against $buf. After this is done, it counts the
number of word-characters left in $buf after each match and records a
minimum of this number.
%map is needed to transform the order of elements in the permuted list
to the original list. Otherwise you get indexes relativ to one of the
permuted lists.
You can probably shrink the above a little. It needs quite a bit of
memory because it even stores those results that are irrelevant to the
solution (that is: those that contain more word-characters than a
previous attempt). So you don't need %histo but it gives you some nice
statistics.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: 5 May 2003 21:39:03 -0700
From: adwser@hotmail.com (jtd)
Subject: Re: Why is POE idle most of the time?
Message-Id: <c57c103.0305052039.1aac1034@posting.google.com>
Benjamin Goldberg <goldbb2@earthlink.net> wrote in message news:<3EB6C298.A2624B35@earthlink.net>...
> jtd wrote:
> >
> > I wrote a simple test script using POE that created a single session
> > with a single handler that simply incremented a counter (0..1000) and
> > then yielded to itself. The script took 10s to run. When I profiled
> > it, dprofpp showed that the total user+system time was less than 0.8s.
> >
> > What is happening here? Shouldn't POE use as much CPU time as the OS
> > scheduler allows?
> >
> > Jtd
>
> Maybe there were other things running on your computer?
Nothing intensive, the CPU was mostly idle according to top. Could it
be that POE's scheduler has fixed (time) resolution?
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 4943
***************************************
