[30087] in Perl-Users-Digest
Perl-Users Digest, Issue: 1330 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 4 06:09:44 2008
Date: Tue, 4 Mar 2008 03:09:08 -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 Tue, 4 Mar 2008 Volume: 11 Number: 1330
Today's topics:
Auction Software <swasaaron@gmail.com>
Classified Script <swasaaron@gmail.com>
Does LWP::UserAgent download images himanshu.garg@gmail.com
Re: Does LWP::UserAgent download images <greymausg@mail.com>
evaluating shared rescources on remote system. <ramakrishnadeepak@gmail.com>
Re: FAQ 4.53 How do I manipulate arrays of bits? sheinrich@my-deja.com
new CPAN modules on Tue Mar 4 2008 (Randal Schwartz)
Re: Parsing natural language timestamps <ced@blv-sam-01.ca.boeing.com>
Re: php vs perl for RDBMS backend work <usenet200801@tobyinkster.co.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: reading from stdin via pipe, buffering? <Rudy.Gevaertno@spamugent.be>
Rename File Using Strring Found in File? <Entwadumayla@HyenaKiller.com>
Re: Rename File Using Strring Found in File? <Entwadumayla@HyenaKiller.com>
Two perl-specific postings on Codeaholic <Bruce.Axtens@gmail.com>
Re: Two perl-specific postings on Codeaholic <someone@example.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 3 Mar 2008 22:18:58 -0800 (PST)
From: Agnes <swasaaron@gmail.com>
Subject: Auction Software
Message-Id: <98fedd8f-60a4-4220-a9a7-5d175f11cff9@s12g2000prg.googlegroups.com>
AJ Auction Pro is the best Auction Portal script software available in
the Universe. Being a PHP /MYSQL Script providing complete online
auction solutions, it has now expanded to offer services such as
Merchant Solutions, Packaged Software and Enterprise Solutions.
Unlike the various majorities of services out there we make a
difference!
Sources: http://www.ajauctionpro.com/products/hosting_pack.php?pro=host&plan_id=13
------------------------------
Date: Mon, 3 Mar 2008 22:24:05 -0800 (PST)
From: Agnes <swasaaron@gmail.com>
Subject: Classified Script
Message-Id: <29cad463-b2ed-44f2-a9a3-34b6d6c20d1a@e23g2000prf.googlegroups.com>
AJ Dating endues your online business with magnetic features and holds
more users to your website. AJ Dating is molded for the one who is in
search of good business in the e-commerce market. With AJ auction you
can construct and create your own dating site. It has potential to
generate very heavy revenues for you.
Sources: http://www.ajclassifieds.net/features.php
------------------------------
Date: Tue, 4 Mar 2008 02:15:46 -0800 (PST)
From: himanshu.garg@gmail.com
Subject: Does LWP::UserAgent download images
Message-Id: <6fc6f995-30a1-44e4-ab1d-9e3d2d6e4b0f@u10g2000prn.googlegroups.com>
Hi,
Will the following code also download the images on
search.cpan.org, if any :-
require LWP::UserAgent;
my $ua = LWP::UserAgent->new;
my $response = $ua->get('http://search.cpan.org/');
If yes, is there a way to avoid them. I want to minimize the
bandwidth the program consumes.
Thank You,
Himanshu.
------------------------------
Date: 4 Mar 2008 10:40:42 GMT
From: greymaus <greymausg@mail.com>
Subject: Re: Does LWP::UserAgent download images
Message-Id: <slrnfsq9g3.5dt.greymausg@maus.org>
On 2008-03-04, himanshu.garg@gmail.com <himanshu.garg@gmail.com> wrote:
> Hi,
>
> Will the following code also download the images on
> search.cpan.org, if any :-
>
> require LWP::UserAgent;
> my $ua = LWP::UserAgent->new;
> my $response = $ua->get('http://search.cpan.org/');
>
> If yes, is there a way to avoid them. I want to minimize the
> bandwidth the program consumes.
>
> Thank You,
> Himanshu.
>
Use WWW::Mechanize, a superset of LWP::UserAgent. read the docs.
--
greymaus
Just Another Grumpy Old Man
------------------------------
Date: Mon, 3 Mar 2008 23:42:04 -0800 (PST)
From: deepak <ramakrishnadeepak@gmail.com>
Subject: evaluating shared rescources on remote system.
Message-Id: <95426f2d-1011-4c00-8d52-01cb378ea869@i12g2000prf.googlegroups.com>
Hi,
Is there any perl module through which we can find the shared files
on a remote XP system.If not is there any idea how to get the shared
files on the remote system.
thanx in advance.
------------------------------
Date: Tue, 4 Mar 2008 00:08:20 -0800 (PST)
From: sheinrich@my-deja.com
Subject: Re: FAQ 4.53 How do I manipulate arrays of bits?
Message-Id: <86893652-f585-4886-abea-8ec057a59e87@u69g2000hse.googlegroups.com>
On Mar 3, 10:12 pm, Uri Guttman <u...@stemsystems.com> wrote:
> >>>>> "bdf" == brian d foy <brian.d....@gmail.com> writes:
>
> bdf> In article
> bdf> <ca334bbf-a028-4179-bcac-6fe5105b1...@13g2000hsb.googlegroups.com>,
> bdf> <sheinr...@my-deja.com> wrote:
>
> >> On Feb 29, 9:03 pm, PerlFAQ Server <br...@stonehenge.com> wrote:
> >> <snip>
> >> > For example, this sets $vec to have bit N set if $ints[N] was set:
> >> >
> >> > $vec = '';
> >> > foreach(@ints) { vec($vec,$_,1) = 1 }
> >> >
> >> <snip>
> >>
> >> IMHO the above sentence is wrong.
>
> and the code is wrong too.
That depends on how you see it.
The use of vec() as a replacement for pack() on a ready list of bits
has never occurred to me.
Hence my 2nd example above with some distinct bit indices specified:
my @ints = (5,0,2,4);
For this case the FAQ loop works alright.
>
> my @ints = ( 1, 0, 0, 1, 1, 0 ) ;
> my $vec = '';
> foreach(@ints) {
> vec($vec,$_,1) = 1 if $_;
>
> }
>
> print join( '', unpack 'B*', $vec ), "\n" ;
>
> foreach(0 .. $#ints) {
> vec($vec,$_,1) = $ints[$_];
>
> }
>
> print join( '', unpack 'B*', $vec ), "\n" ;
>
> output:
> 00000010
> 00011001
>
> the FAQ loop never changes the offset arg to vec so it twiddles the same
> bit over and over.
>
> in fact given a list of bit values, pack is the best answer for making a
> bit vector. vec is better for random access of bit fields (and it sucks
> because of its requirement for the field size being a power of
> 2). Bit::Vector is a very good module (speedy since it is in XS) for all
> sorts of bit stuff.
ACK
Beside the ubiquitous example for the use of vec() with select() I
only ever found an application in creating symbol distribution
patterns for sudoku solvers.
And Bit::Vector would most certainly have proven more adequate for the
task.
Steffen
------------------------------
Date: Tue, 4 Mar 2008 05:42:18 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Mar 4 2008
Message-Id: <Jx6yII.G7t@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-ReturnValue-0.04
http://search.cpan.org/~domm/Acme-ReturnValue-0.04/
report interesting module return values
----
Algorithm-Nhash-0.001
http://search.cpan.org/~mooli/Algorithm-Nhash-0.001/
Exim nhash algorithm
----
Apache-AuthCookie-3.12_01
http://search.cpan.org/~mschout/Apache-AuthCookie-3.12_01/
Perl Authentication and Authorization via cookies
----
Bit-MorseSignals-0.03
http://search.cpan.org/~vpit/Bit-MorseSignals-0.03/
The MorseSignals protocol.
----
CGI-Application-Plugin-LogDispatch-1.02
http://search.cpan.org/~ceeshek/CGI-Application-Plugin-LogDispatch-1.02/
Add Log::Dispatch support to CGI::Application
----
CGI-Application-Plugin-ParsePath-0.01
http://search.cpan.org/~dhorne/CGI-Application-Plugin-ParsePath-0.01/
populate query parameters by parsing the PATH_INFO
----
Cache-Memcached-libmemcached-0.02000
http://search.cpan.org/~dmaki/Cache-Memcached-libmemcached-0.02000/
Perl Interface to libmemcached
----
Catalyst-Plugin-AuthenCookie-0.01
http://search.cpan.org/~drolsky/Catalyst-Plugin-AuthenCookie-0.01/
Plugin for cookie-based authentication
----
Catalyst-View-CSV-0.01
http://search.cpan.org/~gaudeon/Catalyst-View-CSV-0.01/
Comma separated values or Delimiter separated values for your data
----
Catalyst-View-JSON-0.24
http://search.cpan.org/~miyagawa/Catalyst-View-JSON-0.24/
JSON view for your data
----
Coat-Persistent-0.9_6
http://search.cpan.org/~sukria/Coat-Persistent-0.9_6/
Simple Object-Relational mapping for Coat objects
----
Cookie-XS-0.05
http://search.cpan.org/~agent/Cookie-XS-0.05/
HTTP Cookie parser in C
----
Cookie-XS-0.06
http://search.cpan.org/~agent/Cookie-XS-0.06/
HTTP Cookie parser in C
----
DBD-ASAny-1.14
http://search.cpan.org/~smirnios/DBD-ASAny-1.14/
----
DBD-Multi-0.14
http://search.cpan.org/~dwright/DBD-Multi-0.14/
Manage Multiple Data Sources with Failover and Load Balancing
----
DBD-Pg-2.2.2
http://search.cpan.org/~turnstep/DBD-Pg-2.2.2/
PostgreSQL database driver for the DBI module
----
DBD-SQLAnywhere-1.16
http://search.cpan.org/~smirnios/DBD-SQLAnywhere-1.16/
----
DBIx-Web-0.73
http://search.cpan.org/~makarow/DBIx-Web-0.73/
Active Web Database Layer
----
Decision-Depends-0.18
http://search.cpan.org/~djerius/Decision-Depends-0.18/
Perform actions based upon file dependencies
----
Devel-Hook-0.005
http://search.cpan.org/~ferreira/Devel-Hook-0.005/
Mess around with BEGIN/CHECK/INIT/END blocks
----
Egg-Release-3.05
http://search.cpan.org/~lushe/Egg-Release-3.05/
Version of Egg WEB Application Framework.
----
Etk-Perl-0.08
http://search.cpan.org/~leviathan/Etk-Perl-0.08/
----
ExtUtils-Install-1.48
http://search.cpan.org/~yves/ExtUtils-Install-1.48/
install files from here to there
----
ExtUtils-Install-1.49
http://search.cpan.org/~yves/ExtUtils-Install-1.49/
install files from here to there
----
File-Maintenance-0.01
http://search.cpan.org/~dhorne/File-Maintenance-0.01/
Maintain files based on their age.
----
File-Stat-OO-0.01
http://search.cpan.org/~dhorne/File-Stat-OO-0.01/
OO interface for accessing file status attributes
----
Finance-Bank-Cahoot-0.06
http://search.cpan.org/~masaccio/Finance-Bank-Cahoot-0.06/
Check your Cahoot bank accounts from Perl
----
Finance-Card-Citibank-1.70
http://search.cpan.org/~mgrimes/Finance-Card-Citibank-1.70/
Check your Citigroup credit card accounts from Perl
----
Geo-LocaPoint-0.0.2
http://search.cpan.org/~kokogiko/Geo-LocaPoint-0.0.2/
Simple encoder/decoder of LocaPoint
----
Gtk2-ImageView-0.03
http://search.cpan.org/~ratcliffe/Gtk2-ImageView-0.03/
----
HTML-FillInForm-Lite-1.00
http://search.cpan.org/~gfuji/HTML-FillInForm-Lite-1.00/
Fills in HTML forms with data
----
Linux-loadavg-0.06
http://search.cpan.org/~perlboy/Linux-loadavg-0.06/
Get system load averages (via getloadavg(3C) system call)
----
Linux-loadavg-0.07
http://search.cpan.org/~perlboy/Linux-loadavg-0.07/
Get system load averages (via getloadavg(3C) system call)
----
Memcached-libmemcached-0.1701
http://search.cpan.org/~timb/Memcached-libmemcached-0.1701/
Thin fast full interface to the libmemcached client API
----
Net-Delicious-1.13
http://search.cpan.org/~ascope/Net-Delicious-1.13/
OOP for the del.icio.us API
----
Net-MRIM-1.07
http://search.cpan.org/~aau/Net-MRIM-1.07/
Perl implementation of mail.ru agent protocol
----
Net-OBEX-0.001
http://search.cpan.org/~zoffix/Net-OBEX-0.001/
implementation of OBEX protocol
----
Net-Whois-Gateway-Client-0.05
http://search.cpan.org/~graykot/Net-Whois-Gateway-Client-0.05/
Interface to Net::Whois::Gateway::Server
----
Net-Whois-Gateway-Server-0.05
http://search.cpan.org/~graykot/Net-Whois-Gateway-Server-0.05/
whois gateway
----
OOB-0.08
http://search.cpan.org/~elizabeth/OOB-0.08/
out of band data for any data structure in Perl
----
POE-Component-Client-Whois-Smart-0.09
http://search.cpan.org/~graykot/POE-Component-Client-Whois-Smart-0.09/
Provides very quick WHOIS queries with smart features.
----
POE-Component-IRC-5.70
http://search.cpan.org/~bingos/POE-Component-IRC-5.70/
a fully event-driven IRC client module.
----
Shell-Perl-0.0016
http://search.cpan.org/~ferreira/Shell-Perl-0.0016/
A read-eval-print loop in Perl
----
Socket-GetAddrInfo-0.08
http://search.cpan.org/~pevans/Socket-GetAddrInfo-0.08/
RFC 2553's getaddrinfo and getnameinfo functions.
----
Statistics-QMethod-QuasiNormalDist-0.01
http://search.cpan.org/~zarquon/Statistics-QMethod-QuasiNormalDist-0.01/
----
Symbol-Approx-Sub-2.03
http://search.cpan.org/~davecross/Symbol-Approx-Sub-2.03/
Perl module for calling subroutines by approximate names!
----
Sys-Manage-0.59
http://search.cpan.org/~makarow/Sys-Manage-0.59/
Systems management commands/scripts environment
----
Text-CSV-1.01
http://search.cpan.org/~makamaka/Text-CSV-1.01/
comma-separated values manipulator (using XS or PurePerl)
----
Text-Trac-0.10
http://search.cpan.org/~mizzy/Text-Trac-0.10/
Perl extension for formatting text with Trac Wiki Style.
----
WWW-OpenResty-0.01
http://search.cpan.org/~agent/WWW-OpenResty-0.01/
Client-side library for OpenResty servers
----
WebService-Careerjet-0.05
http://search.cpan.org/~jeteve/WebService-Careerjet-0.05/
Perl interface to Careerjet's public search API
----
WebService-MusicBrainz-0.17
http://search.cpan.org/~bfaist/WebService-MusicBrainz-0.17/
----
Win32-API-0.54
http://search.cpan.org/~cosimo/Win32-API-0.54/
Perl Win32 API Import Facility
----
devel-nytprof-0.01
http://search.cpan.org/~akaplan/devel-nytprof-0.01/
----
kurila-1.8_0
http://search.cpan.org/~tty/kurila-1.8_0/
Perl Kurila
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: Mon, 3 Mar 2008 21:26:25 -0800 (PST)
From: "comp.llang.perl.moderated" <ced@blv-sam-01.ca.boeing.com>
Subject: Re: Parsing natural language timestamps
Message-Id: <2e4ef2b9-97df-417b-b8c8-475e18e992bb@i29g2000prf.googlegroups.com>
On Mar 3, 12:51 pm, "comp.llang.perl.moderated" <c...@blv-
sam-01.ca.boeing.com> wrote:
> On Mar 3, 12:37 am, Peter Makholm <pe...@makholm.net> wrote:
>
> > I have a command line application where the use specifies a time span
> > with two arguments --from and --to. At the moment I'm using strptime
> > from Date::Parse, but it would be nice to support dates like '2 days
> > ago', 'today', 'next friday'.
>
> > If the user doesn't specifies a exact time but just a day I would like
> > to have the from argument use the start of the date (00:00:00) and the
> > to argument use the end of the date (23:59:59).
> >...
>
> A Date::Manip concoction could help if you're say, trying to normalize
> "today".
>
> If "today" is the --from:
>
> UnixDate(UnixDate(ParseDate("today"),"%b%e%Y")"%s)
>
That should be:
UnixDate UnixDate(ParseDate("today"),"%b%e%Y"),"%s"
--
Charles DeRykus
> --
> Charles DeRykus
------------------------------
Date: Tue, 4 Mar 2008 10:56:39 +0000
From: Toby A Inkster <usenet200801@tobyinkster.co.uk>
Subject: Re: php vs perl for RDBMS backend work
Message-Id: <7gmv95-7gu.ln1@ophelia.g5n.co.uk>
dcruncher4 wrote:
> So I need some real reasons as to why php is superior to perl. I got one
> so far: It has a more natural support for OO, which I agree.
PHP's version of the OO paradigm is a lot more familiar to people who come
from Java backgrounds, because it has familiar ideas like classes and
objects, with methods and properties, but Perl's OO is more flexible. Perl
can do, for instance, multiple inheritance, whereas PHP and Java cannot.
--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 34 days, 17:01.]
Bottled Water
http://tobyinkster.co.uk/blog/2008/02/18/bottled-water/
------------------------------
Date: Tue, 04 Mar 2008 08:17:35 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <zA7zj.14873$Ej5.6549@newssvr29.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: Tue, 04 Mar 2008 08:47:18 +0100
From: Rudy Gevaert <Rudy.Gevaertno@spamugent.be>
Subject: Re: reading from stdin via pipe, buffering?
Message-Id: <fqiuvd$1ia$1@ikaria.belnet.be>
xhoster@gmail.com wrote:
> Rudy Gevaert <Rudy.Gevaertno@spamugent.be> wrote:
>> Hi,
>>
>> I have written a perl program that reads from stdin:
>> while(<STDIN>)
>> {
>> chomp
>> do_it($_);
>> }
>> Data is fed to it via a pipe:
>>
>> cat myfile | ./myprogram
>>
>> When running the program, the program doesn't always read the whole
>> line. I'm guessing this has something to do with the stdin buffer.
>
> My guess is that you are misinterpreting something. Maybe you have
> cross OS line ending problems.
I have checked the file and it only has \n on the end of all the lines.
>> I would like to know how I can make that perl gets the whole line. As
>> it is clearly failing from time to time.
>
> That is far from clear to me. Can you produce an example we can
> run to show this problem?
I have looked at my problem a bit more and changed the program so I call
open(FILE, "-") || die("Can't read from stdin: $!");
while(<FILE>){ ...}
The following happens:
1) I run my command: cat bigfile | ./myprogram
2) I do an strace on 'myprogram' and on 'cat'. I observe:
a) cat is reading the whole file!
b) cat finishes reading the whole and 'myprogram' happily carries on
c) cat reads from/ writes to the file in blocks of 4096 bytes:
read(3, "\nan@email.com\nother@mail.com"..., 4096) = 4096
write(1, "\nan@email.com\nother@mail.com"..., 4096) = 4096
d) 'myprogram' reads from stdin in blocks of 4096 bytes:
read(0, "e\nmarieke.bocket@ugent.be\nsofie."..., 4096) = 4096
e) But then, 'myprogram' reads:
read(0, "", 4096) = 0
But that is not at the end of the file!
I'll try to come up with a program. But reading a lot of lines and just
printing them doesn't trigger the error.
Thanks in advance,
Rudy
------------------------------
Date: Tue, 04 Mar 2008 04:01:28 GMT
From: He Who Greets With Fire <Entwadumayla@HyenaKiller.com>
Subject: Rename File Using Strring Found in File?
Message-Id: <21hps35eoj2u6s75m067u6tuas8237g4s9@4ax.com>
I am trying to write a little script to access many files in folder,
parse each file and then if a certain string is found, rename the file
using a substring of that found string.
OK, I have posted here before many many years ago (around 2001), back
when I did some perl programming. I even wrote a program as my senior
project to parse financial news stories and assign values to the
stories based on whether there were negative or positive words in the
news stories.
Some people here helped me with that program, and when I finished that
project I posted the code to the web.
Now I need some more help. :-)
I have not programmed in a long time. I know perl has changed
somewhat. I have downloaded the latest activestate win32 perl and
installed it.
I have a file directory named E:/personalinjury. In the file directory
are 821 files named from 1.htm to 821.htm
I want to access each file in turn, and use a regex to parse the file
contents to see if a string similar to this one is found in it:
Citation: 20-333 Dorsaneo, Texas Litigation Guide § 333.103
Some files will not have a string similar to the above string. I am
not interesting in renaming those files.
If the string above is found, the numbers 20-333 and 333.103 will be
the ones that vary from file to file. All the words in the string
above and the section symbol will remain the same from file to file.
So another string I might find might be:
20-332 Dorsaneo, Texas Litigation Guide § 332.107
I am interested in that string of numbers at the end; in the examples
above, it is 333.103 and 332.107, but there are many other variations.
So, I want to rename that file to 333.103 from whatever it was before
(e.g., so I would rename the file from 1.htm or 5.htm or 200.htm etc
to 333.103.htm or 333.105.htm or 332.203.htm or whatever).
So, my script should strip off that string of digits and the end,
including the decimal point, and rename the file using that string of
digits.
Anyone got any ideas?
thx
------------------------------
Date: Tue, 04 Mar 2008 04:08:07 GMT
From: He Who Greets With Fire <Entwadumayla@HyenaKiller.com>
Subject: Re: Rename File Using Strring Found in File?
Message-Id: <jjips35417jia96p5js08but3v7ohb5tlu@4ax.com>
On Tue, 04 Mar 2008 04:01:28 GMT, He Who Greets With Fire
<Entwadumayla@HyenaKiller.com> wrote:
>I have a file directory named E:/personalinjury.
Oops! it should be a BACKslash: E:\personalinjury
------------------------------
Date: Mon, 3 Mar 2008 20:49:55 -0800 (PST)
From: axtens <Bruce.Axtens@gmail.com>
Subject: Two perl-specific postings on Codeaholic
Message-Id: <d1060dda-02d3-4278-b2aa-08c11826f120@d4g2000prg.googlegroups.com>
G'day everyone
1. [Perl/PDK/PerlCtrl] Returning an array of arrays for VB6/VBScript
http://codeaholic.blogspot.com/2008/02/perlpdkperlctrl-returning-array-of.html
2. [Perl] How not to do it? http://codeaholic.blogspot.com/2008/03/perl-how-not-to-do-it.html
Kind regards,
Bruce.
------------------------------
Date: Tue, 04 Mar 2008 06:40:27 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Two perl-specific postings on Codeaholic
Message-Id: <v96zj.58884$FO1.30804@edtnps82>
axtens wrote:
> G'day everyone
>
> 1. [Perl/PDK/PerlCtrl] Returning an array of arrays for VB6/VBScript
> http://codeaholic.blogspot.com/2008/02/perlpdkperlctrl-returning-array-of.html
> 2. [Perl] How not to do it? http://codeaholic.blogspot.com/2008/03/perl-how-not-to-do-it.html
> (I'm no guru when it comes to Perl, so if you see something that could
> be expressed in a more efficient manner, please let me know.)
> 1. Remove all 's'
> sub rule1 {
> my $arg = shift;
> $arg =~ s/s//g;
> return $arg;
> }
sub rule1 {
( my $arg = shift ) =~ tr/s//d;
return $arg;
}
> 2. Sort the characters of the word into alphabetic order
> sub rule2 {
> my $arg = shift;
> my @arr = split( //, $arg );
> @arr = sort @arr ;
> $arg = join( '', @arr );
> return $arg;
> }
sub rule2 {
return join '', sort split //, shift;
}
> 3. Convert all vowels to 'e
> sub rule3 {
> my $arg = shift;
> $arg =~ s/[a|e|i|o|u]/e/g;
> return $arg;
> }
Why are you converting the '|' character and the 'e' character to 'e'?
sub rule3 {
( my $arg = shift ) =~ tr/aiou/e/;
return $arg;
}
> 4. Replace the first letter with 'n'
> sub rule4 {
> my $arg = shift;
> $arg =~ s/^./n/;
> return $arg;
> }
The . character class matches a lot more than just letters, or did you
really mean "replace any first character except newline with 'n'".
sub rule4 {
( my $arg = shift ) =~ s/\A[[:alpha:]]/n/;
return $arg;
}
> 5. Drop the last letter
> sub rule5 {
> $arg = shift;
> $arg =~ s/.$//;
> return $arg;
> }
The . character class matches a lot more than just letters.
sub rule5 {
( my $arg = shift ) =~ s/[[:alpha:]]\z//;
return $arg;
}
> 6. Replace letter pairs with 'ow'
> sub rule6 {
> $arg = shift;
> @arr = split( //, "abcdefghijklmnopqrstuvwxyz" );
> for $letter ( @arr ) {
> $arg =~ s/$letter$letter/"ow"/eg;
> }
> return $arg;
> }
sub rule6 {
( my $arg = shift ) =~ s/([[:lower:]])\1/ow/g;
return $arg;
}
> Each rule is evaluated against the passed in value in $arg, and stored
> in $res. $reason is cleared and each test applied to $res.
>
> $res = eval( "rule$j(\"$arg\")" );
Ouch! Use a dispatch table instead of string eval().
my %rule = (
1 => sub {
( my $arg = shift ) =~ tr/s//d;
return $arg;
},
2 => sub {
return join '', sort split //, shift;
},
3 => sub {
( my $arg = shift ) =~ tr/aiou/e/;
return $arg;
},
# more rules here
);
# and later on, use rules
$res = $rule{ $j }( $arg );
John
--
Perl isn't a toolbox, but a small machine shop where you
can special-order certain sorts of tools at low cost and
in short order. -- Larry Wall
------------------------------
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 1330
***************************************
