[28363] in Perl-Users-Digest
Perl-Users Digest, Issue: 9727 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 15 06:05:44 2006
Date: Fri, 15 Sep 2006 03:05:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 15 Sep 2006 Volume: 10 Number: 9727
Today's topics:
Check IP range for DNSBL listing <scubacuda@gmail.com>
Re: Check IP range for DNSBL listing usenet@DavidFilmer.com
Re: Check IP range for DNSBL listing <mumia.w.18.spam+nospam.usenet@earthlink.net>
Re: I/O with raw disk <josef.moellers@fujitsu-siemens.com>
Re: Maximum number of sockets <sisyphus1@nomail.afraid.org>
Re: Maximum number of sockets <sisyphus1@nomail.afraid.org>
new CPAN modules on Fri Sep 15 2006 (Randal Schwartz)
Re: perl on windows - possible bug? <sisyphus1@nomail.afraid.org>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Preventing changes to a module's variables in mod_p <nobull67@gmail.com>
sort hash values does not work fatgirl.brown@gmail.com
Re: sort hash values does not work <xicheng@gmail.com>
Re: String buffer instead of file handle? <danparker276@yahoo.com>
Re: String buffer instead of file handle? <RedGrittyBrick@SpamWeary.foo>
Re: String buffer instead of file handle? <RedGrittyBrick@SpamWeary.foo>
Re: String buffer instead of file handle? <o_c@invaliddomain.com>
Re: String buffer instead of file handle? <o_c@invaliddomain.com>
Re: String buffer instead of file handle? <spamhole@ntp.isc.org>
Re: String buffer instead of file handle? <David.Squire@no.spam.from.here.au>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 15 Sep 2006 00:12:51 -0700
From: "RR" <scubacuda@gmail.com>
Subject: Check IP range for DNSBL listing
Message-Id: <1158304371.545856.29600@h48g2000cwc.googlegroups.com>
I'm looking for a Perl script that will easily check ranges of IP
addresses that make it into DNSBLs, such as sbl-xbl.spamhaus.org and
bl.spamcop.net
I found RBLcheck and ARBLcheck
http://freshmeat.net/projects/rblcheck.pl/
http://www.unixwiz.net/tools/arblcheck.html
But unfortunately those don't allow me to put in ranges of IPs
Ideally, I'd like for these scripts to email me when there's a
violation. Any links to decent Perl mail scripts would be greatly
appreciated. Thus far, I've found
http://willmaster.com/possibilities/archives/wmp20020709001.shtml
http://willmaster.com/possibilities/archives/wmp20020716001.shtml
http://perl.about.com/od/email/a/perlemailsub.htm
------------------------------
Date: 15 Sep 2006 00:47:56 -0700
From: usenet@DavidFilmer.com
Subject: Re: Check IP range for DNSBL listing
Message-Id: <1158306476.088863.267020@i42g2000cwa.googlegroups.com>
RR wrote:
[ a multiposted question]
Don't multipost. It's rude.
------------------------------
Date: Fri, 15 Sep 2006 08:43:07 GMT
From: "Mumia W." <mumia.w.18.spam+nospam.usenet@earthlink.net>
Subject: Re: Check IP range for DNSBL listing
Message-Id: <vItOg.7896$v%4.3249@newsread1.news.pas.earthlink.net>
On 09/15/2006 02:12 AM, RR wrote:
> I'm looking for a Perl script that will easily check ranges of IP
> addresses that make it into DNSBLs, such as sbl-xbl.spamhaus.org and
> bl.spamcop.net
> [...]
http://search.cpan.org/search?query=DNSBL&mode=module
I hope one of those will help you. You'll still have to know
some perl to use those modules.
------------------------------
Date: Fri, 15 Sep 2006 09:48:44 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: I/O with raw disk
Message-Id: <eedm0r$8s2$1@nntp.fujitsu-siemens.com>
dcruncher4@aim.com wrote:
> How can I open a raw disk file and write to it. I have to write a
> program which will
> write few gigs of data to both raw disk and a cooked file to compare
> the write
> performance.
>=20
> Which functions to use for that.
Depending on your OS, you could (on Linux systems) use the appropriate=20
/dev entries for the disks, but that, too, will send it through the=20
buffer cache and all you measure is file system overhead.
On 2.4 kernels, you could set up /dev/raw devices to get around the=20
buffer cache, on 2.6 kernels you'd need to open the device with O_DIRECT.=
But, as Anno pointed out, it has not much to do with Perl.
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Fri, 15 Sep 2006 11:54:06 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: Maximum number of sockets
Message-Id: <450a08ca$0$5111$afc38c87@news.optusnet.com.au>
"A Ma" <angusma@attglobal.net> wrote in message
.
.
> May be I am hitting some other limit instead of FD_SETSIZE.
Did you check that FD_SETSIZE has in fact been set to your desired value ?
If socket.h contains:
#ifndef PERL_FD_SETSIZE
#define PERL_FD_SETSIZE 1000
#endif
then that means that PERL_FD_SETSIZE gets set to 1000 *only* if it was not
earlier defined. (I don't think it would have been defined earlier - but
it's probably a good idea to verify that.)
The following Inline::C script should print the actual value that
PERL_FD_SETSIZE is set to:
------------------------
use warnings;
use Inline C => Config =>
BUILD_NOISY => 1;
use Inline C => <<'EOC';
void get_size() {
printf("%d", PERL_FD_SETSIZE);
}
EOC
get_size();
------------------------
Cheers,
Rob
------------------------------
Date: Fri, 15 Sep 2006 12:05:11 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: Maximum number of sockets
Message-Id: <450a0b62$0$11969$afc38c87@news.optusnet.com.au>
"Sisyphus" <sisyphus1@nomail.afraid.org> wrote in message
news:450a08ca$0$5111$afc38c87@news.optusnet.com.au...
>
> "A Ma" <angusma@attglobal.net> wrote in message
> .
> .
> > May be I am hitting some other limit instead of FD_SETSIZE.
>
> Did you check that FD_SETSIZE has in fact been set to your desired value ?
>
> If socket.h contains:
>
> #ifndef PERL_FD_SETSIZE
> #define PERL_FD_SETSIZE 1000
> #endif
>
> then that means that PERL_FD_SETSIZE gets set to 1000 *only* if it was not
> earlier defined. (I don't think it would have been defined earlier - but
> it's probably a good idea to verify that.)
>
Actually ... I've just found that winsock2.h (in the MinGW/include folder)
sets FD_SETSIZE to 64, so there's a chance that PERL_FD_SETSIZE *has* been
defined earlier. You might need to remove the first and third lines (quoted
above) from socket.h, and then re-compile perl.
Anyway - first check to see just what the actual value of PERL_FD_SETSIZE
is.
Cheers,
Rob
------------------------------
Date: Fri, 15 Sep 2006 04:42:08 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Sep 15 2006
Message-Id: <J5MAE8.1o05@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-Hoge-0.03
http://search.cpan.org/~mahito/Acme-Hoge-0.03/
Replace "foo" in output with "hoge".
----
Chart-Clicker-1.1.0
http://search.cpan.org/~gphat/Chart-Clicker-1.1.0/
Powerful, extensible charting.
----
Class-DBI-Sybase-0.5
http://search.cpan.org/~michaelw/Class-DBI-Sybase-0.5/
Extensions to Class::DBI for Sybase
----
DBIx-Class-0.07002
http://search.cpan.org/~danieltwc/DBIx-Class-0.07002/
Extensible and flexible object <-> relational mapper.
----
Data-Template-0.0003
http://search.cpan.org/~ferreira/Data-Template-0.0003/
Generate data structures from templates
----
Declare-Constraints-Simple-0.03
http://search.cpan.org/~phaylon/Declare-Constraints-Simple-0.03/
Declarative Validation of Data Structures
----
Devel-Modlist-0.71
http://search.cpan.org/~rjray/Devel-Modlist-0.71/
Perl extension to collect module use information
----
ExtUtils-Command-1.11
http://search.cpan.org/~rkobes/ExtUtils-Command-1.11/
utilities to replace common UNIX commands in Makefiles etc.
----
ExtUtils-Manifest-1.47
http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.47/
utilities to write and check a MANIFEST file
----
ExtUtils-Manifest-1.48
http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.48/
utilities to write and check a MANIFEST file
----
HTML-Template-Compiled-0.75
http://search.cpan.org/~tinita/HTML-Template-Compiled-0.75/
Template System Compiles HTML::Template files to Perl code
----
HTML-Template-Compiled-Plugin-InlineImage-0.03
http://search.cpan.org/~tinita/HTML-Template-Compiled-Plugin-InlineImage-0.03/
Inline-Images with HTML::Template::Compiled
----
HTTP-QuickBase-1.51
http://search.cpan.org/~cvonroes/HTTP-QuickBase-1.51/
Create a web shareable database in under a minute
----
IO-Interface-1.02
http://search.cpan.org/~lds/IO-Interface-1.02/
Perl extension for access to network card configuration information
----
IO-Socket-Multicast6-0.01
http://search.cpan.org/~njh/IO-Socket-Multicast6-0.01/
Send and receive IPv4 and IPv6 multicast messages
----
Image-Size-3.01
http://search.cpan.org/~rjray/Image-Size-3.01/
read the dimensions of an image in several popular formats
----
Imager-0.54
http://search.cpan.org/~tonyc/Imager-0.54/
Perl extension for Generating 24 bit Images
----
Ingres-Utility-IIMonitor-0.02
http://search.cpan.org/~worm/Ingres-Utility-IIMonitor-0.02/
API to IIMONITOR Ingres utility for IIDBMS servers control
----
Ingres-Utility-IIMonitor-0.10
http://search.cpan.org/~worm/Ingres-Utility-IIMonitor-0.10/
API to IIMONITOR Ingres utility for IIDBMS servers control
----
Ingres-Utility-IINamu-0.01
http://search.cpan.org/~worm/Ingres-Utility-IINamu-0.01/
API to IINamu Ingres utility for (un)registering services with IIGCN
----
Jabber-Lite-0.6
http://search.cpan.org/~beecee/Jabber-Lite-0.6/
Standalone library for communicating with Jabber servers.
----
Jabber-Lite-0.7
http://search.cpan.org/~beecee/Jabber-Lite-0.7/
Standalone library for communicating with Jabber servers.
----
Math-Symbolic-Custom-CCompiler-1.01
http://search.cpan.org/~smueller/Math-Symbolic-Custom-CCompiler-1.01/
Compile Math::Symbolic trees to C
----
Net-Pcap-Reassemble-0.02
http://search.cpan.org/~jraftery/Net-Pcap-Reassemble-0.02/
IP fragment reassembly for Net::Pcap
----
Output-Rewrite-0.03
http://search.cpan.org/~mahito/Output-Rewrite-0.03/
Rewrite your script output.
----
PAR-Filter-Squish-0.02
http://search.cpan.org/~smueller/PAR-Filter-Squish-0.02/
PAR filter for reducing code size
----
PAR-Repository-0.12
http://search.cpan.org/~smueller/PAR-Repository-0.12/
Create and modify PAR repositories
----
PAR-Repository-Client-0.11
http://search.cpan.org/~smueller/PAR-Repository-Client-0.11/
Access PAR repositories
----
PDF-Table-0.9
http://search.cpan.org/~omega/PDF-Table-0.9/
A utility class for building table layouts in a PDF::API2 object.
----
POE-Component-Daemon-0.1001
http://search.cpan.org/~gwyn/POE-Component-Daemon-0.1001/
Handles all the housework for a daemon.
----
POE-XS-Queue-Array-0.003
http://search.cpan.org/~tonyc/POE-XS-Queue-Array-0.003/
an XS implementation of POE::Queue::Array.
----
Params-Util-0.18
http://search.cpan.org/~adamk/Params-Util-0.18/
Simple, compact and correct param-checking functions
----
Params-Util-0.19
http://search.cpan.org/~adamk/Params-Util-0.19/
Simple, compact and correct param-checking functions
----
Pod-Webserver-3.04
http://search.cpan.org/~arandal/Pod-Webserver-3.04/
minimal web server to serve local Perl documentation
----
SMS-Send-DE-MeinBMW-0.02
http://search.cpan.org/~borisz/SMS-Send-DE-MeinBMW-0.02/
An SMS::Send driver for the www.meinbmw.de website
----
Set-Object-1.18
http://search.cpan.org/~samv/Set-Object-1.18/
set of objects and strings
----
Socialtext-Resting-0.03
http://search.cpan.org/~synedra/Socialtext-Resting-0.03/
module for accessing Socialtext REST APIs
----
Socket-Multicast6-0.01
http://search.cpan.org/~njh/Socket-Multicast6-0.01/
Constructors and constants for IPv4 and IPv6 multicast socket operations.
----
Template-Plugin-JSON-0.02
http://search.cpan.org/~nuffin/Template-Plugin-JSON-0.02/
Adds a .json vmethod for all TT values.
----
Test-Count-0.0101
http://search.cpan.org/~shlomif/Test-Count-0.0101/
Module for keeping track of the number of tests in a Test Script.
----
Tripletail-0.18
http://search.cpan.org/~hio/Tripletail-0.18/
Tripletail, Framework for Japanese Web Application
----
Verilog-Perl-2.360
http://search.cpan.org/~wsnyder/Verilog-Perl-2.360/
----
WebService-ISBNDB-0.12
http://search.cpan.org/~rjray/WebService-ISBNDB-0.12/
----
XML-Compile-0.06
http://search.cpan.org/~markov/XML-Compile-0.06/
Compilation based XML processing
----
XML-SAX-Writer-0.50
http://search.cpan.org/~dahut/XML-SAX-Writer-0.50/
SAX2 Writer
----
classes-0.940
http://search.cpan.org/~rmuhle/classes-0.940/
conventional Perl 5 classes
----
v6-alpha-0.015
http://search.cpan.org/~fglock/v6-alpha-0.015/
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Fri, 15 Sep 2006 11:38:56 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: perl on windows - possible bug?
Message-Id: <450a053b$0$22358$afc38c87@news.optusnet.com.au>
<lililevy@hotmail.com> wrote in message
news:1158247266.145511.216690@m73g2000cwd.googlegroups.com...
> Hello,
>
> I'm using perl58.dll (version 5.8.4, build 810) in a c++ application
> with several threads that runs on win2000SP4.
> Every thread creates a perl interpreter that runs a perl script from an
> arbitrary file.
> After a while I'm experiencing a deadlock.
> I can see that I have a thread that is stack in the function
> _alloc_osfhnd (Microsoft function from the msvcrt.dll that is called
> from the _open function).
>
> I found this link http://bugs.mysql.com/bug.php?id=12071 that describes
> a Microsoft bug in _alloc_osfhnd that might cause this deadlock.
>
.
.
>
> Has anyone experienced this problem before?
> Is it really a Microsoft bug that affects perl?
> Can another version of perl solve the problem?
> Can another version of OS solve the problem?
>
If you don't find an answer here, try posting to perlmonks. There's a guy
there (BrowserUk) who is particularly knowledgeable on threads issues with
Win32.
If you could provide some (minimal) code that demonstrates the problem (and
that others can run on their own machines), it would improve your chances of
getting assistance - both here and on perlmonks ... and on any other forum
to which you post.
(I acknowledge that it's not always feasible to provide such code :-)
Cheers,
Rob
------------------------------
Date: 15 Sep 2006 07:22:10 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
Message-Id: <450a54a1$0$47255$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.6 $)
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
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: 15 Sep 2006 01:00:05 -0700
From: "Brian McCauley" <nobull67@gmail.com>
Subject: Re: Preventing changes to a module's variables in mod_perl
Message-Id: <1158307205.423260.214610@p79g2000cwp.googlegroups.com>
max@maxgraphic.com wrote:
> I have a module that exists as a central data store, returning simple
> scalars or references to larger structures. All of its data is stored
> in a big hash, and I use AUTOLOAD to return the requested value.
>
> The problem is that, with mod_perl, if the script that uses the module
> changes the data (which with auto-vivication is pretty easy), the data
> is changed for all subsequent scripts using that module run by that
> particular apache child, which leads to the usual hair-pulling
> intermittent bugs that mod_perl users historically puzzle over.
>
> I've looked at a couple locking options, but the problem is that the
> data can be arbitrarily deep references (which seems to rule out
> Hash::Util).
The Readonly module claims to recursively follow deep structures (by
default).
Is there a reason you can't simply make the central data store readonly?
------------------------------
Date: 14 Sep 2006 20:15:11 -0700
From: fatgirl.brown@gmail.com
Subject: sort hash values does not work
Message-Id: <1158290110.965494.266150@d34g2000cwd.googlegroups.com>
Hi, I have a two-dim array as hash value and I want to sort it:
# <code>
#!/usr/bin/perl -w
push @{$hash{"test"}}, [10, "hi1"];
push @{$hash{"test"}}, [3, "hi2"];
push @{$hash{"test"}}, [5, "hi3"];
push @{$hash{"test"}}, [1111, "hi4"];
@{$hash{"test"}} = sort {$a <=> $b} @{$hash{"test"}};
print join " ", @{$hash{"test"}[0]};
print "\n";
# </code>
But it prints "5 hi3". So it put the 5 first, although the 3 should be
first after it's sorted. How can I sort so that it's 3, 5, 10, 1111?
Thanks!!
Junupa
------------------------------
Date: 14 Sep 2006 21:04:13 -0700
From: "Xicheng Jia" <xicheng@gmail.com>
Subject: Re: sort hash values does not work
Message-Id: <1158293053.204269.98550@p79g2000cwp.googlegroups.com>
fatgirl.brown@gmail.com wrote:
> Hi, I have a two-dim array as hash value and I want to sort it:
>
> # <code>
> #!/usr/bin/perl -w
>
> push @{$hash{"test"}}, [10, "hi1"];
> push @{$hash{"test"}}, [3, "hi2"];
> push @{$hash{"test"}}, [5, "hi3"];
> push @{$hash{"test"}}, [1111, "hi4"];
>
> @{$hash{"test"}} = sort {$a <=> $b} @{$hash{"test"}};
here you are comparing two array references, to compare based on one of
their elements, you may want to dereference them, like:
@{$hash{"test"}} = sort { $a->[0] <=> $b->[0] } @{$hash{"test"}};
Xicheng
------------------------------
Date: 14 Sep 2006 15:26:40 -0700
From: "danparker276@yahoo.com" <danparker276@yahoo.com>
Subject: Re: String buffer instead of file handle?
Message-Id: <1158272800.322715.232850@i3g2000cwc.googlegroups.com>
I wish I could do it in .net. We gotta use linux servers for much of
the stuff where I work. Problem is I finish the .net stuff so quickly
that I have to work on this other perl and java crap. I used to
program in Java a lot, but .NET just blows it away now.
My MySpace friends rule, see I'm really popular because I breakdance on
stage at clubs, and chicks see how good looking I am and want to talk
to me. I'm kissing my biceps as i'm typing this message now. You can
see me at www.bboy360.com, I back up what I say.
RedGrittyBrick wrote:
> danparker276@yahoo.com wrote:
> > .NET 2.0 blows
>
> I was wondering why you were struggling with perl when you could be
> dashing off a quick .NET 2.0 replacement.
>
> Aren't any of your 9000 MySpace friends any good at .NET 2.0 either?
> Maybe they can help?
------------------------------
Date: Thu, 14 Sep 2006 23:50:54 +0100
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: String buffer instead of file handle?
Message-Id: <tIqdnZ154KT7R5TYRVnyhw@bt.com>
danparker276@yahoo.com wrote:
> I have to work on this other perl and java crap.
You *have* to? You're not some kind of a wimp just pretending to be a
stud are you?
> but .NET just blows
You said that already.
> My MySpace friends rule,
They suck at .NET 2.0 though don't they.
------------------------------
Date: Fri, 15 Sep 2006 00:11:44 +0100
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: String buffer instead of file handle?
Message-Id: <W_ydnQnePf7VQpTYnZ2dnUVZ8tKdnZ2d@bt.com>
danparker276@yahoo.com wrote:
> I love chicks that can't read.
This is where your analogy breaks down. I suspect you can read, at least
a little bit. If you're a chick then your name suggests you're not the
sort of chick anyone would invite in to watch Prison Break.
Q.E.D.
------------------------------
Date: Thu, 14 Sep 2006 19:40:42 -0700
From: "Ottis Caw" <o_c@invaliddomain.com>
Subject: Re: String buffer instead of file handle?
Message-Id: <1158287309_4031@sp6iad.superfeed.net>
Ala Qumsieh wrote:
> danparker276@yahoo.com wrote:
>
> > Oh yeah, and I top-posted on purpose. Everyone on this group is so
> > stuck up. .NET 2.0 blows everything away anyway. At least on their
> > formus, people from microsoft will answer questions instead of "Look
> > at the docs"
>
> Well, they are being paid by Microsoft to do that. If somebody (for
> example, you) pays me, I'll answer too. Otherwise, you don't really
> get to complain.
>
> --Ala
A completely false presumption. Most of the people on those forums are
in fact people who volunteer their time. The difference is the attitude.
Yes, I fully agree docs should be checked and search engines queried,
but I got the distinct impression that either there were no docs for
this module or they didn't lead to an answer the OP was looking for (I
cannot say either way as I am not familiar with this particular module.
The biggest problem with this group and others that display the same
attitudes, is that many who frequent this group seem to presume that
most, shall we say, inexperienced users are automatically clueless. At
least this is the common vide I feel from threads like this. Why is it
so difficult to give people the benefit of the doubt. Why not offer a
little useful knowledge. Pointing to the docs works. The addition of an
in-body snippet is even better, as it better serves the archives.
You not be paid to help people, but then again, who said anyone here was
entitled to payment? Last I checked, that was never the way UseNet
worked. Wasn't the main point of mediums like UseNet is for the _free_
exchange of information and knowledge?
--
OC
------------------------------
Date: Thu, 14 Sep 2006 19:48:58 -0700
From: "Ottis Caw" <o_c@invaliddomain.com>
Subject: Re: String buffer instead of file handle?
Message-Id: <1158287805_4035@sp6iad.superfeed.net>
Tad McClellan wrote:
> danparker276@yahoo.com <danparker276@yahoo.com> wrote:
>
>
>> .NET 2.0 blows everything away anyway. At least on their
>> formus, people from microsoft will answer questions instead of "Look
>> at the docs"
>
>
> That's because Bill's mindless minions _need_ someone to hold their
> hand.
>
> This programming stuff is pretty scary!
Honestly, are these types of post _REALLY_ necessary? I mean, really, so
not everyone knows as much as you do with computers. Ok, fine. But
doesn't mean everyone coming with what may be a simple problem from your
perspective, but from someone who is, shall we say, young with Perl
and/or the IT scene in general, it just might of been a legitimate
question.
My point I'm trying to make is perhaps this approach you often take
seems take, with posts such as the one I quoted here, seem to serve no
one and certainly doesn't further the thread in the right direction.
--
OC
------------------------------
Date: Thu, 14 Sep 2006 19:55:04 -0700
From: "Steve K." <spamhole@ntp.isc.org>
Subject: Re: String buffer instead of file handle?
Message-Id: <4muj0aF7tqgeU1@individual.net>
Mumia W. wrote:
| On 09/13/2006 05:31 PM, danparker276@yahoo.com wrote:
| > Tad,
| > " open($fh, '>', \$variable)" This would work perfect, just not the
| > right version of perl. [...]
|
| Do you mean that you can't install and use IO::Scalar?
That assumes he knows of it. Why can't anyone realize not everyone
memorizes all of CPAN by heart. Yes you can search it, but sometimes
it's not a straight forward task as it may seem, especially if you don't
know what to look for (yet) in the first place, and hence a perfectly
acceptable reason for posting such a post that the OP posted...
| If you haven't tried it, you probably can.
Heres a link.
http://search.cpan.org/search?query=IO%3A%3AScalar&mode=all
You can also attempt to install it using the CPAN shell from the
commandline:
$ perl -MCPAN -e shell
install IO::Scalar
------------------------------
Date: Fri, 15 Sep 2006 10:27:04 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: String buffer instead of file handle?
Message-Id: <eedrl8$hvv$1@gemini.csx.cam.ac.uk>
Steve K. wrote:
> Mumia W. wrote:
> | On 09/13/2006 05:31 PM, danparker276@yahoo.com wrote:
> | > Tad,
> | > " open($fh, '>', \$variable)" This would work perfect, just not the
> | > right version of perl. [...]
> |
> | Do you mean that you can't install and use IO::Scalar?
>
> That assumes he knows of it. Why can't anyone realize not everyone
> memorizes all of CPAN by heart.
It had already been pointed out to him in this thread. Why can't some
folk check a thread before jumping in?
DS
------------------------------
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 9727
***************************************
