[30110] in Perl-Users-Digest
Perl-Users Digest, Issue: 1353 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 11 06:11:08 2008
Date: Tue, 11 Mar 2008 03: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, 11 Mar 2008 Volume: 11 Number: 1353
Today's topics:
class global variable?(from Perltoot document) <jh3ang@gmail.com>
Re: class global variable?(from Perltoot document) <joost@zeekat.nl>
Fastest way to send file to browser <howachen@gmail.com>
Re: Fastest way to send file to browser <devnull4711@web.de>
new CPAN modules on Tue Mar 11 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Regex newbie <nitte.sudhir@gmail.com>
Re: Regex newbie <darthludi@gmail.com>
Re: regular expression with split goes wrong ? <jh3ang@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 10 Mar 2008 21:45:40 -0700 (PDT)
From: jh3an <jh3ang@gmail.com>
Subject: class global variable?(from Perltoot document)
Message-Id: <f8cd740f-41f6-4ad7-909a-e307bc105556@h25g2000hsf.googlegroups.com>
Please give me your advice :(
I was reading perltoot document, and I got stuck the following class
global variable concept.
HELP!!
Why global variable should be accessed by hash like this? :
$self->{"_CENSUS"}
Perltoot doc:
Accessing Class Data
It turns out that this is not really a good way to go about handling
class data. A good scalable rule is that you must never reference
class data directly from an object method. Otherwise you aren't
building a scalable, inheritable class. The object must be the
rendezvous point for all operations, especially from an object method.
The globals (class data) would in some sense be in the "wrong" package
in your derived classes. In Perl, methods execute in the context of
the class they were defined in, not that of the object that triggered
them. Therefore, namespace visibility of package globals in methods is
unrelated to inheritance.(WHAT THE HECK HE IS TALKING ABOUT @.@??????)
Got that? Maybe not. Ok, let's say that some other class
"borrowed" (well, inherited) the DESTROY method as it was defined
above. When those objects are destroyed, the original $Census variable
will be altered, not the one in the new class's package namespace.
Perhaps this is what you want, but probably it isn't.
(WHAT THE HECK HE IS TALKING ABOUT @.@??????)
------------------------------
Date: Tue, 11 Mar 2008 07:31:07 +0100
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: class global variable?(from Perltoot document)
Message-Id: <87pru1ixg4.fsf@zeekat.nl>
jh3an <jh3ang@gmail.com> writes:
> Please give me your advice :(
> I was reading perltoot document, and I got stuck the following class
> global variable concept.
> HELP!!
>
> Why global variable should be accessed by hash like this? :
> $self->{"_CENSUS"}
Note that that's not just a hash, $self is an object, and
$self->{_CENSUS} in the original text is a reference to a shared lexical
variable, not a package variable.
> Perltoot doc:
> Accessing Class Data
> It turns out that this is not really a good way to go about handling
> class data. A good scalable rule is that you must never reference
> class data directly from an object method. Otherwise you aren't
> building a scalable, inheritable class. The object must be the
> rendezvous point for all operations, especially from an object method.
> The globals (class data) would in some sense be in the "wrong" package
> in your derived classes. In Perl, methods execute in the context of
> the class they were defined in, not that of the object that triggered
> them. Therefore, namespace visibility of package globals in methods is
> unrelated to inheritance.(WHAT THE HECK HE IS TALKING ABOUT @.@??????)
That part relates to the "Class Data" section directly above it. Maybe
you should read that again.
> Got that? Maybe not. Ok, let's say that some other class
> "borrowed" (well, inherited) the DESTROY method as it was defined
> above. When those objects are destroyed, the original $Census variable
> will be altered, not the one in the new class's package namespace.
> Perhaps this is what you want, but probably it isn't.
> (WHAT THE HECK HE IS TALKING ABOUT @.@??????)
<MS Paperclip>It seems you're having trouble grasping the potential
problems with inheritance. Maybe you should just try and build some
inheriting classes and objects and you'll find out</MS Paperclip>
--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/
------------------------------
Date: Tue, 11 Mar 2008 00:48:49 -0700 (PDT)
From: howa <howachen@gmail.com>
Subject: Fastest way to send file to browser
Message-Id: <c840b7ed-cb5f-4fc4-80c3-c9e1cacddaa6@s8g2000prg.googlegroups.com>
In order to hidden the real path, I send the png file via CGI, e.g.
##############
print "Content-type:image/png\n\n";
my $file = "test.png";
open INPUT_FILE, "$file" or die "Couldn't open file: $!";
while( sysread(INPUT_FILE, $data, 10240) ) {
print $data;
}
close FILE;
##############
Any faster/better method?
Thanks.
------------------------------
Date: Tue, 11 Mar 2008 09:23:55 +0100
From: Frank Seitz <devnull4711@web.de>
Subject: Re: Fastest way to send file to browser
Message-Id: <63mtstF28h6p5U1@mid.individual.net>
howa wrote:
> In order to hidden the real path, I send the png file via CGI, e.g.
>
> [Perl program]
>
> Any faster/better method?
An alias (HTTP server directive).
Frank
--
Dipl.-Inform. Frank Seitz; http://www.fseitz.de/
Anwendungen für Ihr Internet und Intranet
Tel: 04103/180301; Fax: -02; Industriestr. 31, 22880 Wedel
------------------------------
Date: Tue, 11 Mar 2008 04:42:20 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Mar 11 2008
Message-Id: <JxJuEK.t7D@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.
App-Bondage-0.2.5
http://search.cpan.org/~hinrik/App-Bondage-0.2.5/
A featureful IRC bouncer based on POE::Component::IRC
----
App-MadEye-0.02
http://search.cpan.org/~tokuhirom/App-MadEye-0.02/
enterprise-class monitoring solutions
----
Archive-Heritrix-0.01
http://search.cpan.org/~allenday/Archive-Heritrix-0.01/
Perl extension for processing Heritrix archive (.arc) files
----
Archive-Heritrix-0.02
http://search.cpan.org/~allenday/Archive-Heritrix-0.02/
Perl extension for processing Heritrix archive (.arc) files
----
Archive-Tar-Wrapper-0.11
http://search.cpan.org/~mschilli/Archive-Tar-Wrapper-0.11/
API wrapper around the 'tar' utility
----
BigIP-ParseConfig-1.1.6
http://search.cpan.org/~sschneid/BigIP-ParseConfig-1.1.6/
F5/BigIP configuration parser
----
CGI-Application-PhotoGallery-0.12
http://search.cpan.org/~bricas/CGI-Application-PhotoGallery-0.12/
module to provide a simple photo gallery
----
CGI-Application-PhotoGallery-0.13
http://search.cpan.org/~bricas/CGI-Application-PhotoGallery-0.13/
module to provide a simple photo gallery
----
CPAN-Reporter-1.12
http://search.cpan.org/~dagolden/CPAN-Reporter-1.12/
Adds CPAN Testers reporting to CPAN.pm
----
CPAN-Reporter-Smoker-0.07
http://search.cpan.org/~dagolden/CPAN-Reporter-Smoker-0.07/
Turnkey CPAN Testers smoking
----
DB2-Admin-2.9
http://search.cpan.org/~hbiersma/DB2-Admin-2.9/
Support for DB2 Administrative API from perl
----
Data-FeatureFactory-0.04-r3
http://search.cpan.org/~sixtease/Data-FeatureFactory-0.04-r3/
evaluate features normally or numerically
----
Data-ResultSet-1.001
http://search.cpan.org/~doneill/Data-ResultSet-1.001/
Container for aggregating and examining multiple results
----
Devel-NYTProf-0.06
http://search.cpan.org/~akaplan/Devel-NYTProf-0.06/
line-by-line code profiler and report generator
----
Devel-NYTProf-0.07
http://search.cpan.org/~akaplan/Devel-NYTProf-0.07/
line-by-line code profiler and report generator
----
Devel-NYTProf-0.08
http://search.cpan.org/~akaplan/Devel-NYTProf-0.08/
line-by-line code profiler and report generator
----
Gaim-Log-Mailer-0.02
http://search.cpan.org/~mschilli/Gaim-Log-Mailer-0.02/
Have your Gaim/Pidgin logs mailed to you
----
Games-Go-Sgf2Dg-4.216
http://search.cpan.org/~reid/Games-Go-Sgf2Dg-4.216/
----
Games-Go-Sgf2Dg-4.220
http://search.cpan.org/~reid/Games-Go-Sgf2Dg-4.220/
----
Glib-1.180
http://search.cpan.org/~tsch/Glib-1.180/
Perl wrappers for the GLib utility and Object libraries
----
Gtk2-1.180
http://search.cpan.org/~tsch/Gtk2-1.180/
Perl interface to the 2.x series of the Gimp Toolkit library
----
Gtk2-Ex-Geo-0.56
http://search.cpan.org/~ajolma/Gtk2-Ex-Geo-0.56/
The main module to use for geospatial applications
----
Gtk2-Ex-Geo-0.57
http://search.cpan.org/~ajolma/Gtk2-Ex-Geo-0.57/
The main module to use for geospatial applications
----
HTML-TagCloud-Sortable-0.03
http://search.cpan.org/~bricas/HTML-TagCloud-Sortable-0.03/
A sortable HTML tag cloud
----
HTML-Template-Compiled-Plugin-LineBreak-0.02
http://search.cpan.org/~hagy/HTML-Template-Compiled-Plugin-LineBreak-0.02/
HTC Plugin to replaces any newlines with <br> HTML tags.
----
IO-Socket-SSL-1.13_5
http://search.cpan.org/~sullr/IO-Socket-SSL-1.13_5/
Nearly transparent SSL encapsulation for IO::Socket::INET.
----
IPC-MorseSignals-0.13
http://search.cpan.org/~vpit/IPC-MorseSignals-0.13/
Communicate between processes with Morse signals.
----
JS-0.12
http://search.cpan.org/~ingy/JS-0.12/
JavaScript Modules on CPAN
----
JS-jQuery-1.2.3.001
http://search.cpan.org/~ingy/JS-jQuery-1.2.3.001/
----
Lingua-Stem-Es-0.03
http://search.cpan.org/~jfraire/Lingua-Stem-Es-0.03/
Perl Spanish Stemming
----
Lingua-Translit-0.05
http://search.cpan.org/~alinke/Lingua-Translit-0.05/
transliterates text between writing systems
----
Linux-SysInfo-0.10
http://search.cpan.org/~vpit/Linux-SysInfo-0.10/
Perl interface to the sysinfo(2) Linux system call.
----
Makefile-DOM-0.003
http://search.cpan.org/~agent/Makefile-DOM-0.003/
Simple DOM parser for Makefiles
----
Makefile-DOM-0.004
http://search.cpan.org/~agent/Makefile-DOM-0.004/
Simple DOM parser for Makefiles
----
Makefile-Parser-0.205
http://search.cpan.org/~agent/Makefile-Parser-0.205/
A simple parser for Makefiles
----
Makefile-Parser-0.206
http://search.cpan.org/~agent/Makefile-Parser-0.206/
A simple parser for Makefiles
----
Makefile-Parser-0.207
http://search.cpan.org/~agent/Makefile-Parser-0.207/
A simple parser for Makefiles
----
Makefile-Parser-0.208
http://search.cpan.org/~agent/Makefile-Parser-0.208/
A simple parser for Makefiles
----
Muldis-DB-0.6.1
http://search.cpan.org/~duncand/Muldis-DB-0.6.1/
Full-featured truly relational DBMS in Perl
----
Net-IMAP-Server-0.2
http://search.cpan.org/~alexmv/Net-IMAP-Server-0.2/
A single-threaded multiplexing IMAP server implementation, using Net::Server::Coro.
----
Net-Server-Coro-0.2
http://search.cpan.org/~alexmv/Net-Server-Coro-0.2/
A co-operative multithreaded server using Coro
----
OAuth-Lite-1.08
http://search.cpan.org/~lyokato/OAuth-Lite-1.08/
OAuth framework
----
Object-InsideOut-3.39
http://search.cpan.org/~jdhedden/Object-InsideOut-3.39/
Comprehensive inside-out object support module
----
Osgood-Client-1.0.7
http://search.cpan.org/~gphat/Osgood-Client-1.0.7/
Client for the Osgood Passive, Persistent Event Queue
----
Osgood-Server-1.0.5
http://search.cpan.org/~gphat/Osgood-Server-1.0.5/
Catalyst based application
----
Osgood-Server-1.0.6
http://search.cpan.org/~gphat/Osgood-Server-1.0.6/
Catalyst based application
----
POE-Component-CPAN-YACSmoke-1.20
http://search.cpan.org/~bingos/POE-Component-CPAN-YACSmoke-1.20/
Bringing the power of POE to CPAN smoke testing.
----
POE-Component-Client-opentick-0.03
http://search.cpan.org/~infidel/POE-Component-Client-opentick-0.03/
A POE component for working with opentick.com's market data feeds.
----
POE-Component-Client-opentick-0.04
http://search.cpan.org/~infidel/POE-Component-Client-opentick-0.04/
A POE component for working with opentick.com's market data feeds.
----
POE-Component-IRC-Plugin-BasePoCoWrap-0.002
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-BasePoCoWrap-0.002/
base talking/ban/trigger functionality for plugins using POE::Component::*
----
POE-Component-IRC-Plugin-BaseWrap-0.001
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-BaseWrap-0.001/
base class for IRC plugins which need triggers/ban/root control
----
POE-Component-IRC-Plugin-BrowserSupport-0.002
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-BrowserSupport-0.002/
lookup browser support for CSS/HTML/JS from IRC
----
POE-Component-IRC-Plugin-Unicode-UCD-0.001
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-Unicode-UCD-0.001/
lookup unicode chars/codes from IRC
----
POE-Component-IRC-Plugin-Validator-HTML-0.002
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-Validator-HTML-0.002/
access HTML validator from IRC
----
Parallel-SubFork-0.02
http://search.cpan.org/~potyl/Parallel-SubFork-0.02/
Manage Perl functions in forked processes.
----
RDF-Server-0.02
http://search.cpan.org/~jsmith/RDF-Server-0.02/
toolkit for building RDF servers
----
RDF-Trine-0.103
http://search.cpan.org/~gwilliams/RDF-Trine-0.103/
An RDF Framework for Perl.
----
Run-Env-0.01_01
http://search.cpan.org/~jkutej/Run-Env-0.01_01/
running environment detection
----
SNMP-Query-Asynch-v0.1_21
http://search.cpan.org/~sscaffidi/SNMP-Query-Asynch-v0.1_21/
Fast asynchronous execution of batches of SNMP queries
----
SVN-S4-1.030
http://search.cpan.org/~wsnyder/SVN-S4-1.030/
Wrapper for Subversion
----
Template-Plugin-StripScripts-0.02
http://search.cpan.org/~kentaro/Template-Plugin-StripScripts-0.02/
TT plugin to filter HTML against XSS
----
Term-Title-0.01
http://search.cpan.org/~dagolden/Term-Title-0.01/
Portable API to set the terminal titlebar
----
Text-Template-Simple-0.51_3
http://search.cpan.org/~burak/Text-Template-Simple-0.51_3/
Simple text template engine
----
Text-TermExtract-0.02
http://search.cpan.org/~mschilli/Text-TermExtract-0.02/
Extract terms from text
----
Tk-PerlMethodList-0.07
http://search.cpan.org/~lamprecht/Tk-PerlMethodList-0.07/
query the Symbol-table for methods (subroutines) defined in a class (package) and its parents.
----
WWW-PhpfiCom-Retrieve-0.002
http://search.cpan.org/~zoffix/WWW-PhpfiCom-Retrieve-0.002/
retrieve pastes from http://phpfi.com
----
perfSONAR_PS-Base-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Base-0.08/
----
perfSONAR_PS-Client-Echo-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-Echo-0.08/
A module that provides methods for interacting with perfSONAR Echo services.
----
perfSONAR_PS-Client-LS-Remote-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-LS-Remote-0.08/
A module that provides a client API for an LS
----
perfSONAR_PS-Client-Status-MA-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-Status-MA-0.08/
A module that provides methods for interacting with Status MA servers.
----
perfSONAR_PS-Client-Status-SQL-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-Status-SQL-0.08/
A module that provides methods for interacting with a Status MA database directly.
----
perfSONAR_PS-Client-Topology-MA-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-Topology-MA-0.08/
A module that provides methods for interacting with Topology MA servers.
----
perfSONAR_PS-Client-Topology-XMLDB-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Client-Topology-XMLDB-0.08/
A module that provides methods for interacting with a Topology MA database directly.
----
perfSONAR_PS-Collectors-Daemon-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Collectors-Daemon-0.08/
----
perfSONAR_PS-Collectors-LinkStatus-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Collectors-LinkStatus-0.08/
A module that will collect link status information and store the results into a Link Status MA.
----
perfSONAR_PS-DB-File-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-DB-File-0.08/
A module that provides methods for adding 'database like' functions to files that contain XML markup.
----
perfSONAR_PS-DB-RRD-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-DB-RRD-0.08/
A module that provides a simple API for dealing with data stored in rrd files through the RRDTool's RRDp perl module.
----
perfSONAR_PS-DB-SQL-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-DB-SQL-0.08/
A module that provides methods for dealing with common SQL databases.
----
perfSONAR_PS-DB-XMLDB-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-DB-XMLDB-0.08/
A module that provides methods for dealing with the Sleepycat [Oracle] XML database.
----
perfSONAR_PS-Services-Daemon-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-Daemon-0.08/
----
perfSONAR_PS-Services-LS-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-LS-0.08/
This is a stub module to make it easier for installing the Lookup Service. This allows them install "perfSONAR_PS::Services::LS" instead of having to install "perfSONAR_PS::Services::LS::LS"
----
perfSONAR_PS-Services-MA-Base-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-MA-Base-0.08/
----
perfSONAR_PS-Services-MA-SNMP-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-MA-SNMP-0.08/
A module that provides methods for the perfSONAR-PS SNMP based Measurement Archive (MA).
----
perfSONAR_PS-Services-MA-Status-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-MA-Status-0.08/
A module that provides methods for a an L2 Status Measurement Archive. The service can be used to make Link Status Data available to individuals via webservice interface.
----
perfSONAR_PS-Services-MA-Topology-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-MA-Topology-0.08/
A module that provides methods for a Topology Service. The Topology Service can be used to make Topology Data available to individuals via webservice interface.
----
perfSONAR_PS-Services-MA-perfSONARBOUY-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Services-MA-perfSONARBOUY-0.08/
A module that provides methods for the perfSONARBOUY MA. perfSONARBOUY exposes data formerly collected by the AMI framework, including BWCTL and OWAMP data. This data is stored in a database backend (
----
perfSONAR_PS-Status-Common-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Status-Common-0.08/
A module that provides common methods for Link Status clients and services within the perfSONAR-PS framework.
----
perfSONAR_PS-Topology-Common-0.08
http://search.cpan.org/~perfsonar/perfSONAR_PS-Topology-Common-0.08/
A module that provides various utility functions for Topology structures.
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: Tue, 11 Mar 2008 07:14:49 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <JjqBj.22690$R84.20331@newssvr25.news.prodigy.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.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, 10 Mar 2008 21:45:42 -0700 (PDT)
From: kath <nitte.sudhir@gmail.com>
Subject: Re: Regex newbie
Message-Id: <e50a8a9a-31a1-4b29-81ab-e3d1457d5396@e25g2000prg.googlegroups.com>
On Mar 11, 8:30 am, gazza67 <garyho...@gmail.com> wrote:
> Anybody,
>
> I want to use a regex in which the string for which we are searching
> is a variable. Is this possible - it doesnt seem to work for me.
>
> $a = "be";
>
> $b="to be or not to be";
> if ($b =~ m/$a/i )
> print "this should be true";
>
> $b = "apples and oranges";
> if ($b =~ m/$a/i )
> print "this should be false";
>
> Cheers
> Gary
Either you have to use post condition or have to close block after if
statement with brackets
print "this should be true" if ($b =~ /$a/i);
or
if ($b =~ /$a/i){
print "this should be true";
}
sudhir.
------------------------------
Date: Tue, 11 Mar 2008 09:14:00 +0100
From: Peter Ludikovsky <darthludi@gmail.com>
Subject: Re: Regex newbie
Message-Id: <1205223274.302176@nntpcache01.si.eunet.at>
gazza67 wrote:
> Anybody,
>
> I want to use a regex in which the string for which we are searching
> is a variable. Is this possible - it doesnt seem to work for me.
>
> $a = "be";
>
> $b="to be or not to be";
> if ($b =~ m/$a/i )
> print "this should be true";
>
> $b = "apples and oranges";
> if ($b =~ m/$a/i )
> print "this should be false";
>
>
>
> Cheers
> Gary
1) Don't use $a & $b. Quote from 'perldoc perlvar':
Special package variables when using sort(), see "sort" in
perlfunc. Because of this specialness $a and $b don't need to
be declared (using use vars, or our()) even when using the
"strict 'vars'" pragma. Don't lexicalize them with "my $a" or
"my $b" if you want to be able to use them in the sort() comâ€
parison block or function.
2) You can make a better distinction between matching text and matching
variables by enclosing your variables in curly brackets, eg:
$string =~ /${test}/;
HTH
/peter
------------------------------
Date: Mon, 10 Mar 2008 21:41:05 -0700 (PDT)
From: jh3an <jh3ang@gmail.com>
Subject: Re: regular expression with split goes wrong ?
Message-Id: <f72d31a1-ca12-4de0-8f51-1283a8101c1a@n36g2000hse.googlegroups.com>
Thank you everyone !
------------------------------
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 1353
***************************************
