[25272] in Perl-Users-Digest
Perl-Users Digest, Issue: 7517 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 14 06:05:31 2004
Date: Tue, 14 Dec 2004 03:05:06 -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 Tue, 14 Dec 2004 Volume: 10 Number: 7517
Today's topics:
(quickie) (Aliasing) Possible to get this to work in st <xxxx@yyyy.zzzz>
Re: (quickie) (Aliasing) Possible to get this to work i <tassilo.von.parseval@rwth-aachen.de>
Re: (quickie) (Aliasing) Possible to get this to work i (Anno Siegel)
Re: FAQ 4.36: How can I expand variables in text string <emschwar@pobox.com>
Re: get startup / running time of a process? <xxxx@yyyy.zzzz>
Re: How to detect an undefined SV* value in XS? <kalinaubears@iinet.net.au>
How to do this job? <sonet.all@msa.hinet.net>
Re: how to read email automatically without POP3 and IM xhoster@gmail.com
Re: how to read email automatically without POP3 and IM <matthew.garrish@sympatico.ca>
Re: mkdir <jurgenex@hotmail.com>
Re: Need help with constants and package names. <emschwar@pobox.com>
Re: Newbie questions, migrating from c++ <do-not-use@invalid.net>
Re: Newbie questions, migrating from c++ <zen13097@zen.co.uk>
Re: Opinions on the Design of Perl (Anno Siegel)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: socket script dies <dontmewithme@got.it>
Re: socket script dies <dontmewithme@got.it>
Re: Solaris taking over Perl ownership <1usa@llenroc.ude.invalid>
Re: Solaris taking over Perl ownership <matthew.garrish@sympatico.ca>
Thread safety Tips in perl madhav_a_kelkar@hotmail.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 14 Dec 2004 00:43:06 -0800
From: "Crom" <xxxx@yyyy.zzzz>
Subject: (quickie) (Aliasing) Possible to get this to work in strict?
Message-Id: <cpm91r$8of$1@news.astound.net>
1: my $n = 5;
2: *r = \$n;
3:
4: $r++; # both should now be 6
5: $n++; # both should not be 7
6:
7: print "\$n = $n\n\$r = $r";
Works fine without 'use strict'...
$n = 7
$r = 7
...but with strict it barfs.
Global symbol "$r" requires explicit package name at line 6.
Global symbol "$r" requires explicit package name at line 9.
------------------------------
Date: Tue, 14 Dec 2004 09:54:16 +0100
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: (quickie) (Aliasing) Possible to get this to work in strict?
Message-Id: <slrncrtaho.h4u.tassilo.von.parseval@localhost.localdomain>
Also sprach Crom:
> 1: my $n = 5;
> 2: *r = \$n;
> 3:
> 4: $r++; # both should now be 6
> 5: $n++; # both should not be 7
> 6:
> 7: print "\$n = $n\n\$r = $r";
>
>
> Works fine without 'use strict'...
>
> $n = 7
> $r = 7
>
> ...but with strict it barfs.
>
> Global symbol "$r" requires explicit package name at line 6.
> Global symbol "$r" requires explicit package name at line 9.
You can circumvent that by pre-declaring $r using our() or 'use vars':
use strict;
our $r; # pre-5.6.0 perls: use vars qw/$r/;
my $n = 5;
*r = \$n;
$r++;
print "$n - $r\n";
__END__
6 - 6
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: 14 Dec 2004 08:58:55 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: (quickie) (Aliasing) Possible to get this to work in strict?
Message-Id: <cpma0f$o4q$1@mamenchi.zrz.TU-Berlin.DE>
Crom <xxxx@yyyy.zzzz> wrote in comp.lang.perl.misc:
> 1: my $n = 5;
> 2: *r = \$n;
> 3:
> 4: $r++; # both should now be 6
> 5: $n++; # both should not be 7
> 6:
> 7: print "\$n = $n\n\$r = $r";
>
>
> Works fine without 'use strict'...
>
> $n = 7
> $r = 7
>
> ...but with strict it barfs.
>
> Global symbol "$r" requires explicit package name at line 6.
> Global symbol "$r" requires explicit package name at line 9.
"use strict" means, among other things, that you have to declare
all variables. You haven't declared your variables, so it complains.
Anno
------------------------------
Date: Mon, 13 Dec 2004 17:54:52 -0700
From: Eric Schwartz <emschwar@pobox.com>
Subject: Re: FAQ 4.36: How can I expand variables in text strings?
Message-Id: <etod5xd1yxv.fsf@wilson.emschwar>
Brian McCauley <nobull@mail.com> writes:
> PerlFAQ Server wrote:
>> 4.36: How can I expand variables in text strings?
>> Let's assume that you have a string like:
>> $text = 'this has a $foo in it and a $bar';
>
> This is question is clearly asking for a simple templating system.
I've been thinking about this, because the question as stated doesn't
seem to match the question as meant. At first glance, I even wondered
why someone would need a FAQ to tell them to use $var inside a
double-quotish string!
Perhaps restating the question as something along the lines of one of
these might help:
* How can I expand a variable name in text strings?
* How can I replace a string with the contents of a variable?
Or something along those lines. Maybe it's just me, but I'd find
something like that to make more sense. Of course, if that's how the
question is normally stated, then regardless of my preferences, that's
how it should read in the FAQ.
-=Eric
--
Come to think of it, there are already a million monkeys on a million
typewriters, and Usenet is NOTHING like Shakespeare.
-- Blair Houghton.
------------------------------
Date: Tue, 14 Dec 2004 00:48:56 -0800
From: "Crom" <xxxx@yyyy.zzzz>
Subject: Re: get startup / running time of a process?
Message-Id: <cpm9da$8qs$1@news.astound.net>
Peter Michael wrote:
> Crom,
>
> "Crom" <xxxx@yyyy.zzzz> schrieb im Newsbeitrag
> news:cp8vo8$jua$1@news.astound.net...
>> Is there a portable way of obtaining the start up and/or elapsed time
>> since start (which I suppose could be calculated given the start
>> time, so no biggy, just need the start time.)
>
> have a look at $^T in the perlvar man page.
Sorry I was not clearer, I wanted ot find this information for _other_
runing programs on the system.
------------------------------
Date: Tue, 14 Dec 2004 05:07:37 +0000
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: How to detect an undefined SV* value in XS?
Message-Id: <41be848a$0$21740$5a62ac22@per-qv1-newsreader-01.iinet.net.au>
Tassilo v. Parseval wrote:
> Also sprach Sisyphus:
>
>
>>Sisyphus wrote:
>>
>>
>>>use warnings;
>>>use Inline C => Config =>
>>> BUILD_NOISY => 1; # to make sure we get to
>>> # see compiler warnings
>>>
>>>use Inline C => <<'END_OF_C_CODE';
>>>
>>>void set_undef(SV * a) {
>>>
>>>sv_setsv(a, &PL_sv_undef);
>>
>>Another thread, and another list - and it has just been drawn to my
>>attention that's not the right way to assign PL_sv_undef to an SV. The
>>above line should be replaced by:
>>
>>a = &PL_sv_undef
>
>
> Wont help either. You cannot change 'a' in-place thusly. If you want
> that you'd have to have something like:
>
> void set_undef (SV **a) {
> *a = &PL_sv_undef;
> }
>
> But I don't think that Inline::C or XS know about an SV** prototype. The
> reason is again the difference between changing a C-structure internally
> (this is what sv_setsv does) or having a variable point to something
> else. If you want to do the latter, you need to pass the pointer by
> reference. These are the usual C-semantics.
>
>
>>>if(a == &PL_sv_undef)
>>> printf("A valid means of testing for &PL_sv_undef\n");
>>>
>>>else printf("An INVALID means of testing for &PL_sv_undef\n");
>>>
>>>}
>>>
>>
>>I haven't tested, but I expect one would then find that the script
>>reports "A valid means of testing for &PL_sv_undef".
>
>
> Only if the variable passed to set_undef() was a real PL_sv_undef in the
> first place. :-) What you are thinking of is a no-op.
>
> Tassilo
A tree ... and some rope .... that's all I *really* need ;-)
Cheers,
Rob
--
To reply by email u have to take out the u in kalinaubears.
------------------------------
Date: Tue, 14 Dec 2004 14:14:25 +0800
From: "news.hinet.net" <sonet.all@msa.hinet.net>
Subject: How to do this job?
Message-Id: <cpm0cu$8kh$1@netnews.hinet.net>
Direcory:
/usr/local/ap/
Filename:
1
1.lock
2
3
4
4.lock
want to list 2 and 3.
========================================================
opendir(DIR,"/usr/local/ap/");
@dots = grep {-f "/usr/local/ap/$_" && $_ !~m/\.lock/} readdir(DIR);
close(DIR);
========================================================
The @dots have 1 2 3 4 elements. I know i can use -e to check the
$filename.lock in loop.
But how to make @dots just have 2 and 3? Becaues the directory have
many files,i don't want to worse time to check the $filename.lock .
please help!
thanks!
------------------------------
Date: 13 Dec 2004 23:28:35 GMT
From: xhoster@gmail.com
Subject: Re: how to read email automatically without POP3 and IMAP servers in perl?
Message-Id: <20041213182835.252$Xr@newsreader.com>
"dale" <zhangd@tycoelectronics.com> wrote:
> Our company is using SMTP on the mail server. The help desk told me
> that this is the only one we use to receive and send mails.
Well, they are almost certainly wrong.
> We use
> microsoft outlook to read and send emails.
I think that MS Outlook speaks some propietary protocol(s) to communicate
with the MS Exchange server. The server has to be running this protocol(s)
or else Outlook would not work. Perhaps your helpdesk meant that,
other than propietary protocols, they run only SMTP.
I cannot find any perl module that emulates this protocol, but I may
have overlooked it. There is a Evolve program which runs on Linux
and I think is supposed to support Exchanges protocols. I don't
think it has anything to do with Perl, but you may be able to link into
it from Perl. I can't figure out whether it is commercial or open source.
(Earlier)
> If not, I can use internet explorer to access my emails, could I use
> web server to do this?
Perhaps. I can use Mozilla to access (at least one version of) Outlook Web
Access, so it doesn't seem to be highly propietary on the browser side.
You might be able to use LWP or WWW::Mechanize or something like that to
get your mail from the mail/web server. I don't know enough about using
those modlules to give any more detailed advice, however.
Good Luck,
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: Mon, 13 Dec 2004 20:54:22 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: how to read email automatically without POP3 and IMAP servers in perl?
Message-Id: <eJrvd.7143$%p1.599777@news20.bellglobal.com>
"dale" <zhangd@tycoelectronics.com> wrote in message
news:1102976196.788139.63590@z14g2000cwz.googlegroups.com...
>I have verizon dsl service at home. I guess that they have pop3 server
> for receiving mails. I tried to telnet or ping to incoming.verizon.net.
> None of them works.
>
> Any idea? -Dale
>
Why not just use their web interface...
http://netmail.verizon.net/
How about writing some actual code now to do whatever it is you're trying to
do and then come back with any specific problems you have. Sorry, but I see
nothing useful coming of this thread anymore.
Matt
------------------------------
Date: Tue, 14 Dec 2004 03:13:14 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: mkdir
Message-Id: <eTsvd.3525$Zn6.566@trnddc08>
Freak wrote:
> can somene post sample of creating directory, ie:
> I have
> www.domain.com
> Now I need this:
> www.domain.com/directory1
Which part of "perldoc -f mkdir" is unclear to you?
Please let us know such that we can try an improve it.
jue
------------------------------
Date: Mon, 13 Dec 2004 18:06:54 -0700
From: Eric Schwartz <emschwar@pobox.com>
Subject: Re: Need help with constants and package names.
Message-Id: <eto8y811ydt.fsf@wilson.emschwar>
Terry <just@say.no> writes:
> Hello all, I'm having trouble with packages and constants. What I'd
> like to have is a single .pm for all constants used by the application.
Others have commented on how, and why (and why not), so I'll just add
my two cents on the wisdom of doing so:
On clpm, we tell everybody to 'use warnings;' and 'use strict;'. Why?
Because, among other things, they force you to declare your variables,
so you can catch when you typo writing one and also so you can trace
the life of your variable more easily. When you import a variable
(or a constant), you're effectively circumventing at least one of
those benefits.
Admittedly, it's worse with variables, where you're potentially
subject to action-at-a-distance when some random code out there
somewhere modifies a variable you didn't know it was modifying, but
even with constants, unless you explicitly import them all, it's very
easy to forget where it's defined and why, if you're in the habit of
exporting such things by default. (And for my next trick, a run-on
sentence the length of War and Peace!)
Just a thought.
-=Eric
--
Come to think of it, there are already a million monkeys on a million
typewriters, and Usenet is NOTHING like Shakespeare.
-- Blair Houghton.
------------------------------
Date: 14 Dec 2004 09:59:50 +0100
From: Arndt Jonasson <do-not-use@invalid.net>
Subject: Re: Newbie questions, migrating from c++
Message-Id: <yzdoegxl0ft.fsf@invalid.net>
Michael Carman <mjcarman@mchsi.com> writes:
> gg500@lycos.com wrote:
> > Sherm Pendley wrote:
> >>
> >> A. Sinan didn't give you noise, he gave you good advice. Arrogance
> >> is what you're giving him back, by flaming him in return for his
> >> help.
> >
> > If you honestly didn't recognize his reply as arrogant then I suggest
> > you take another look.
>
> If that post really offended you I suggest you leave this group and
> don't return until you've grown a thicker skin. Honestly, I do.
> Otherwise this will just degenerate into yet another "why is everybody
> in this newsgroup so !%@*#$ rude?" threads that benefit no one.
I think the way to grow a thicker skin, if that's what one wants to
do, is to participate in the skin-beating process, not to
retreat. That means using this group for what it's meant for, of
course: discussing Perl, and not so much discussing whether the
questions posed are a model of clarity. (Sorry for doing $#thread++.)
------------------------------
Date: 14 Dec 2004 09:17:50 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: Newbie questions, migrating from c++
Message-Id: <41beafbd$0$1076$db0fefd9@news.zen.co.uk>
On Sun, 12 Dec 2004 13:47:50 -0500,
Matt Garrish <matthew.garrish@sympatico.ca> wrote:
>
> s/^(\s+)/print length($1)/e;
Yuk! That seems quite convoluted, and also needlessly destroys your
source string:
$_ = " hello world ";
s/^(\s+)/print length($1)/e;
print "\n-\n";
print;
__END__
4
-
1hello world
IMHO, better would be:
print length $1 if /^(\s*)/;
------------------------------
Date: 14 Dec 2004 09:14:25 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Opinions on the Design of Perl
Message-Id: <cpmath$o4q$2@mamenchi.zrz.TU-Berlin.DE>
<AaronJSherman@gmail.com> wrote in comp.lang.perl.misc:
> "I have a question about the design of Perl5"
>
> Ok....
>
> "What advantages does exporting symbols of module have over allowing
> method calls"
>
> Well, that's not really a Perl 5 design issue at all. You can do
> either, and there are times that either or both make sense.
>
> It really depends on how your module will be used. If it's going to be
> used in a primarily OO style, then it makes sense to treat everything
> (including your module) as an object.
A Perl module is never an object in a meaningful sense. You probably
meant to say "class".
Anno
------------------------------
Date: 14 Dec 2004 08:22:39 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <41bea2ce$0$16523$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, 13 Dec 2004 23:34:47 GMT
From: Larry <dontmewithme@got.it>
Subject: Re: socket script dies
Message-Id: <dontmewithme-CCF1E7.00335014122004@twister2.tin.it>
I also tried with this:
foreach $var (sort(keys(%SIG))) {
$val = $SIG{$var};
${var}='IGNORE';
}
but it didn't work...
I'M HAD!
------------------------------
Date: Mon, 13 Dec 2004 23:48:50 GMT
From: Larry <dontmewithme@got.it>
Subject: Re: socket script dies
Message-Id: <dontmewithme-0BC3DC.00475314122004@twister2.tin.it>
In article <dontmewithme-D61C47.22301513122004@twister1.tin.it>,
Larry <dontmewithme@got.it> wrote:
> In article <1102970605.937600.60190@c13g2000cwb.googlegroups.com>,
> AaronJSherman@gmail.com wrote:
>
> > Your script may be responding to a signal like SIGPIPE. You need to
> > trap it and deal with it as appropriate. See %SIG in the perlvar
> > manpage.
> >
>
> how could I trap it?
local $SIG{PIPE} = 'IGNORE';
It doesn't work either...
--> # No such signal: SIGPIPE.
------------------------------
Date: 14 Dec 2004 01:49:16 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Solaris taking over Perl ownership
Message-Id: <Xns95BED3CD7D4E6asu1cornelledu@132.236.56.8>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in
news:mHlvd.5495$%p1.493010@news20.bellglobal.com:
>
> <krakle@visto.com> wrote in message
> news:1102961637.365303.109980@c13g2000cwb.googlegroups.com...
>> Sherm I suppose you are an idiot because I'm not the one who said:
>>>> Define iterputer please.
>>
>
> No, you're the idiot who wrote:
>
> "Perl language. Perl code. perl interputer."
>
> Please pay attention to your own postings.
>
And I am the idiot who then misspelled krakle's misspelling:
http://tinyurl.com/5ut8m
Sinan.
------------------------------
Date: Mon, 13 Dec 2004 21:10:13 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Solaris taking over Perl ownership
Message-Id: <5Yrvd.7159$%p1.607820@news20.bellglobal.com>
"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in message
news:Xns95BED3CD7D4E6asu1cornelledu@132.236.56.8...
> "Matt Garrish" <matthew.garrish@sympatico.ca> wrote in
> news:mHlvd.5495$%p1.493010@news20.bellglobal.com:
>
>>
>> <krakle@visto.com> wrote in message
>> news:1102961637.365303.109980@c13g2000cwb.googlegroups.com...
>>> Sherm I suppose you are an idiot because I'm not the one who said:
>>>>> Define iterputer please.
>>>
>>
>> No, you're the idiot who wrote:
>>
>> "Perl language. Perl code. perl interputer."
>>
>> Please pay attention to your own postings.
>>
>
> And I am the idiot who then misspelled krakle's misspelling:
>
> http://tinyurl.com/5ut8m
>
Hang your head in shame... : )
Matt
------------------------------
Date: 13 Dec 2004 22:49:23 -0800
From: madhav_a_kelkar@hotmail.com
Subject: Thread safety Tips in perl
Message-Id: <338e571.0412132249.468ab2b1@posting.google.com>
Hi all,
I want to use perl threads in my project. I have already
written modules for my project, which are working fine. But since I
want to use threads, how can I insure that the modules which I have
written are thread safe? what are the addiotional constriants need to
be considered for this?
any help is greatly appriciated.
Thanks in advance,
Madhav.
------------------------------
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 7517
***************************************
