[31165] in Perl-Users-Digest
Perl-Users Digest, Issue: 2410 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue May 12 06:09:42 2009
Date: Tue, 12 May 2009 03:09:06 -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, 12 May 2009 Volume: 11 Number: 2410
Today's topics:
Re: FAQ 6.15 How can I print out a word-frequency or li <tadmc@seesig.invalid>
Re: FAQ 6.15 How can I print out a word-frequency or li <tadmc@seesig.invalid>
Re: FAQ 6.15 How can I print out a word-frequency or li jidanni@jidanni.org
Re: FAQ 6.15 How can I print out a word-frequency or li <uri@stemsystems.com>
Re: FAQ 6.15 How can I print out a word-frequency or li <ben@morrow.me.uk>
new CPAN modules on Tue May 12 2009 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Print strings based on regular expression <yong321@yahoo.com>
writing get_script as an external routine callable by C <frank@example.invalid>
Re: writing get_script() <frank@example.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 11 May 2009 17:12:48 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: FAQ 6.15 How can I print out a word-frequency or line-frequency summary?
Message-Id: <slrnh0h8n0.qhd.tadmc@tadmc30.sbcglobal.net>
Nathan Keel <nat.k@gm.ml> wrote:
> jidanni@jidanni.org wrote:
>
>> I saved you 2 bytes!:
>> --- perlfaq6.ORIG.pod 2009-05-12 01:56:38.000000000 +0800
>> +++ perlfaq6.pod 2009-05-12 01:57:44.706933151 +0800
>> @@ -539,8 +539,8 @@
>> in the previous question:
>>
>> while (<>) {
>> - while ( /(\b[^\W_\d][\w'-]+\b)/g ) { # misses "`sheep'"
>> - $seen{$1}++;
>> + while ( /\b[^\W_\d][\w'-]+\b/g ) { # misses "`sheep'"
>> + $seen{$&}++;
>> }
>> }
>
> I wouldn't use $&
Why not?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 11 May 2009 17:12:24 -0500
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: FAQ 6.15 How can I print out a word-frequency or line-frequency summary?
Message-Id: <slrnh0h8m8.qhd.tadmc@tadmc30.sbcglobal.net>
Uri Guttman <uri@stemsystems.com> wrote:
> read up on why $& is bad
at
perldoc -q '\$&'
Why does using $&, $`, or $' slow my program down?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Tue, 12 May 2009 07:25:40 +0800
From: jidanni@jidanni.org
Subject: Re: FAQ 6.15 How can I print out a word-frequency or line-frequency summary?
Message-Id: <87zldji5mz.fsf@jidanni.org>
$ perldoc -q '\$&'|grep -B 1 expensive
... As of the 5.005 release, the $& variable is no longer
"expensive" the way the other two are.
Muhahaha.
However I did not time(1) the difference.
------------------------------
Date: Mon, 11 May 2009 19:48:31 -0400
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: FAQ 6.15 How can I print out a word-frequency or line-frequency summary?
Message-Id: <87ab5j6w1c.fsf@quad.sysarch.com>
>>>>> "j" == jidanni <jidanni@jidanni.org> writes:
j> $ perldoc -q '\$&'|grep -B 1 expensive
j> ... As of the 5.005 release, the $& variable is no longer
j> "expensive" the way the other two are.
j> Muhahaha.
j> However I did not time(1) the difference.
it is still poor coding as $& and friends are global vars. $1 is scoped
so you can't screw up things with action at a distance. also it is
better to explicitly grab something than to do it implicitly with
$&. still laughing? you really think saving 2 chars is worth all the
other pain?
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 12 May 2009 00:58:23 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: FAQ 6.15 How can I print out a word-frequency or line-frequency summary?
Message-Id: <vlqmd6-5j8.ln1@osiris.mauzo.dyndns.org>
Quoth jidanni@jidanni.org:
> $ perldoc -q '\$&'|grep -B 1 expensive
>
> ... As of the 5.005 release, the $& variable is no longer
> "expensive" the way the other two are.
>
> Muhahaha.
> However I did not time(1) the difference.
~% perldoc perlre | grep -C1 5.005
appreciate them), once you’ve used them once, use them at will,
because you’ve already paid the price. As of 5.005, $& is not so
costly as the other two.
$& still imposes *some* penalty on every match without captures, just
not as much as $` and $' do. I must admit I can't find (with a quick
look and no deep understanding of the regex engine) any difference
between the three.
Ben
------------------------------
Date: Tue, 12 May 2009 04:42:27 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue May 12 2009
Message-Id: <KJIL2r.1417@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.
CPANPLUS-Dist-Arch-0.08
http://search.cpan.org/~juster/CPANPLUS-Dist-Arch-0.08/
CPANPLUS backend for building Archlinux pacman packages
----
Catalyst-Devel-1.14_02
http://search.cpan.org/~flora/Catalyst-Devel-1.14_02/
Catalyst Development Tools
----
Catalyst-Plugin-ENV-0.02
http://search.cpan.org/~plcgi/Catalyst-Plugin-ENV-0.02/
getter for value from enviroment
----
Catalyst-Plugin-ErrorCatcher-0.0.2.2
http://search.cpan.org/~chisel/Catalyst-Plugin-ErrorCatcher-0.0.2.2/
Catch application errors and emit them somewhere
----
Catalyst-Plugin-ErrorCatcher-0.0.3
http://search.cpan.org/~chisel/Catalyst-Plugin-ErrorCatcher-0.0.3/
Catch application errors and emit them somewhere
----
Chart-Clicker-2.29
http://search.cpan.org/~gphat/Chart-Clicker-2.29/
Powerful, extensible charting.
----
Chart-Clicker-2.30
http://search.cpan.org/~gphat/Chart-Clicker-2.30/
Powerful, extensible charting.
----
Crypt-Twofish-2.13
http://search.cpan.org/~ams/Crypt-Twofish-2.13/
The Twofish Encryption Algorithm
----
DBIx-Class-ResultSet-Void-0.03
http://search.cpan.org/~fayland/DBIx-Class-ResultSet-Void-0.03/
improve DBIx::Class::ResultSet with void context
----
DBIx-Class-ResultSet-Void-0.04
http://search.cpan.org/~fayland/DBIx-Class-ResultSet-Void-0.04/
improve DBIx::Class::ResultSet with void context
----
DateTime-0.50
http://search.cpan.org/~drolsky/DateTime-0.50/
A date and time object
----
Dist-Zilla-Plugin-Repository-0.05
http://search.cpan.org/~fayland/Dist-Zilla-Plugin-Repository-0.05/
Automatically sets repository URL from svn/svk/Git checkout for Dist::Zilla
----
Dist-Zilla-Plugin-Repository-0.06
http://search.cpan.org/~fayland/Dist-Zilla-Plugin-Repository-0.06/
Automatically sets repository URL from svn/svk/Git checkout for Dist::Zilla
----
ELF-Extract-Sections-0.01.00
http://search.cpan.org/~kentnl/ELF-Extract-Sections-0.01.00/
Extract Raw Chunks of data from identifiable ELF Sections
----
Elive-0.16
http://search.cpan.org/~warringd/Elive-0.16/
Elluminate Live (c) client library
----
File-ChangeNotify-0.03
http://search.cpan.org/~drolsky/File-ChangeNotify-0.03/
Watch for changes to files, cross-platform style
----
File-Strmode-0.03
http://search.cpan.org/~salva/File-Strmode-0.03/
Converts a file mode into a symbolic string
----
Find-Lib-0.06
http://search.cpan.org/~yannk/Find-Lib-0.06/
Helper to smartly find libs to use in the filesystem tree
----
Geo-IPfree-0.6
http://search.cpan.org/~bricas/Geo-IPfree-0.6/
Look up country of IP Address. This module make this off-line and the DB of IPs is free & small.
----
HTML-FormWidgets-0.4.176
http://search.cpan.org/~pjfl/HTML-FormWidgets-0.4.176/
Create HTML form markup
----
IO-1.24
http://search.cpan.org/~gbarr/IO-1.24/
load various IO modules
----
Log-Deep-0.0.5
http://search.cpan.org/~ivanwills/Log-Deep-0.0.5/
Deep Logging of information about a script state
----
Log-Deep-0.0.6
http://search.cpan.org/~ivanwills/Log-Deep-0.0.6/
Deep Logging of information about a script state
----
MIME-Charset-1.007_01
http://search.cpan.org/~nezumi/MIME-Charset-1.007_01/
Charset Informations for MIME
----
MIME-EncWords-1.011_01
http://search.cpan.org/~nezumi/MIME-EncWords-1.011_01/
deal with RFC 2047 encoded words (improved)
----
MP3-Tag-1.11
http://search.cpan.org/~ilyaz/MP3-Tag-1.11/
Module for reading tags of MP3 audio files
----
Mail-Lite-0.1005
http://search.cpan.org/~davinchi/Mail-Lite-0.1005/
----
Math-VarRate-0.091310
http://search.cpan.org/~rjbs/Math-VarRate-0.091310/
deal with linear, variable rates of increase
----
Moose-Documenter-0.01
http://search.cpan.org/~dsbike/Moose-Documenter-0.01/
class for getting Moose documentation for your Moose classes
----
Net-Pachube-0.01
http://search.cpan.org/~beanz/Net-Pachube-0.01/
Perl extension for accessing pachube.com
----
Net-SFTP-Foreign-1.52_05
http://search.cpan.org/~salva/Net-SFTP-Foreign-1.52_05/
SSH File Transfer Protocol client
----
Net-SFTP-Foreign-1.52_06
http://search.cpan.org/~salva/Net-SFTP-Foreign-1.52_06/
SSH File Transfer Protocol client
----
Net-SFTP-Server-0.01
http://search.cpan.org/~salva/Net-SFTP-Server-0.01/
Base class for writting SFTP servers
----
POE-Filter-HTTP-Parser-1.00
http://search.cpan.org/~bingos/POE-Filter-HTTP-Parser-1.00/
A HTTP POE filter for HTTP clients or servers
----
Parallel-Depend-4.02
http://search.cpan.org/~lembark/Parallel-Depend-4.02/
: Parallel-dependent dispatch of perl or shell code.
----
Parse-Stallion-0.81
http://search.cpan.org/~arthur/Parse-Stallion-0.81/
EBNF based regexp backtracking parser and tree evaluator.
----
Passwd-Unix-0.51
http://search.cpan.org/~strzelec/Passwd-Unix-0.51/
----
Pod-Abstract-0.16
http://search.cpan.org/~blilburne/Pod-Abstract-0.16/
Abstract document tree for Perl POD documents
----
Religion-Bible-Regex-Builder-0.9.2
http://search.cpan.org/~holmlund/Religion-Bible-Regex-Builder-0.9.2/
builds regular expressions that match Bible References
----
Rose-DBx-Object-Renderer-0.48
http://search.cpan.org/~danny/Rose-DBx-Object-Renderer-0.48/
Web UI Rendering for Rose::DB::Object
----
SMS-Send-Wadja-0.01
http://search.cpan.org/~dandv/SMS-Send-Wadja-0.01/
Non-regional SMS::Send driver for the <http://wadja.com> free global SMS service, using their API.
----
SMS-Send-Wadja-0.02
http://search.cpan.org/~dandv/SMS-Send-Wadja-0.02/
Non-regional SMS::Send driver for the <http://wadja.com> free global SMS service, using their API.
----
SMS-Send-Wadja-0.03
http://search.cpan.org/~dandv/SMS-Send-Wadja-0.03/
Non-regional SMS::Send driver for the <http://wadja.com> free global SMS service, using their API.
----
Simo-0.1110
http://search.cpan.org/~kimoto/Simo-0.1110/
Very simple framework for Object Oriented Perl.
----
Syntax-Highlight-Perl6-0.55
http://search.cpan.org/~azawawi/Syntax-Highlight-Perl6-0.55/
Perl 6 Syntax Highlighter
----
Template-Plugin-LinkTo-0.08
http://search.cpan.org/~hirafoo/Template-Plugin-LinkTo-0.08/
like link_to in Ruby on Rails
----
Test-Able-0.07
http://search.cpan.org/~jdv/Test-Able-0.07/
xUnit with Moose
----
Test-Apache2-0.03
http://search.cpan.org/~kzys/Test-Apache2-0.03/
Simple test harness of mod_perl handler
----
Test-Command-0.05
http://search.cpan.org/~danboo/Test-Command-0.05/
Test routines for external commands
----
Test-Output-0.14
http://search.cpan.org/~jlholt/Test-Output-0.14/
Utilities to test STDOUT and STDERR messages.
----
TheSchwartz-Moosified-0.04
http://search.cpan.org/~stash/TheSchwartz-Moosified-0.04/
TheSchwartz based on Moose!
----
Wetware-CLI-0.06
http://search.cpan.org/~drieux/Wetware-CLI-0.06/
A base class wrapper on Getopt::Long::GetOptions()
----
Wetware-Test-0.07
http://search.cpan.org/~drieux/Wetware-Test-0.07/
Wetware Test::Class extensions
----
Wetware-Test-CreateTestSuite-0.03
http://search.cpan.org/~drieux/Wetware-Test-CreateTestSuite-0.03/
for creating TestSuite.pm
----
Win32-Process-Critical-v0.82
http://search.cpan.org/~rootkwok/Win32-Process-Critical-v0.82/
Prevent interupt by setting your program as critical progress
----
Win32-Process-Hide-v1.82
http://search.cpan.org/~rootkwok/Win32-Process-Hide-v1.82/
Perl extension for hiding your process.
----
Win32-Process-Kill-v2.2
http://search.cpan.org/~rootkwok/Win32-Process-Kill-v2.2/
Perl extension for Terminating Process in Win32 (R3)
----
Win32-Process-Suspend-v0.04
http://search.cpan.org/~rootkwok/Win32-Process-Suspend-v0.04/
Suspending Other Process With Perl
----
Win32-SysPrivilege-v1.42
http://search.cpan.org/~rootkwok/Win32-SysPrivilege-v1.42/
Perl extension for Running external programs with SYSTEM Privilege
----
XML-Amazon-0.11
http://search.cpan.org/~hedwig/XML-Amazon-0.11/
Perl extension for getting information from Amazon
----
Yoyo-0.00001_01
http://search.cpan.org/~yamakura/Yoyo-0.00001_01/
It is a tool that confirms the command result to various hosts connected with ssh.
----
makepatch-2.04
http://search.cpan.org/~jv/makepatch-2.04/
create script to update a source tree
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 12 May 2009 07:14:08 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <4l9Ol.10230$im1.3918@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.9 $)
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_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, 11 May 2009 14:56:37 -0700 (PDT)
From: Yong Huang <yong321@yahoo.com>
Subject: Re: Print strings based on regular expression
Message-Id: <8aa7e1cc-888b-4461-9e10-0a1a58a732b9@q2g2000vbr.googlegroups.com>
On Apr 20, 1:58 pm, Ted Zlatanov <t...@lifelogs.com> wrote:
> On Sun, 19 Apr 2009 11:36:35 -0700 (PDT) Yong Huang <yong...@yahoo.com> wrote:
>
> YH> Is there a program that prints all possible strings based on a regular
> YH> expression?
>
> YH> $ thisprogram '^\w\d$'
> YH> A0
> YH> A1
> YH> ...
> YH> z9
>
> YH> The output could easily be made infinite. That's fine. The point is to
> YH> let users visualize what the matching strings look like. I think this
> YH> program has great educational value in teaching regular expressions.
>
> See _Higher-Order Perl_ by Mark-Jason Dominus, chapter 6.5 (generating a
> list of all the strings matched by a regular expression). The whole
> book is terrific.
>
> It's available online for free but it's also one of the few Perl books I
> recommend purchasing without reservation.
>
> Ted
Thanks, Ted. After hours of testing the functions in that excellent
book, I searched CPAN one more time and found
http://search.cpan.org/~bowmanbs/Regexp-Genex-0.07/lib/Regexp/Genex.pm
It's much easier to use. But currently it doesn't output all possible
characters given character class or \w or \d (or I didn't get it to
work). Every time it picks one but different character to output.
Anyway, it's close to what I want.
Yong Huang
------------------------------
Date: Tue, 12 May 2009 00:34:02 -0700
From: Franken Sense <frank@example.invalid>
Subject: writing get_script as an external routine callable by C
Message-Id: <10p7dbdx06p63$.a51zjgxaz8ux.dlg@40tude.net>
With forum help, I've been able to do pretty good damage with using perl
for input. It's *so much* easier than my alternatives with compiled
languages that I really feel like I'm in touch with the virtue of laziness.
I'm simply too immature with perl to, say, populate a binary tree with the
data or do many of the things that I can do with compiled languages, once I
have the data where I want it. This is, I think, a nice final touch by
Mark Krahn:
#!/usr/bin/perl
# perl m13.pl
use warnings;
use strict;
# open input file
my $filename = 'text43.txt';
open(my $fh, '<', $filename) or
die "cannot open $filename for reading: $!";
# open output file
my $filename2 = 'outfile16.txt';
open(my $gh, '>', $filename2) or
die "cannot open $filename2 for writing: $!";
local $/="";
while ( <$fh> )
{
my ( $verse, @s ) = split;
my $script = join ' ', @s;
print $gh "$verse $script\n";
}
# close input and output files
close($gh) or die("Error closing $filename2: $!");
close($fh) or die("Error closing $filename: $!");
# abridged output:
44:004:002 Being grieved that they taught the people, and preached through
Jesus the resurrection from the dead.
44:004:003 And they laid hands on them, and put them in hold unto the next
day: for it was now eventide.
44:004:004 Howbeit many of them which heard the word believed; and the
number of the men was about five thousand.
44:004:005 And it came to pass on the morrow, that their rulers, and
elders, and scribes,
So now I want main to have to call a routine to get the next $verse and
$script.
@anything = get_script( $verse, \@s)
sub get_script
{
my ( $verse, @s ) = split;
my $script = join ' ', @s;
return something;
}
Not exactly beautiful code, but my first efforts rarely look nice. The
reference for this in the camel book is §6 : Passing References. p 224
Then there's the matter of calling a perl subroutine from C.
#include <EXTERN.h>
#include <perl.h>
static PerlInterpreter *my_perl;
int main(int argc, char **argv, char ** env)
{
char *args[] = {Null};
my_perl = perl_alloc();
perl_construct(my_perl);
perl_parse(my_perl, NULL, argc, argv, NULL);
call_argv("get_script", args);
perl_destruct(my_perl);
perl_free(my_perl);
return 0;
}
The reference here is §21 of the camel book, p. 540.
Does any of this look close?
--
Frank
Oh, What Doesn't Kill You Can Have Lingering Aftereffects!
~~ Al Franken,
------------------------------
Date: Mon, 11 May 2009 23:15:10 -0700
From: Franken Sense <frank@example.invalid>
Subject: Re: writing get_script()
Message-Id: <1sk65gbdr7282.159wn8akyfbqs.dlg@40tude.net>
In Dread Ink, the Grave Hand of Franken Sense Did Inscribe:
> In Dread Ink, the Grave Hand of Jürgen Exner Did Inscribe:
>
>>>> True. However there is no reason why not to build a binary tree in Perl.
>>>
>>>Is there a module for it?
>>
>> A quick search for 'Binary Tree" on CPAN returns several hundred
>> results, the very first on being "Tree::Binary" with many more
>> interesting modules on the same and the next page.
>
> I've got a new problem here. I've installed Tree::Binary using
> activestate's ppm. To test, I've run a script with the line
> use Tree::Binary;
> . I find no Binary.pm in the Tree folder where I would expect it:
>
> http://lomas-assault.net/usenet/z31.jpg
>
> I wouldn't know how to proceed.
I went to cpan and downloaded the tar.gz package for this, exracted them on
my desktop, and somehow I have .pm files where I had .html files (in the
site folder not on my desktop). I would have thought that I remembered
falsely what I was looking at before, but I saved it in a screenshot
yesterday: http://lomas-assault.net/usenet/z31.jpg
So it would appear that making the ppm install was half the soln and
extracting the tar.gz file was the second half.
The bad news is that this is very much beyond my ability with perl, and
finding examples has been fruitless. (For what would one google?)
It prettymuch all looks like this:
sub setRight {
my ($self, $tree) = @_;
(blessed($tree) && $tree->isa("Tree::Binary"))
|| die "Insufficient Arguments : right argument must be a Tree::Binary object";
$tree->{_parent} = $self;
$self->{_right} = $tree;
unless ($tree->isLeaf()) {
$tree->fixDepth();
}
else {
$tree->{_depth} = $self->getDepth() + 1;
}
$self;
}
There's nothing in the camel book on it, so I would rather take the
discretion part of valor as opposed to getting myself in too deep.
I think, instead, I'll try to shoe horn these data into a hash and see what
I can pull off.
--
Frank
No Child Left Behind is the most ironically named act, piece of legislation
since the 1942 Japanese Family Leave Act.
~~ Al Franken, in response to the 2004 SOTU address
------------------------------
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 2410
***************************************
