[30427] in Perl-Users-Digest
Perl-Users Digest, Issue: 1670 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 24 03:09:41 2008
Date: Tue, 24 Jun 2008 00:09:05 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 24 Jun 2008 Volume: 11 Number: 1670
Today's topics:
change a single digit to corresponding English word <xiaoxia2005a@yahoo.com>
Re: change a single digit to corresponding English word <jurgenex@hotmail.com>
Re: change a single digit to corresponding English word <noreply@gunnar.cc>
Re: change a single digit to corresponding English word <jack@home.net>
Re: How to ensure I'm doing lwp with https correctly? <ced@blv-sam-01.ca.boeing.com>
Re: How to match string end for a multiline string? <tadmc@seesig.invalid>
Re: I hate CGI.pm <joe+usenet@sunstarsys.com>
new CPAN modules on Tue Jun 24 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Printing Problems dummy@phony.info
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 23 Jun 2008 20:06:13 -0700 (PDT)
From: April <xiaoxia2005a@yahoo.com>
Subject: change a single digit to corresponding English word
Message-Id: <3f8e4157-755b-426e-92a5-0d0fe7b241b6@k13g2000hse.googlegroups.com>
Will the following change a single digit to corresponding English
word, like 3 to three, 5 to five, etc?
$char = $numbers[$char]
------------------------------
Date: Tue, 24 Jun 2008 03:19:53 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: change a single digit to corresponding English word
Message-Id: <app064lbgc8epdc61qpe1tfa1a5chuh4hs@4ax.com>
April <xiaoxia2005a@yahoo.com> wrote:
>Will the following change a single digit to corresponding English
>word, like 3 to three, 5 to five, etc?
>
>$char = $numbers[$char]
Assuming that the array @numbers contains the string 'three' at index 3,
then yes, after this assignment $char will contain the string 'three'.
In which case $char is a very poor choice for an identifier.
jue
------------------------------
Date: Tue, 24 Jun 2008 05:26:10 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: change a single digit to corresponding English word
Message-Id: <6cb7qqF3fvlmcU1@mid.individual.net>
April wrote:
> Will the following change a single digit to corresponding English
> word, like 3 to three, 5 to five, etc?
>
> $char = $numbers[$char]
Only if the array @numbers, with those words, exists.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 24 Jun 2008 00:42:09 -0600
From: "Jack D" <jack@home.net>
Subject: Re: change a single digit to corresponding English word
Message-Id: <OG08k.129052$2%5.19510@fe39.usenetserver.com>
"April" <xiaoxia2005a@yahoo.com> wrote in message
news:3f8e4157-755b-426e-92a5-0d0fe7b241b6@k13g2000hse.googlegroups.com...
> Will the following change a single digit to corresponding English
> word, like 3 to three, 5 to five, etc?
>
> $char = $numbers[$char]
In addition to the answers already given, I thought I would also point out
that there is a module that does this very thing:
http://search.cpan.org/~sburke/Lingua-EN-Numbers-1.01/
Jack
------------------------------
Date: Mon, 23 Jun 2008 16:22:52 -0700 (PDT)
From: "comp.llang.perl.moderated" <ced@blv-sam-01.ca.boeing.com>
Subject: Re: How to ensure I'm doing lwp with https correctly?
Message-Id: <b47e08b8-4536-41e7-867e-99a6b2e24d9a@w8g2000prd.googlegroups.com>
On Jun 23, 11:29 am, PugetSoundSyl...@gmail.com wrote:
>
> I'm using LWP for programatic access to a website. I'm using https,
> and have installed Crypt::SSLeay (hopefully correctly).
>
> What I'd like to do is make sure that my https access is actually
> correctly set up, and that I am accessing everything securely. Any
> ideas on how I can double-check that everything is happening
> correctly? Or is there something I can use to audit my connection?
> If I didn't do the Crypt::SSLeay install correctly, would https access
> just not work, or would it just default to http?
>
If Crypt::SSLeay installed successfully
and passed its test suite, you can be
reasonably assured that SSL transactions
occur. You can confirm actual details of the exchange by setting:
$ENV{HTTPS_DEBUG} = 1
before initiating the connection. See:
perldoc Crypt::SSLeay.
Also, if using Perl's LWP module, you
can add:
use LWP::Debug qw/+/
for other details of the exchange>
See perldoc LWP::Debug for less
verbose settings.
Here's an example with HTTPS_DEBUG and
LWP::Debug set:
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
LWP::UserAgent::new: ()
HTTP::Cookies::add_cookie_header: Checking ... for cookies
LWP::UserAgent::send_request: GET https://....
LWP::UserAgent::_need_proxy: Not proxied
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server key exchange A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 read server hello A
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server key exchange A
--
Charles DeRykus
------------------------------
Date: Mon, 23 Jun 2008 21:32:35 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: How to match string end for a multiline string?
Message-Id: <slrng60n63.eop.tadmc@tadmc30.sbcglobal.net>
Peng Yu <PengYu.UT@gmail.com> wrote:
> $ matches line end.
No, it matches end of string, not end of line.
If used with //m, _then_ it matches end of line.
> When a string has multiple lines, how to much the
> last line end?
/$/
See it for yourself:
-------------------------------
#!/usr/bin/perl
use warnings;
use strict;
$_ = '
foo
bar
baz
';
s/$/END-OF-STRING/;
print;
-------------------------------
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 23 Jun 2008 21:12:26 -0400
From: Joe Schaefer <joe+usenet@sunstarsys.com>
Subject: Re: I hate CGI.pm
Message-Id: <873an3bpqd.fsf@gemini.sunstarsys.com>
Ben Bullock <benkasminbullock@gmail.com> writes:
> I tried to read the documentation for Catalyst, and it makes no sense
> to me - it looks like you have to buy a book and spend hours and hours
> to understand it. Since I don't usually even write web things, I don't
> want to spend a lot of time studying the systems - I just want a
> "better CGI module". Does it exist?
>
The Apache folks, myself included, got together to write libapreq2,
which provides APR::Request::CGI. Installing the module is a pita,
because it depends on apache2 and mod_perl2 being installed. But
as far as features and performance goes there are few perl modules
capable of matching it.
Migrating between APR::Request::CGI and APR::Request::Apache2 for
mod_perl2 is straightforward: just change the initial
APR::Request::CGI->handle() to APR::Request::Apache2->handle(). Otherwise
the behavior of the library should be identical between CGI and
mod_perl2.
One nice feature is that parameters and cookies are subclassable
objects, so you can change the FETCH behavior of the underlying
tables by changing their param_class or cookie_class. It's also
compatible with the basic param() API of CGI.pm, so you don't need
to read a whole lot of docs in order to make basic use of it.
--
Joe Schaefer
------------------------------
Date: Tue, 24 Jun 2008 04:42:23 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Jun 24 2008
Message-Id: <K2yAEn.22rx@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-NabeAtzz-0.01
http://search.cpan.org/~yappo/Acme-NabeAtzz-0.01/
One, Two, ???
----
Acme-PerlVMGolf-0.01
http://search.cpan.org/~tokuhirom/Acme-PerlVMGolf-0.01/
perl5 vm golf
----
Algorithm-Evolutionary-0.5.8
http://search.cpan.org/~jmerelo/Algorithm-Evolutionary-0.5.8/
Perl extension for performing paradigm-free evolutionary algorithms.
----
Algorithm-Evolutionary-0.58
http://search.cpan.org/~jmerelo/Algorithm-Evolutionary-0.58/
Perl extension for performing paradigm-free evolutionary algorithms.
----
Algorithm-Evolutionary-0.58_1
http://search.cpan.org/~jmerelo/Algorithm-Evolutionary-0.58_1/
Perl extension for performing paradigm-free evolutionary algorithms.
----
Algorithm-Evolutionary-0.59
http://search.cpan.org/~jmerelo/Algorithm-Evolutionary-0.59/
Perl extension for performing paradigm-free evolutionary algorithms.
----
Apache2-AuthZLDAP-0.02
http://search.cpan.org/~doumbzh/Apache2-AuthZLDAP-0.02/
Authorization module based on LDAP filters or LDAP groups
----
App-Addex-0.018
http://search.cpan.org/~rjbs/App-Addex-0.018/
generate mail tool configuration from an address book
----
App-Addex-Plugin-Hiveminder-0.002
http://search.cpan.org/~rjbs/App-Addex-Plugin-Hiveminder-0.002/
automatically add "to Hiveminder.com" addrs
----
App-Addex-Plugin-Nobody-0.001
http://search.cpan.org/~rjbs/App-Addex-Plugin-Nobody-0.001/
automatically add a recipient that goes nowhere
----
App-ErrorCalculator-1.02
http://search.cpan.org/~smueller/App-ErrorCalculator-1.02/
Calculations with Gaussian Error Propagation
----
App-Whiff-0.001
http://search.cpan.org/~rjbs/App-Whiff-0.001/
find the first executable of a series of alternatives
----
Applications-BackupAndRestore-0.021
http://search.cpan.org/~hooo/Applications-BackupAndRestore-0.021/
a linux frontend for tar
----
BDB-Wrapper-0.11
http://search.cpan.org/~hikarine/BDB-Wrapper-0.11/
Wrapper module for BerkeleyDB.pm
----
Bundle-STRO-1.01
http://search.cpan.org/~stro/Bundle-STRO-1.01/
----
CPAN-Reporter-Smoker-0.15
http://search.cpan.org/~dagolden/CPAN-Reporter-Smoker-0.15/
Turnkey CPAN Testers smoking
----
Crypt-Util-0.07
http://search.cpan.org/~nuffin/Crypt-Util-0.07/
A lightweight Crypt/Digest convenience API
----
DBIx-Class-Graph-0.01_01
http://search.cpan.org/~perler/DBIx-Class-Graph-0.01_01/
Represent a graph in a relational database using DBIC
----
DBIx-Web-0.75
http://search.cpan.org/~makarow/DBIx-Web-0.75/
Active Web Database Layer
----
Devel-Hints-Lexical-0.10
http://search.cpan.org/~chocolate/Devel-Hints-Lexical-0.10/
lexical pragma utils
----
Devel-Pragma-0.11
http://search.cpan.org/~chocolate/Devel-Pragma-0.11/
helper functions for developers of lexical pragmas
----
Devel-Pragma-0.12
http://search.cpan.org/~chocolate/Devel-Pragma-0.12/
helper functions for developers of lexical pragmas
----
Encode-ZapCP1252-0.12
http://search.cpan.org/~dwheeler/Encode-ZapCP1252-0.12/
Zap Windows Western Gremlins
----
GRID-Machine-0.097
http://search.cpan.org/~casiano/GRID-Machine-0.097/
Remote Procedure Calls over a SSH link
----
Geo-Hashing-0.04
http://search.cpan.org/~zigdon/Geo-Hashing-0.04/
Perl library to calculate Geohashing points
----
Goto-Cached-0.10
http://search.cpan.org/~chocolate/Goto-Cached-0.10/
a fast drop-in replacement for Perl's O(n) goto
----
HTML-Table-2.08a
http://search.cpan.org/~ajpeacock/HTML-Table-2.08a/
produces HTML tables
----
HTTP-Body-1.04
http://search.cpan.org/~agrundma/HTTP-Body-1.04/
HTTP Body Parser
----
IPC-Messaging-0.01_08
http://search.cpan.org/~gruber/IPC-Messaging-0.01_08/
process handling and message passing, Erlang style
----
LSF_Base_0.07
http://search.cpan.org/~lsfisv/LSF_Base_0.07/
----
LSF_Batch_0.06
http://search.cpan.org/~lsfisv/LSF_Batch_0.06/
----
Lingua-Strfname-0.12
http://search.cpan.org/~dwheeler/Lingua-Strfname-0.12/
Formats people's names
----
Math-GMPz-0.26
http://search.cpan.org/~sisyphus/Math-GMPz-0.26/
perl interface to the GMP library's integer (mpz) functions.
----
Module-Install-Substitute-0.03
http://search.cpan.org/~ruz/Module-Install-Substitute-0.03/
substitute values into files before install
----
Net-LDAP-AutoDNs-0.0.0
http://search.cpan.org/~vvelox/Net-LDAP-AutoDNs-0.0.0/
Automatically make some default decisions some LDAP DNs and scopes.
----
Net-SFTP-Foreign-1.39
http://search.cpan.org/~salva/Net-SFTP-Foreign-1.39/
SSH File Transfer Protocol client
----
Net-SNMP-Mixin-Dot1dStp-0.03
http://search.cpan.org/~gaissmai/Net-SNMP-Mixin-Dot1dStp-0.03/
mixin class for 802.1D spanning tree information
----
Net-Squid-Auth-Engine-0.01.02
http://search.cpan.org/~lmc/Net-Squid-Auth-Engine-0.01.02/
External Credentials Authentication for Squid HTTP Cache
----
POE-Component-Client-Nowa-0.02
http://search.cpan.org/~woremacx/POE-Component-Client-Nowa-0.02/
POE Client of the Nowa
----
POE-Component-Client-Stomp-0.07
http://search.cpan.org/~kesteb/POE-Component-Client-Stomp-0.07/
Perl extension for the POE Environment
----
POE-Component-Pool-DBI-0.012
http://search.cpan.org/~tag/POE-Component-Pool-DBI-0.012/
Simplified DBI access through a pooled resource.
----
POE-Filter-BigBrother-0.10
http://search.cpan.org/~yblusseau/POE-Filter-BigBrother-0.10/
protocol abstractions for BigBrother streams
----
Params-CallbackRequest-1.19
http://search.cpan.org/~dwheeler/Params-CallbackRequest-1.19/
Functional and object-oriented callback architecture
----
PerlIO-Util-0.50
http://search.cpan.org/~gfuji/PerlIO-Util-0.50/
A selection of general PerlIO utilities
----
Proc-Exists-0.90
http://search.cpan.org/~brianski/Proc-Exists-0.90/
quickly check for process existence
----
Queue-Q4M-0.00002
http://search.cpan.org/~dmaki/Queue-Q4M-0.00002/
Simple Interface To q4m
----
Queue-Q4M-0.00003
http://search.cpan.org/~dmaki/Queue-Q4M-0.00003/
Simple Interface To q4m
----
Sepia-0.97
http://search.cpan.org/~seano/Sepia-0.97/
Simple Emacs-Perl Interface
----
Socket-Class-1.23
http://search.cpan.org/~chrmue/Socket-Class-1.23/
A class to communicate with sockets
----
Sort-Packed-0.03
http://search.cpan.org/~salva/Sort-Packed-0.03/
Sort records packed in a vector
----
Statistics-ANOVA-0.02
http://search.cpan.org/~rgarton/Statistics-ANOVA-0.02/
Perform oneway analyses of variance
----
Sys-Manage-0.60
http://search.cpan.org/~makarow/Sys-Manage-0.60/
Systems management commands/scripts environment
----
Test-TempDir-0.03
http://search.cpan.org/~nuffin/Test-TempDir-0.03/
Temporary files support for testing.
----
UUID-Random-0.03
http://search.cpan.org/~perler/UUID-Random-0.03/
----
UUID-Random-0.03_01
http://search.cpan.org/~perler/UUID-Random-0.03_01/
Generate random uuid strings
----
UUID-Random-0.04
http://search.cpan.org/~perler/UUID-Random-0.04/
Generate random uuid strings
----
User-Simple-1.37
http://search.cpan.org/~gwolf/User-Simple-1.37/
Simple user sessions management
----
WWW-Blogger-2008.0623
http://search.cpan.org/~ermeyers/WWW-Blogger-2008.0623/
Blogger Development Interface (BDI)
----
WWW-IndexParser-0.91
http://search.cpan.org/~jeb/WWW-IndexParser-0.91/
Fetch and parse the directory index from a web server
----
WWW-YouTube-2008.0623
http://search.cpan.org/~ermeyers/WWW-YouTube-2008.0623/
YouTube Development Interface (YTDI)
----
WebService-Nowa-0.02
http://search.cpan.org/~woremacx/WebService-Nowa-0.02/
Perl interface to the Nowa
----
WikiText-Socialtext-0.11
http://search.cpan.org/~ingy/WikiText-Socialtext-0.11/
Socialtext WikiText Module
----
Win32-EnvProcess-0.05
http://search.cpan.org/~clive/Win32-EnvProcess-0.05/
Perl extension to set or get environment variables from other processes
----
Win32-NetAdmin-0.10
http://search.cpan.org/~jdb/Win32-NetAdmin-0.10/
Manage network groups and users in Perl
----
Win32-NetResource-0.056
http://search.cpan.org/~jdb/Win32-NetResource-0.056/
Manage network resources in Perl
----
Win32-Registry-0.10
http://search.cpan.org/~jdb/Win32-Registry-0.10/
accessing the Windows registry [obsolete, use Win32::TieRegistry]
----
XML-Compile-0.86
http://search.cpan.org/~markov/XML-Compile-0.86/
Compilation based XML processing
----
XML-LibXSLT-Easy-0.02
http://search.cpan.org/~nuffin/XML-LibXSLT-Easy-0.02/
DWIM XSLT processing with XML::LibXSLT
----
XUL-App-0.02
http://search.cpan.org/~agent/XUL-App-0.02/
Nifty XUL apps in a XUL::App
----
XUL-App-0.03
http://search.cpan.org/~agent/XUL-App-0.03/
Nifty XUL apps in a XUL::App
----
XUL-App-0.04
http://search.cpan.org/~agent/XUL-App-0.04/
Nifty XUL apps in a XUL::App
----
XUL-App-0.05
http://search.cpan.org/~agent/XUL-App-0.05/
Nifty XUL apps in a XUL::App
----
Xen-Control-0.01
http://search.cpan.org/~jkutej/Xen-Control-0.01/
control and fetch information about xen domains
----
mysubs-0.10
http://search.cpan.org/~chocolate/mysubs-0.10/
lexical subroutines
----
mysubs-0.11
http://search.cpan.org/~chocolate/mysubs-0.11/
lexical subroutines
----
mysubs-0.12
http://search.cpan.org/~chocolate/mysubs-0.12/
lexical subroutines
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/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 24 Jun 2008 06:14:12 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <Ug08k.9641$xZ.8793@nlpi070.nbdc.sbc.com>
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.8 $)
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.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 23 Jun 2008 15:34:02 -0700
From: dummy@phony.info
Subject: Re: Printing Problems
Message-Id: <oq7064d44539kpsn4o8sf18gc6118t8v8j@4ax.com>
On Thu, 19 Jun 2008 03:14:22 -0700 (PDT), dakin999 <akhilshri@gmail.com>
wrote:
>Hi,
>
>I have following code which works ok. It does following:
>
>1. reads data from a input file
>2. puts the data into seperate variables in a array
>3. reads from this array and prints out to another file
>
>It works except that it prints the same record 4 times. I can see I
>have missed some thing in my array definition as their are 4 elements
>in array, it is printing 4 times each element and then moving to next
>element till it reaches eof().
>
>
>while (<input>) #reading a line from file
># Read the line into a set of variables
> ($1,$2,$3,$4)=split(/,/,$_);
>....
>....
># Buid an array with these varaibles
> my @array = ([$1, $2, $3, $4]);
> foreach my $r(@array) {
> foreach (@$r){
>
>... print <out> "$1\n";
> print <out> "$2\n";
> print <out> "$3\n";
> print <out> "$4\n";
> print <out> "\n";
>
>
>The out put is coming like this:
>
>yellow
>blue
>orange
>red
>
>yellow
>blue
>orange
>red
>
>yellow
>blue
>orange
>red
>
>yellow
>blue
>orange
>red
>
>black
>white
>red
>pink
>
>black
>white
>red
>pink
>
>black
>white
>red
>pink
>
>black
>white
>red
>pink
>
>Clearly it should just print one time and go to the next record....
>
>Please suggest.
You're making it too complicated; only one loop necessary.
for each line: split on comma, join with new line and print:
use strict; use warnings;
print join("\n",split(/,/)),"\n" while (<DATA>);
__DATA__
yellow,blue,orange,red
black,white,red,pink
green,cerise,purple,terracotta
gray,turquoise,snow,navy
------------------------------
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 V11 Issue 1670
***************************************
