[24039] in Perl-Users-Digest
Perl-Users Digest, Issue: 6236 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 9 06:05:37 2004
Date: Tue, 9 Mar 2004 03: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 Tue, 9 Mar 2004 Volume: 10 Number: 6236
Today's topics:
Re: Calling a remote ASP script from my Perl Script -li <ceo@nospan.on.net>
Daemon with Perl <corleone@godfather.com>
Re: Daemon with Perl <nospam@bigpond.com>
Re: Daemon with Perl (Malcolm Dew-Jones)
Digital signature with Perl <Guru03@despammed.com>
Re: Digital signature with Perl <vetro@online.no>
Re: function override (Roel van der Steen)
How to modify struct value within a list (Barry)
Re: How to modify struct value within a list <usenet@morrow.me.uk>
IO::Pipe::close returns wrong value (Heinrich Mislik)
modbus/tcp <module | anything> <iain@nospam.pcorp.com.au>
Re: Need help with Undeliverable Emails <jwillmore@remove.adelphia.net>
Re: Ordering large files (in perl?) <bmb@ginger.libs.uga.edu>
Re: pack/unpack question (OTR Comm)
Re: parsing smime files using Perl (Anno Siegel)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
storing and accessing a has in a package user@domain.invalid
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 09 Mar 2004 04:18:41 GMT
From: Chris <ceo@nospan.on.net>
Subject: Re: Calling a remote ASP script from my Perl Script -libwww?
Message-Id: <BAb3c.56812$4Y1.7232@newssvr33.news.prodigy.com>
Matt Garrish wrote:
> "Chris" <ceo@nospan.on.net> wrote in message
> news:0R%2c.22009$3m4.6006@newssvr31.news.prodigy.com...
>
>>Dave Smithz wrote:
>>
>>>I have a Perl script that needs to process a web form. But also I then
>
> need
>
>>>to send some of that data to a third party ASP script and interpret the
>>>returned results.
>>>
>>>How can I do this.
>>>
>>
>>Form filled in -> Submit -> Form fields returned to Perl -> Perl
>>processes information -> Redirects to ASP passing information to ASP page.
>>
>
>
> Take another look at his question. He's not looking for a redirect but to
> call the script on a different server and process the returned page/data.
> LWP not CGI...
>
You're absolutely right. When I read it again that's what he wants.
Thanks for the correction. That's actually much easier to do too (using
LWP as you first suggested) than what I thought he wanted.
-ceo
------------------------------
Date: Tue, 9 Mar 2004 15:17:18 +0900
From: Vito Corleone <corleone@godfather.com>
Subject: Daemon with Perl
Message-Id: <20040309151718.6529b1dd.corleone@godfather.com>
Hi,
I am writing a perl code to insert all my emails to database. This code
is executed from Postfix. The problem is each time the mail is arriving,
Postfix will create a new process and this takes too much time.
I want to create a server and a client with Perl, the server will run as
a daemon, and each time Postfix gets new mail it will only start a
client process to connect to the server. Can I do this with Perl? Any
documentation, etc? Thank you very much.
------------------------------
Date: Tue, 09 Mar 2004 17:05:21 +1000
From: Gregory Toomey <nospam@bigpond.com>
Subject: Re: Daemon with Perl
Message-Id: <26314930.XjldjUvhsY@GMT-hosting-and-pickle-farming>
Vito Corleone wrote:
> Hi,
>
> I am writing a perl code to insert all my emails to database. This code
> is executed from Postfix. The problem is each time the mail is arriving,
> Postfix will create a new process and this takes too much time.
>
> I want to create a server and a client with Perl, the server will run as
> a daemon, and each time Postfix gets new mail it will only start a
> client process to connect to the server. Can I do this with Perl? Any
> documentation, etc? Thank you very much.
The Postfix/mysql interface is very well documented
eg http://high5.net/howto/
And postfix is supposed to be able to handle in excess of a million emails
day on commodity hardware, so I find the claim that creating a process
takes too much time difficult to understand.
The postfix group my be more helpful instead news:alt.comp.mail.postfix
gtoomey
------------------------------
Date: 8 Mar 2004 23:33:26 -0800
From: yf110@vtn1.victoria.tc.ca (Malcolm Dew-Jones)
Subject: Re: Daemon with Perl
Message-Id: <404d7346@news.victoria.tc.ca>
Vito Corleone (corleone@godfather.com) wrote:
: I want to create a server and a client with Perl
perldoc perlipc
It has various examples of perl clients and servers.
The spamassassin program uses spamc and spamd. spamd is a server (written
in perl) and spamc is a client written in C that reads and writes (at the
same time) to the server. I mention this because the techniques it uses
might be useful.
------------------------------
Date: Tue, 9 Mar 2004 09:28:17 +0000 (UTC)
From: Guru03 <Guru03@despammed.com>
Subject: Digital signature with Perl
Message-Id: <Xns94A76A85428CFGuru03despammedcom@193.43.96.1>
Is there any CPAN module to verify a digital GPG/PGP sign with Perl?
Possibily with no usage of external programs.
Thanks
------------------------------
Date: Tue, 09 Mar 2004 10:35:30 +0100
From: Vetle Roeim <vetro@online.no>
Subject: Re: Digital signature with Perl
Message-Id: <m3n06qnz19.fsf@quimby.dirtyhack.org>
* Guru03@despammed.com
> Is there any CPAN module to verify a digital GPG/PGP sign with Perl?
> Possibily with no usage of external programs.
Check out Crypt::OpenPGP, which is a pure-Perl implementation of
OpenPGP.
<URL:http://search.cpan.org/~btrott/Crypt-OpenPGP-1.03/lib/Crypt/OpenPGP.pm>
--
#!/usr/bin/vr
------------------------------
Date: 9 Mar 2004 00:15:51 -0800
From: roel-perl@st2x.net (Roel van der Steen)
Subject: Re: function override
Message-Id: <ec8dd39e.0403090015.74aa36c9@posting.google.com>
zhao_wu@pmc-sierra.com (Zhao Wu) wrote in message news:<8ec9eeab.0403081803.48e8f713@posting.google.com>...
> For example, redirect_ok() is a function defined in LWP::UserAgent.
> I can override it with:
> sub LWP::UserAgent::redirect_ok { .... }
OK, it probably works. But also: it's *bad*. (That's why you get a
warning.)
Read about inheritance and subclassing, that will solve your problem
in a more elegant and maintainable way.
Regards, Roel
------------------------------
Date: 8 Mar 2004 19:02:06 -0800
From: titanandrews@hotmail.com (Barry)
Subject: How to modify struct value within a list
Message-Id: <54b5a0f1.0403081902.45cbf058@posting.google.com>
Hello,
I have a series of different instances of structs which are stored
in a list. I want to be able to modify an element of a list that is in
the struct that is stored in the list. Follow that? I am certain my
syntax is the problem, but I just can't figure it out. Here is a
simple example of what I am trying to do:
use Class::Struct;
struct defs =>
{
name => '$',
types => '@',
};
my @alldefs;
my $defs = defs->new( name => 'Fred',
types => ('this','that');
push(@alldefs,$defs);
my $otherdefs = defs->new( name => 'Bilbo',
types => ('loot','boot');
push(@alldefs,$otherdefs);
# --- Modify the name of element 0. THIS DOES WORK!
$alldefs[0]->name = 'Barry';
# --- BUT HOW DO I GET TO AN ELEMENT OF THE LIST??
$alldefs[0]->types(0) = 'toot';
I get: "Can't modify non-lvalue subroutine call" compiler error.
I have also tried other methods of changing this value but have
failed. Does anyone know?
many thanks,
Barry
------------------------------
Date: Tue, 9 Mar 2004 03:07:37 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: How to modify struct value within a list
Message-Id: <c2jcdp$23a$1@wisteria.csv.warwick.ac.uk>
Quoth titanandrews@hotmail.com (Barry):
> use Class::Struct;
>
> struct defs =>
> {
> name => '$',
> types => '@',
> };
>
<snip>
> # --- BUT HOW DO I GET TO AN ELEMENT OF THE LIST??
> $alldefs[0]->types(0) = 'toot';
>
> I get: "Can't modify non-lvalue subroutine call" compiler error.
Try reading perldoc Class::Struct: which part of
$obj->a(2, new value); # assign to array element
is unclear?
Ben
--
Like all men in Babylon I have been a proconsul; like all, a slave ... During
one lunar year, I have been declared invisible; I shrieked and was not heard,
I stole my bread and was not decapitated.
~ ben@morrow.me.uk ~ Jorge Luis Borges, 'The Babylon Lottery'
------------------------------
Date: 09 Mar 2004 09:34:11 GMT
From: Heinrich.Mislik@univie.ac.at (Heinrich Mislik)
Subject: IO::Pipe::close returns wrong value
Message-Id: <404d8f93$0$16036$3b214f66@usenet.univie.ac.at>
IO::Pipe::close is not documented. IO::Handle says that close is just a frontend to perl's close. So I expected close to a pipe to return false, if a child returns nonzero. Truth is, that IO::Pipe has it's own close, which doesn't return the code from waitpid. Here is a program to demonstrate it (assuming that ls -Z is an error):
pipe.pl:
#!/bin/perl
use warnings;
use strict;
use IO::Pipe;
my @prog = qw(ls -Z);
open(my $pipe,'-|',@prog) or die;
while(<$pipe>)
{
print
}
close $pipe or warn "command @prog filed";
$pipe = new IO::Pipe;
$pipe->reader(@prog) or die;
while(<$pipe>)
{
print
}
$pipe->close or warn "command @prog filed";
######################
This gives me:
~>./pipe.pl
ls: invalid option -- Z
Try `ls --help' for more information.
command ls -Z filed at ./pipe.pl line 15.
ls: invalid option -- Z
Try `ls --help' for more information.
--
Heinrich Mislik
Zentraler Informatikdienst der Universitaet Wien
A-1010 Wien, Universitaetsstrasse 7
Tel.: (+43 1) 4277-14056, Fax: (+43 1) 4277-9140
------------------------------
Date: Tue, 09 Mar 2004 16:55:46 +0930
From: Iain Buchanan <iain@nospam.pcorp.com.au>
Subject: modbus/tcp <module | anything>
Message-Id: <404d7190$0$3687$c30e37c6@lon-reader.news.telstra.net>
Hi all,
I've done quite a bit of looking on google, cpan, and the like for any
work that someone may have done with modbus tcp. Most search results
were false positives though, so that didn't help.
The modbus/tcp spec is readily available, but first I'm wondering if
anyone has done _any_ modbus tcp stuff with perl, and if not, why not!
I know a little about modbus and perl, so writing some sort of module
(or at least function) wouldn't be completely beyond me, but a few
pointers might save me a lot of time.
Thanks for any info,
Iain
------------------------------
Date: Tue, 09 Mar 2004 00:37:58 -0500
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: Need help with Undeliverable Emails
Message-Id: <pan.2004.03.09.05.37.56.725731@remove.adelphia.net>
On Mon, 08 Mar 2004 16:38:20 +0000, whoknows wrote:
> On Sun, 07 Mar 2004 10:55:05 -0500, James Willmore wrote:
>> The code used to do so *is* a potential security risk. There are many
>> references as to why. Start here in clpm, then move onto Google :-)
>
> I did not comment on OP's code, I commented on usage of Net::SMTP over
> sendmail binary.
You should have commented on the code :-) Perl newsgroup, Perl code ...
simple :-)
Impart your wisdom on how to use the sendmail (or Postfix equivalent)
binary in a safe and secure fashion, will you ... please? Instead of
trolling :-)
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
The human mind treats a new idea the way the body treats a
strange protein -- it rejects it. -- P. Medawar
------------------------------
Date: Mon, 8 Mar 2004 21:16:28 -0500
From: Brad Baxter <bmb@ginger.libs.uga.edu>
Subject: Re: Ordering large files (in perl?)
Message-Id: <Pine.A41.4.58.0403082104460.14578@ginger.libs.uga.edu>
On Mon, 8 Mar 2004, Oeln wrote:
>
> One idea I came upon implied that exec(sort) would be a good option.
> I'd imagine like exec(sort INFILE -o OUTFILE); but I'm not certain, or
> clear on the other options it offers. Is that good enough by itself
> for large files? I get the impression there is a way to output to a
> group of temp files, and then 'integrate' them into one file, etc.
> etc.
>
Following is an example of what I've done:
system( 'sort', '-T', '/tmp', '-o', $index_temp, $index_temp );
(Note, I _want_ the output to go to the same file. Maybe you don't.)
That is, using system()--not exec()--run the unix sort command. As for
options, see (unix) man sort. The unix sort does the temp file
integration process you describe. At least, that's my understanding.
What if something goes wrong? See perldoc -f system.
Regards,
brad
------------------------------
Date: Tue, 09 Mar 2004 06:03:29 GMT
From: otrcomm@wildapache.net (OTR Comm)
Subject: Re: pack/unpack question
Message-Id: <404d5d04.435300453@news.commspeed.net>
Hello,
>Having said that, you can change your template to
>
> c1 x3 i l l l l l s s A16
>
>and then you will get a 'real' 1 into the $op, that is: $op will hold an
>integer instead of a string with the first byte set to 1.
>
>Tassilo
Thank you both Tassilo and gnari, as you both know, your suggestions
worked.
Murrah Boswell
------------------------------
Date: 9 Mar 2004 10:25:52 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: parsing smime files using Perl
Message-Id: <c2k63g$snd$1@mamenchi.zrz.TU-Berlin.DE>
Amir Kadic <zoooz@gmx.de> wrote in comp.lang.perl.misc:
> Novice wrote:
>
> > Everything is pretty straightforward except determining the end of the
> > text message that is in the e-mail.
>
> I just sent a message to myself (locally) containing a
> From ...
> line in the body and exim transformed it into
> >From ...
>
> Guess you have to find out how your server handles this.
Better to use one of the modules whose author already has found out.
Email::Simple comes to mind.
Anno
------------------------------
Date: Tue, 09 Mar 2004 02:22:30 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <04OdnXzvJZdb49DdRVn-sA@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.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: Tue, 09 Mar 2004 12:37:46 +0200
From: user@domain.invalid
Subject: storing and accessing a has in a package
Message-Id: <c2k6q7$7gn$1@ctb-nnrp2.saix.net>
How can I store a hash array so that I can access it within a package?
E.g.
package mytest
use strict;
sub new {
my $class = shift; #class name
my $self = {}; #create a refence to self
#store hash, so that if visible within the package
$self->StoreHash();
bless($self, $class);
return $self
}
sub GetHash {
sub $self=shift;
...
}
sub StoreHash {
sub $self=shift;
...
}
------------------------------
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 6236
***************************************
