[28611] in Perl-Users-Digest
Perl-Users Digest, Issue: 9975 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 17 09:05:51 2006
Date: Fri, 17 Nov 2006 06:05:05 -0800 (PST)
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, 17 Nov 2006 Volume: 10 Number: 9975
Today's topics:
CPAN problem on sun-sloaris, help me <pvrprasadu@gmail.com>
How can I avoid a Die being raised, the handling used d daniel.crosby@gmx.de
Re: How can I avoid a Die being raised, the handling us anno4000@radom.zrz.tu-berlin.de
Re: How can I avoid a Die being raised, the handling us <tadmc@augustmail.com>
Re: How can I avoid a Die being raised, the handling us <mritty@gmail.com>
Re: How can I avoid a Die being raised, the handling us <thepoet_nospam@arcor.de>
Re: howto POST and leave site? <tadmc@augustmail.com>
Re: OT: O'Reilly 'Perl CD Bookshelf' - gone for good? <zentara@highstream.net>
Perl redirection to browser timeout ... <newsgroup@cleanmymailbox.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Sending email, how to get message "Queue ID" <thilbig@sygration.com>
Re: what the difference between these loops? <spam.meplease@ntlworld.com>
Re: what the difference between these loops? <tadmc@augustmail.com>
Re: Win32::GUI or Tk ? <zentara@highstream.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 17 Nov 2006 02:35:41 -0800
From: "pvrprasadu@gmail.com" <pvrprasadu@gmail.com>
Subject: CPAN problem on sun-sloaris, help me
Message-Id: <1163759741.718273.16880@f16g2000cwb.googlegroups.com>
HI,
i installed the cpan shell on sun-solaris10 (sparc) machine.
While installation of cpan, i opted for the auto configure.
cpan shell is coming when i gave command(# perl -MCPAN -e shell)
I tried to install a Perl module called "SOAP::Lite" using cpan shell,
because, When i am installing SOAP::Lite by using the source,it is
asking for some other modules to install.
i wanted to install all the dependent modules.
But when i am installing it is giving errors.
cpan>install SOAP:Lite
Fetching with LWP:
ftp://ftp.perl.org/pub/CPAN/authors/01mailrc.txt.gz
Can't locate object method "new" via package "URI" at
/usr/perl5/site_perl/5.8.4/URI/WithBase.pm line 19, <FIN> line 5
It is giving same error when i am installing any other module.
Is this a problem with Perl installation or sun-machine or cpan
configuration.
The perl version is come with the sun-machine itself, not installed on
my own.
If it is a CPAN configuration problem, then how to do it manually.
How to fix this problem
Please give me some suggetions to solve this problem.
Thanks.
PVR Prasad
------------------------------
Date: 17 Nov 2006 02:27:29 -0800
From: daniel.crosby@gmx.de
Subject: How can I avoid a Die being raised, the handling used does not help
Message-Id: <1163759248.995000.81080@m73g2000cwd.googlegroups.com>
the resulting output occassionaly produces ERROR DIE main:
Can't call method "prepare" on an undefined value at line 1365. - No
event sent!
How can I prevent a die from occurring setting PrintError=>0,
RaiseError=>0 does not seem to help.
local $SIG{ALRM} = sub { die "TIMEOUT: unable to connect
database $G_CONF{INSERT_DB} \n"};
alarm $G_CONF{TIMEOUT_INVDB};
$l_cstr="DBI:Oracle:$G_CONF{INSERT_DB}";
$l_h =
DBI->connect($l_cstr,$G_CONF{INSERT_USER},$G_CONF{INSERT_PASS}, {
PrintError=>0, RaiseError=>0, AutoCom
mit=>1 } );
&Logging (2, $I, "insert", "prepare $l_insert");
-> line 1365 is below prepare
$l_x=$l_h->prepare ($l_insert ) or &Error ("Prepare $l_insert
failed", "insert");
$l_x->execute or &Error ("Execute $l_insert failed", "insert");
$G_DBCON->disconnect or &Warn ( "Can not close config DB
$G_CONF{CONFIG_DB} - $DBI::errstr", "disconnect");
alarm 0;
};
------------------------------
Date: 17 Nov 2006 11:18:36 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: How can I avoid a Die being raised, the handling used does not help
Message-Id: <4s5k4cFu63n1U1@mid.dfncis.de>
<daniel.crosby@gmx.de> wrote in comp.lang.perl.misc:
> the resulting output occassionaly produces ERROR DIE main:
> Can't call method "prepare" on an undefined value at line 1365. - No
> event sent!
> How can I prevent a die from occurring setting PrintError=>0,
> RaiseError=>0 does not seem to help.
You can wrap the offending statement in an eval block, but really
you shouldn't call prepare() at all when the preceding connect
doesn't return a defined value.
> local $SIG{ALRM} = sub { die "TIMEOUT: unable to connect
> database $G_CONF{INSERT_DB} \n"};
>
> alarm $G_CONF{TIMEOUT_INVDB};
>
> $l_cstr="DBI:Oracle:$G_CONF{INSERT_DB}";
>
> $l_h =
> DBI->connect($l_cstr,$G_CONF{INSERT_USER},$G_CONF{INSERT_PASS}, {
> PrintError=>0, RaiseError=>0, AutoCom
> mit=>1 } );
Check the result. If $l_h isn't defined, you can't call the prepare()
method on it. Catching the error won't help, because the actual error
happened earlier in connect().
> &Logging (2, $I, "insert", "prepare $l_insert");
> -> line 1365 is below prepare
> $l_x=$l_h->prepare ($l_insert ) or &Error ("Prepare $l_insert
> failed", "insert");
> $l_x->execute or &Error ("Execute $l_insert failed", "insert");
>
>
> $G_DBCON->disconnect or &Warn ( "Can not close config DB
> $G_CONF{CONFIG_DB} - $DBI::errstr", "disconnect");
> alarm 0;
> };
>
Anno
------------------------------
Date: Fri, 17 Nov 2006 05:34:15 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: How can I avoid a Die being raised, the handling used does not help
Message-Id: <slrnelr7hn.o0a.tadmc@tadmc30.august.net>
daniel.crosby@gmx.de <daniel.crosby@gmx.de> wrote:
> Can't call method "prepare" on an undefined value at line 1365. - No
> How can I prevent a die from occurring
> $l_h =
> DBI->connect($l_cstr,$G_CONF{INSERT_USER},$G_CONF{INSERT_PASS}, {
> PrintError=>0, RaiseError=>0, AutoCom
> mit=>1 } );
One way would be to check the return value:
do_something_other_than_die() unless defined $l_h;
> &Logging (2, $I, "insert", "prepare $l_insert");
> -> line 1365 is below prepare
> $l_x=$l_h->prepare ($l_insert ) or &Error ("Prepare $l_insert
> failed", "insert");
Another way would be to wrap it in a eval block (and you shouldn't
use ampersand on function calls unless you really do want the
semantics that it brings, see perlsub.pod):
eval {
$l_x = $l_h->prepare($l_insert) or
Error("Prepare $l_insert failed", 'insert');
}
if ( $@ ) {
do_something_other_than_die();
}
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 17 Nov 2006 03:53:07 -0800
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: How can I avoid a Die being raised, the handling used does not help
Message-Id: <1163764387.637783.33720@j44g2000cwa.googlegroups.com>
daniel.crosby@gmx.de wrote:
> the resulting output occassionaly produces ERROR DIE main:
> Can't call method "prepare" on an undefined value at line 1365. - No
> event sent!
> How can I prevent a die from occurring setting PrintError=>0,
> RaiseError=>0 does not seem to help.
That's because you have a Perl error, not a Database error.
>
> local $SIG{ALRM} = sub { die "TIMEOUT: unable to connect
> database $G_CONF{INSERT_DB} \n"};
>
> alarm $G_CONF{TIMEOUT_INVDB};
>
> $l_cstr="DBI:Oracle:$G_CONF{INSERT_DB}";
>
> $l_h =
> DBI->connect($l_cstr,$G_CONF{INSERT_USER},$G_CONF{INSERT_PASS}, {
> PrintError=>0, RaiseError=>0, AutoCom
> mit=>1 } );
You shot yourself in the foot, by setting RaiseError to 0 here. If
you'd set it to 1, Perl would have died when this call to DBI->connect
failed. Because you set it to 0, and didn't bother checking the return
value, you have no way of knowing that the connect() failed until you
later try to erroneously use the return value of the failed connect().
> &Logging (2, $I, "insert", "prepare $l_insert");
> -> line 1365 is below prepare
> $l_x=$l_h->prepare ($l_insert ) or &Error ("Prepare $l_insert
> failed", "insert");
Here. When DBI->connect() failes, it returned undef to $l_h, but you
didn't check that possibility. So when you use it here, you're trying
to call a method on an undefined value, which is a Perl error.
Paul Lalli
------------------------------
Date: Fri, 17 Nov 2006 12:28:58 +0100
From: Christian Winter <thepoet_nospam@arcor.de>
Subject: Re: How can I avoid a Die being raised, the handling used does not help
Message-Id: <455d9cfa$0$27622$9b4e6d93@newsspool2.arcor-online.net>
daniel.crosby@gmx.de wrote:
> the resulting output occassionaly produces ERROR DIE main:
> Can't call method "prepare" on an undefined value at line 1365. - No
> event sent!
> How can I prevent a die from occurring setting PrintError=>0,
> RaiseError=>0 does not seem to help.
>
> local $SIG{ALRM} = sub { die "TIMEOUT: unable to connect
> database $G_CONF{INSERT_DB} \n"};
>
> alarm $G_CONF{TIMEOUT_INVDB};
>
> $l_cstr="DBI:Oracle:$G_CONF{INSERT_DB}";
>
> $l_h =
> DBI->connect($l_cstr,$G_CONF{INSERT_USER},$G_CONF{INSERT_PASS}, {
> PrintError=>0, RaiseError=>0, AutoCom
> mit=>1 } );
At this point you should check if your connect was successfull, and
only if the answer is yes you should try to operate on the database
handle. I usually do something alike
my $dbhandle;
if( $dbhandle = DBI->connect($dsn, $user, $pass, \%options) )
{
...do my database logic...
} else {
...uuups...
}
-Chris
------------------------------
Date: Fri, 17 Nov 2006 05:22:34 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: howto POST and leave site?
Message-Id: <slrnelr6rq.o0a.tadmc@tadmc30.august.net>
botfood <botfood@yahoo.com> wrote:
[ attribution missing ]
>> here: many (most?) people using Perl are not using it for CGI.)
> -----
> ...I wonder. That really is ALL I use perl for; not being a sys admin,
I've supported my family for over 10 years on the back of Perl, and
am neither a sysadmin nor a web developer.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 17 Nov 2006 13:58:14 GMT
From: zentara <zentara@highstream.net>
Subject: Re: OT: O'Reilly 'Perl CD Bookshelf' - gone for good?
Message-Id: <ssfrl29mhvpldogmtpoug7pc4v1ivipdlp@4ax.com>
On 16 Nov 2006 19:34:57 GMT, rdwillia@anon.example.net (Richard
Williams) wrote:
>Just noticed on the O'Reilly site that the 2004 4th edition of the 'Perl
>CD Bookshelf' is out of print (as are all the other Bookshelf titles), and
>cdbookshelves.oreilly.com is gone. I guess that means it's just Safari or
>dead trees from now on, which seems rather a pity - the Perl CD has been
>my main 3rd party reference since version 1, and there are several obvious
>new candidate books for a 5th edition. Just wondering if any of the
>O'Reilly authors here happen to know if (or why) this is indeed the end of
>the line?
>
>Richard.
Look for old copies at amazon.com or ebay.
--
I'm not really a human, but I play one on earth.
http://zentara.net/japh.html
------------------------------
Date: 17 Nov 2006 05:37:46 -0800
From: "JKH" <newsgroup@cleanmymailbox.com>
Subject: Perl redirection to browser timeout ...
Message-Id: <1163770666.727241.76890@e3g2000cwe.googlegroups.com>
I have a Perl script that is called by a web browser. The script may
take up to 60 seconds or more to complete processing before
redirecting the browser to a destination URL. The problem I'm
experiencing is that when the processing time is between 30
and 60 seconds, it returns a DNS error to the browser. If
under 30 seconds, the redirection is fine.
How can I prevent this?
Thank you, JKH
------------------------------
Date: 17 Nov 2006 08:10:12 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <455d6e64$0$81349$ae4e5890@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.7 $)
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.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 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_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: 17 Nov 2006 05:31:17 -0800
From: "Tom" <thilbig@sygration.com>
Subject: Sending email, how to get message "Queue ID"
Message-Id: <1163770277.018106.24230@h48g2000cwc.googlegroups.com>
I am happily using MIME::Lite to send messages via sendmail, but I am
stuck on a problem. I need to track the status of the message to
ensure it was properly accepted by the local sendmail agent and the
remote mail host (i.e. date/time it was accepted by the remote host,
X-Status message id assigned by that host, if delivery was deferred,
etc.)
I can do this in MIME::Lite by setting the Message-ID parameter, then
parsing the sendmail maillog file for this message-ID and returning the
Queue ID. Then, following the Queue ID through the same maillog. This
seems like such a hack (and dangerous setting the Message-ID, but there
doesn't seem to be a way of just fetching it). Is there a better way?
Tom
------------------------------
Date: 17 Nov 2006 01:59:11 -0800
From: "doolittle" <spam.meplease@ntlworld.com>
Subject: Re: what the difference between these loops?
Message-Id: <1163757551.339434.273650@e3g2000cwe.googlegroups.com>
John Bokma wrote:
> In what way?
>
Depending on how the key was defined, the version using 'each' didn't
seem to go through each hash pair. Maybe its because i would sometimes
break out of the each loop before it ended, then the next time into
that loop, it started from the point i left off.
Even so, i only noticed this when i changed how the key was defined.
When i had -
$key = join('',$character,$number);
it appeared to 'work' (ie go through all the pairs every time) But
when I changed that line to
$key = join(':',$character,$number);
it stopped going through every pair every time.
------------------------------
Date: Fri, 17 Nov 2006 05:41:36 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: what the difference between these loops?
Message-Id: <slrnelr7vg.o0a.tadmc@tadmc30.august.net>
doolittle <spam.meplease@ntlworld.com> wrote:
> John Bokma wrote:
>
>> In what way?
In what way what?
Please retain enought context for folks to be able to tell what you
are talking about.
I think it was something about in what way did your code
using "each" fail...
> Depending on how the key was defined, the version using 'each' didn't
> seem to go through each hash pair. Maybe its because i would sometimes
> break out of the each loop before it ended, then the next time into
> that loop, it started from the point i left off.
That's what "perldoc -f each" says it is supposed to do.
It also says how to avoid it.
You should read the documentation for the functions that you use.
(most especially when you are having trouble with that function!)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 17 Nov 2006 13:58:14 GMT
From: zentara <zentara@highstream.net>
Subject: Re: Win32::GUI or Tk ?
Message-Id: <f9frl2tj415dpd8hie9vfei6d9vejrmae4@4ax.com>
On 16 Nov 2006 04:25:26 -0800, "MoshiachNow" <lev.weissman@creo.com>
wrote:
>HI,
>
>What is more popular/preferable/recommended for GUI in Perl:
>Win32::GUI or Tk ?
>
>Thanks
Well Tk will also run on linux, unix, Mac; so Tk is more
cross-platform.
Don't forget the new kid on the block, Gtk2. I think
Gtk2 is the future.
It is actively developed.
It's syntax is close to the c, so you can port to c easily.
It is very state of the art, and allows you to take full control.
Downside: It has a steeper learning curve, and it's docs are
scattered in a slew of different demos, tutorials, and
perldocs. The perldocs are auto-generated from the c libs,
so they are very difficult to read at first ( no example code ).
--
I'm not really a human, but I play one on earth.
http://zentara.net/japh.html
------------------------------
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 9975
***************************************
