[30927] in Perl-Users-Digest
Perl-Users Digest, Issue: 2172 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 30 06:09:45 2009
Date: Fri, 30 Jan 2009 03:09:09 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 30 Jan 2009 Volume: 11 Number: 2172
Today's topics:
Re: CGI.pm and Use of uninitialized value in pattern ma <bart.lateur@pandora.be>
Re: How to remove a module from CPAN? <bart.lateur@pandora.be>
new CPAN modules on Fri Jan 30 2009 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Regex for <option> ... </option> <whynot@pozharski.name>
Regex for standard and specification (was: Regex for <o <whynot@pozharski.name>
Text Print Entire Directory Tree including File Names f <fiazidris@gmail.com>
Re: There is no such thing as Circular Lists (was: FAQ <bart.lateur@pandora.be>
Re: unix - rsync - filter question <tadmc@seesig.invalid>
Re: Vista x64 + DBD::Pg driver <psynowiec@WYTNIJTOop.pl>
Re: Vista x64 + DBD::Pg driver <psynowiec@WYTNIJTOop.pl>
Re: Want to write a script to do the batch conversion f <RedGrittyBrick@spamweary.invalid>
Re: Want to write a script to do the batch conversion f <someone@example.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 30 Jan 2009 10:04:25 +0100
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: CGI.pm and Use of uninitialized value in pattern match
Message-Id: <khg5o4dca6jdh0sp3v7vavlusadjf8385l@4ax.com>
A. Farber wrote:
>> You don't even _allow_ punctuation characters in passwords?
>>
>> Good security generally *requires* punctuation characters in passwords.
>
>your previous comment about anchors etc. has been good, thanks.
>
>No, I don't want punctuation :-) Here in Germany
>the keyboard layout is different from the english.
And in Belgium, keyboard layout is different for some letters, from the
German keyboard layout.
Perhaps you should disallow use of [aqzwm] too.
What kind of argument is that.
--
Bart.
------------------------------
Date: Fri, 30 Jan 2009 09:56:33 +0100
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: How to remove a module from CPAN?
Message-Id: <v4g5o45mqea3j9d9u1u8k4bmmginl0aj1n@4ax.com>
sln@netherlands.com wrote:
>Whoah, from CPAN itself, public domain. I often (well sometimes) wonder how
>do I remove 'sln' from newsgroups, so to keep anonymininindtmy when I apply
>for secret security clearences with the Federal gubbment (CIA) and all.
>
>I guess your fucked !!!
>hahahahahahaaaaaaaaaaaaaaaaaaaaaaaa
>
>sln
What a stupid little troll you are.
You know, you're not going to get laid this way.
--
Bart.
------------------------------
Date: Fri, 30 Jan 2009 05:42:26 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Jan 30 2009
Message-Id: <KE9ruq.IyM@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.
Apache2-ASP-2.16
http://search.cpan.org/~johnd/Apache2-ASP-2.16/
ASP for Perl, reloaded.
----
Apache2-ASP-2.17
http://search.cpan.org/~johnd/Apache2-ASP-2.17/
ASP for Perl, reloaded.
----
App-Sequence-0.0201
http://search.cpan.org/~kimoto/App-Sequence-0.0201/
pluggable subroutine engine.
----
Audio-Ecasound-Multitrack-0.9951
http://search.cpan.org/~ganglion/Audio-Ecasound-Multitrack-0.9951/
Perl extensions for multitrack audio processing
----
Audio-Extract-PCM-0.04_59
http://search.cpan.org/~pepe/Audio-Extract-PCM-0.04_59/
Extract PCM data from audio files
----
Big5Plus-0.31
http://search.cpan.org/~ina/Big5Plus-0.31/
"Yet Another JPerl" Source code filter to escape Big5Plus
----
Binding-0.04
http://search.cpan.org/~gugod/Binding-0.04/
eval with variable binding of caller stacks.
----
CPAN-Testers-Data-Generator-0.35
http://search.cpan.org/~barbie/CPAN-Testers-Data-Generator-0.35/
Download and summarize CPAN Testers data
----
CPAN-Testers-WWW-Reports-Mailer-0.14
http://search.cpan.org/~barbie/CPAN-Testers-WWW-Reports-Mailer-0.14/
CPAN Testers Reports Mailer
----
Catalyst-Runtime-5.8000_05
http://search.cpan.org/~mramberg/Catalyst-Runtime-5.8000_05/
The Catalyst Framework Runtime
----
Config-IniRegEx-0.01
http://search.cpan.org/~sasikala/Config-IniRegEx-0.01/
Ini workaround, regex search for parameters and sections.
----
Config-Model-OpenSsh-1.201
http://search.cpan.org/~ddumont/Config-Model-OpenSsh-1.201/
OpenSsh configuration files editor
----
Data-ChipsChallenge-0.01
http://search.cpan.org/~kirsle/Data-ChipsChallenge-0.01/
Perl interface to Chip's Challenge data files.
----
Data-Dumper-Perltidy-0.01
http://search.cpan.org/~jmcnamara/Data-Dumper-Perltidy-0.01/
Stringify and pretty print Perl data structures.
----
Data-Rx-0.005
http://search.cpan.org/~rjbs/Data-Rx-0.005/
perl implementation of Rx schema system
----
Data-Rx-TypeBundle-Perl-0.002
http://search.cpan.org/~rjbs/Data-Rx-TypeBundle-Perl-0.002/
experimental / perl types
----
Dotiac-addon-jsonify-0.1
http://search.cpan.org/~maluku/Dotiac-addon-jsonify-0.1/
----
Email-MIME-Kit-Renderer-TT-0.001
http://search.cpan.org/~rjbs/Email-MIME-Kit-Renderer-TT-0.001/
render parts of your mail with Template-Toolkit
----
Email-MIME-Kit-Validator-Rx-0.001
http://search.cpan.org/~rjbs/Email-MIME-Kit-Validator-Rx-0.001/
validate assembly stash with Rx (from JSON in kit)
----
Filesys-Virtual-Async-Plain-0.01
http://search.cpan.org/~xantus/Filesys-Virtual-Async-Plain-0.01/
A plain non-blocking virtual filesystem
----
Finance-Bank-IE-PermanentTSB-0.1
http://search.cpan.org/~pallotron/Finance-Bank-IE-PermanentTSB-0.1/
Perl Interface to the PermanentTSB Open24 homebanking on <http://www.open24.ie>
----
GBK-0.31
http://search.cpan.org/~ina/GBK-0.31/
"Yet Another JPerl" Source code filter to escape GBK
----
GBrowse-1.988
http://search.cpan.org/~lds/GBrowse-1.988/
----
Games-Framework-RCP-0.02_01
http://search.cpan.org/~wolfman/Games-Framework-RCP-0.02_01/
Generic video game tactics based battle system.
----
Geo-EOP-0.13
http://search.cpan.org/~markov/Geo-EOP-0.13/
Earth Observation Products EOP
----
Geo-Format-Landsat-0.03
http://search.cpan.org/~markov/Geo-Format-Landsat-0.03/
----
Google-Chart-0.05013
http://search.cpan.org/~dmaki/Google-Chart-0.05013/
Interface to Google Charts API
----
Gtk2-Ex-TickerView-12
http://search.cpan.org/~kryde/Gtk2-Ex-TickerView-12/
scrolling ticker display widget
----
HTML-CTPP2-2.4.2
http://search.cpan.org/~stellar/HTML-CTPP2-2.4.2/
Perl interface for CTPP2 library
----
HTML-FormHandler-0.10
http://search.cpan.org/~gshank/HTML-FormHandler-0.10/
form handler written in Moose
----
Hessian-Client-0.1.1
http://search.cpan.org/~heytrav/Hessian-Client-0.1.1/
RPC via Hessian with a remote server.
----
Hessian-Client-0.1.2
http://search.cpan.org/~heytrav/Hessian-Client-0.1.2/
RPC via Hessian with a remote server.
----
Hessian-Client-0.1.3
http://search.cpan.org/~heytrav/Hessian-Client-0.1.3/
RPC via Hessian with a remote server.
----
IO-Lambda-1.06
http://search.cpan.org/~karasik/IO-Lambda-1.06/
non-blocking I/O as lambda calculus
----
MFor-0.03
http://search.cpan.org/~cornelius/MFor-0.03/
A module for multi-dimension looping.
----
Net-Autoconfig-v1.12.2
http://search.cpan.org/~kevin/Net-Autoconfig-v1.12.2/
Perl extension for provisioning or reconfiguring network devices.
----
Net-CIDR-Set-0.10
http://search.cpan.org/~andya/Net-CIDR-Set-0.10/
Manipulate sets of IP addresses
----
Net-CIDR-Set-0.11
http://search.cpan.org/~andya/Net-CIDR-Set-0.11/
Manipulate sets of IP addresses
----
OpenGL-Earth-0.04
http://search.cpan.org/~cosimo/OpenGL-Earth-0.04/
----
POE-Component-SmokeBox-Recent-1.08
http://search.cpan.org/~bingos/POE-Component-SmokeBox-Recent-1.08/
A POE component to retrieve recent CPAN uploads.
----
POE-Filter-HTTP-Parser-0.08
http://search.cpan.org/~bingos/POE-Filter-HTTP-Parser-0.08/
A HTTP POE filter for HTTP clients or servers
----
Parse-ISF-0.0103
http://search.cpan.org/~razor/Parse-ISF-0.0103/
Parse the ISF file generated by certain models of Tektronix oscillascope (TDS 3000, DPO 4000, etc)
----
Parse-Tektronix-ISF-0.0103
http://search.cpan.org/~razor/Parse-Tektronix-ISF-0.0103/
Parse the ISF file generated by certain models of Tektronix oscillascope (TDS 3000, DPO 4000, etc)
----
Perl-Dist-1.12
http://search.cpan.org/~adamk/Perl-Dist-1.12/
Perl Distribution Creation Toolkit
----
Perl-Dist-Strawberry-1.09
http://search.cpan.org/~adamk/Perl-Dist-Strawberry-1.09/
Strawberry Perl for win32
----
RMI-0.05
http://search.cpan.org/~sakoht/RMI-0.05/
Remote Method Invocation with transparent proxies
----
SMS-Send-UK-Kapow-0.05
http://search.cpan.org/~jjones/SMS-Send-UK-Kapow-0.05/
SMS::Send driver for the Kapow.co.uk website
----
Sjis-0.31
http://search.cpan.org/~ina/Sjis-0.31/
"Yet Another JPerl" Source code filter to escape ShiftJIS
----
Sphinx-Search-0.13_01
http://search.cpan.org/~jjschutz/Sphinx-Search-0.13_01/
Sphinx search engine API Perl client
----
Sys-Sendfile-0.06
http://search.cpan.org/~leont/Sys-Sendfile-0.06/
Zero-copy data transfer
----
Test-Weaken-1.002000
http://search.cpan.org/~jkegl/Test-Weaken-1.002000/
Test that freed references are, indeed, freed
----
UHC-0.31
http://search.cpan.org/~ina/UHC-0.31/
"Yet Another JPerl" Source code filter to escape UHC
----
Vim-Snippet-Converter-0.05
http://search.cpan.org/~cornelius/Vim-Snippet-Converter-0.05/
A Template Converter for Slippery Snippet Vim Plugin
----
Vitacilina-0.1
http://search.cpan.org/~damog/Vitacilina-0.1/
?Ah, qu? buena medicina!
----
WWW-Gazetteer-HeavensAbove-0.18
http://search.cpan.org/~book/WWW-Gazetteer-HeavensAbove-0.18/
Find location of world towns and cities
----
WWW-Mixi-Scraper-0.23
http://search.cpan.org/~ishigaki/WWW-Mixi-Scraper-0.23/
yet another mixi scraper
----
WWW-Myspace-0.92
http://search.cpan.org/~stevenc/WWW-Myspace-0.92/
Access MySpace.com profile information from Perl
----
XML-Encoding-2.07
http://search.cpan.org/~shay/XML-Encoding-2.07/
A perl module for parsing XML encoding maps.
----
XML-FeedLite-1.009
http://search.cpan.org/~rpettett/XML-FeedLite-1.009/
Perl extension for fetching Atom and RSS feeds with minimal outlay
----
XML-Parser-Style-EasyTree-0.01
http://search.cpan.org/~mons/XML-Parser-Style-EasyTree-0.01/
Parse xml to simple tree
----
XML-RPC-Fast-0.2
http://search.cpan.org/~mons/XML-RPC-Fast-0.2/
Faster implementation for an XML-RPC client and server (based on XML::RPC)
----
XML-Toolkit-0.05
http://search.cpan.org/~perigrin/XML-Toolkit-0.05/
A set of tools for dealing with XML with the Way of the Moose.
----
jpgresize-0.3-beta
http://search.cpan.org/~fgoslich/jpgresize-0.3-beta/
----
minismokebox-0.08
http://search.cpan.org/~bingos/minismokebox-0.08/
a small lightweight SmokeBox
----
persona-0.07
http://search.cpan.org/~elizabeth/persona-0.07/
control which code will be loaded for an execution context
----
persona-0.08
http://search.cpan.org/~elizabeth/persona-0.08/
control which code will be loaded for an execution context
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: Fri, 30 Jan 2009 08:14:34 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <KFygl.2492$PE4.1719@nlpi061.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: Fri, 30 Jan 2009 01:04:09 +0200
From: Eric Pozharski <whynot@pozharski.name>
Subject: Re: Regex for <option> ... </option>
Message-Id: <slrngo4df9.d0s.whynot@orphan.zombinet>
On 2009-01-29, Eric Pozharski <whynot@pozharski.name> wrote:
> On 2009-01-29, Tad J McClellan <tadmc@seesig.invalid> wrote:
>> sln@netherlands.com <sln@netherlands.com> wrote:
>>
>>> XHTML/XML/SGML and HTML standards are now and have been for quite some time
>>> defined with REGULAR ESPRESSIONS exclusively.
>>
>>
>> No they haven't.
>>
>> They are defined with a context free grammar, not a regular grammar.
>
> And they aren't standards anyway. Those are specifications.
I'm wrong, again (lack of curiosity issue). Just checked -- SGML is the
only standard, any else (among mentioned) are specifications.
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Fri, 30 Jan 2009 00:47:02 +0200
From: Eric Pozharski <whynot@pozharski.name>
Subject: Regex for standard and specification (was: Regex for <option> ... </option>)
Message-Id: <slrngo4cf7.d0s.whynot@orphan.zombinet>
On 2009-01-29, Tim McDaniel <tmcd@panix.com> wrote:
> In article <slrngo2qbe.6fu.whynot@orphan.zombinet>,
> Eric Pozharski <whynot@pozharski.name> wrote:
>>On 2009-01-29, Tad J McClellan <tadmc@seesig.invalid> wrote:
>>> sln@netherlands.com <sln@netherlands.com> wrote:
>>>
>>>> XHTML/XML/SGML and HTML standards are now and have been for quite
>>>> some time defined with REGULAR ESPRESSIONS exclusively.
>>>
>>> No they haven't.
>>>
>>> They are defined with a context free grammar, not a regular
>>> grammar.
>>
>>And they aren't standards anyway. Those are specifications.
>
> What criteria distinguish a standard from a specification?
> (That's not an accusation or implying that you're wrong;
> I'm interested in definitions.)
I'm noway wrong, I've checked -- all of them XHTML, XML, SGML, and HTML
"papers" call itself "Specification". That can be a template issue
though.
Anyway, that's what I have on hands. I've asked WordNet dictionary:
standard
n 1: a basis for comparison; a reference point against which
other things can be evaluated; "they set the measure for
all subsequent work" [syn: {criterion}, {measure},
{touchstone}]
specification
n 1: a detailed description of design criteria for a piece of
work [syn: {spec}]
After reading about these (there're some more, missing in copy-paste) my
sole understanding of difference is: "standard" is a "paper" that
pictures what status quo is, while "specification" is a "paper" about
subject missing in present. Me lacks historic vision of some issues
obviously.
p.s. In misguided attempt to mess everything up again: criminal law is
a standard, while Ten Ammendments are spec.
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Fri, 30 Jan 2009 03:04:24 -0800 (PST)
From: ifiaz <fiazidris@gmail.com>
Subject: Text Print Entire Directory Tree including File Names from a FTP Directory
Message-Id: <707ced5c-5f50-4470-83ae-ef8915e3a7c4@y23g2000pre.googlegroups.com>
Hello,
I am looking for a way to get the ENTIRE (or at a given depth)
directory tree of a FTP folder and files from an FTP server. The
listing should include file sizes and modified dates, etc. as much
info as possible through some configurable parameters. The same script
may be able to be used on a local drive as well.
I have managed to do this FTP directory task using the
http://www.ftprush.com/ftp-directory-tree.html application. This
application is pretty cool and it did exactly what I wanted.
**********
My question is how can I do this using a Perl Script or any other free
utility from command line.???
**********
I am sure someone out there who must have written such stuff already.
I do not wish to reinvent the wheel and even I am not capable to write
such a script myself.
Any pointers and help is much appreciated. Thank you.
The ftprush program listed something like this (which is SO...
COOL...).
/New Folder/ [345.4 M]
|-Annexures [67.7 M]
| >|-Annexure A2- bbbb Group ppt [2.0 M]
| >| >|-Presentation on Group.ppt (2.0 M)
| >|
| >|-Annexure B1- Copy of Annual Accounts bbb-vii [39.2 M]
| >| >|-vii05s-us.pdf (10.7 M)
| >| >|-vii-rapport-annuel-2006-en (2).pdf (27.8 M)
| >| >|-bbbHSA audited financials 2006.pdf (659.5 k)
| >|
| >|-Annexure C - Quality Manual and safety [540.5 k]
| >| >|-Attachement A - bbb Quality Manual.doc (540.5 k)
| >|
| >|-Annexure C1- Safety and Security [221.5 k]
| >| >|-Attachement C - S&S Manual.doc (221.5 k)
| >|
| >|-Annexure D-Insurance Certificate [82.3 k]
| >| >|-Aviation Insurance -11-07.pdf (82.3 k)
...
...
------------------------------
Date: Fri, 30 Jan 2009 09:50:03 +0100
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: There is no such thing as Circular Lists (was: FAQ 4.47 How do I handle circular lists?)
Message-Id: <9lf5o456fhsm7p4tbh92952v60e67rguj4@4ax.com>
sln@netherlands.com wrote:
>>http://www.nist.gov/dads/HTML/circularlist.html
>
>Don't make me laff. Cite and give props, don't sugar-coat it.
>The quote is below. Its a great example of no such thing. A variant
>of "Linked-Lists" ???
>
>There is NO VARIANT of Linked Lists.
>There is NO SUCH ANIMAL, period, excalamation point !!!
>
>Every List has a head and a tail, a List cannot exist without them !!
Take an ordinary linked list. Of that, the chain link field in the last
item points nowhere.
Now take a pointer to the head of the list, and put it in that the link
field of your tail.
Whoops, suddenly, a circular liinked list *does* exist.
Should I patent it?
--
Bart.
------------------------------
Date: Thu, 29 Jan 2009 20:21:33 -0600
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: unix - rsync - filter question
Message-Id: <slrngo4p1d.ahn.tadmc@tadmc30.sbcglobal.net>
Jim Gibson <jimsgibson@gmail.com> wrote:
> In Unix, errors are usually printed to STDERR, which is unbuffered (or,
> for the pedantic among us, "autoflushed").
Errr, no, STDERR is unbuffered if we're to believe the man page.
> man 3 stderr
...
CONSIDERATIONS
The stream stderr is unbuffered.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 30 Jan 2009 10:42:52 +0100
From: mysiar <psynowiec@WYTNIJTOop.pl>
Subject: Re: Vista x64 + DBD::Pg driver
Message-Id: <glui2q$bjn$1@news.onet.pl>
Tim Greer wrote:
> mysiar wrote:
>
>> I install PG driver and my script didn't work.
>> I tried reinstall driver and still no luck so basically I gave up.
>> Yesterday after I read your post I wanted to run my scripts again with
>> Pg driver and it worked.
>> It was a big surprise for me.
>>
>> I do not shutdown my Vista just hibernate.
>
> Odd, perhaps it was just needing something to restart (a service, or
> whatever). Were you running this through a web server (Apache, IIS, or
> whatever), or from the command line? If a web service via CGI, that
> might make sense if it basically cycled the service after it started
> again. It's been many years since I've used Windows (Thank God), so I
> really don't want to guess further about why it would have suddenly
> started working without changes.
it was all command line
------------------------------
Date: Fri, 30 Jan 2009 10:43:16 +0100
From: mysiar <psynowiec@WYTNIJTOop.pl>
Subject: Re: Vista x64 + DBD::Pg driver
Message-Id: <glui3i$bjn$2@news.onet.pl>
Chris Mattern wrote:
> On 2009-01-27, mysiar <psynowiec@WYTNIJTOop.pl> wrote:
>> Tim Greer wrote:
>>> mysiar wrote:
>>>
>>>> Hi
>>>> does anybody have this driver working ?
>>>> If so could share "prescription" how to run it ?
>>>>
>>>> Regards
>>>> Piotr
>>> Are you having issues installing it, running it, or? If it's installed
>>> without errors, what relevant portions of code can you post and detail
>>> the issue (any errors, etc.)
>> Sorry false alarm.
>> After I reboot my laptop it works great before I had a problem with
>> msvcr80.dll
>> To be honest I do not have any idea what was wrong and why it is OK now.
>>
> Welcome to Windows.
>
thanks just starting after the years with Linux
------------------------------
Date: Fri, 30 Jan 2009 09:46:44 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: Want to write a script to do the batch conversion from domain name to IP.
Message-Id: <4982cc88$0$30298$da0feed9@news.zen.co.uk>
Hongyi Zhao wrote:
> Hi all,
>
> Suppose I've the entries like the following in my file:
>
> ------------------
> 116.52.155.237:80
> ip-72-55-191-6.static.privatedns.com:3128
> 222.124.135.40:80
> 217.151.231.34:3128
> 202.106.121.134:80
> 211.161.197.182:80
> hpc.be.itu.edu.tr:80
> static3-117-183.worldinternetworkcorporation.com:80
> ------------------
>
> Now, I want to convert the domain name to IP by using a perl script,
> any hints on this?
>
I'd use split /:/ to separate the address from the port number.
I'd use a regular expression to check if the address looks like an
ip-address. If your are confident of your data you can be a bit sloppy
and use something simple like m/^[0-9.]+$/ Otherwise read this
http://www.perlmonks.org/?node_id=221512
For addresses that look like a hostname+domain I'd use gethostbyname
--
RGB
------------------------------
Date: Fri, 30 Jan 2009 03:04:18 -0800
From: "John W. Krahn" <someone@example.com>
Subject: Re: Want to write a script to do the batch conversion from domain name to IP.
Message-Id: <S8Bgl.1583$_N1.1407@newsfe01.iad>
Hongyi Zhao wrote:
>
> Suppose I've the entries like the following in my file:
>
> ------------------
> 116.52.155.237:80
> ip-72-55-191-6.static.privatedns.com:3128
> 222.124.135.40:80
> 217.151.231.34:3128
> 202.106.121.134:80
> 211.161.197.182:80
> hpc.be.itu.edu.tr:80
> static3-117-183.worldinternetworkcorporation.com:80
> ------------------
>
> Now, I want to convert the domain name to IP by using a perl script,
> any hints on this?
$ echo "
116.52.155.237:80
ip-72-55-191-6.static.privatedns.com:3128
222.124.135.40:80
217.151.231.34:3128
202.106.121.134:80
211.161.197.182:80
hpc.be.itu.edu.tr:80
static3-117-183.worldinternetworkcorporation.com:80
" | perl -MSocket -lne'
my $address = ( split /:/ )[ 0 ] or next;
my $number = inet_aton $address;
my $ip = inet_ntoa $number;
print "$address -> $ip";
'
116.52.155.237 -> 116.52.155.237
ip-72-55-191-6.static.privatedns.com -> 72.55.191.6
222.124.135.40 -> 222.124.135.40
217.151.231.34 -> 217.151.231.34
202.106.121.134 -> 202.106.121.134
211.161.197.182 -> 211.161.197.182
hpc.be.itu.edu.tr -> 160.75.90.69
static3-117-183.worldinternetworkcorporation.com -> 203.145.117.183
John
--
Those people who think they know everything are a great
annoyance to those of us who do. -- Isaac Asimov
------------------------------
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 2172
***************************************
