[30146] in Perl-Users-Digest
Perl-Users Digest, Issue: 1389 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 25 03:09:59 2008
Date: Tue, 25 Mar 2008 00:09:27 -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, 25 Mar 2008 Volume: 11 Number: 1389
Today's topics:
new CPAN modules on Tue Mar 25 2008 (Randal Schwartz)
Pattern matching <deepan.17@gmail.com>
Re: Pattern matching <deepan.17@gmail.com>
Re: Pattern matching <jurgenex@hotmail.com>
Re: Pattern matching <deepan.17@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: The huge amount response data problem <falconzyx@gmail.com>
Re: The huge amount response data problem <benkasminbullock@gmail.com>
Re: use base and @ISA with package re-definition bigmattstud@gmail.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 25 Mar 2008 04:42:25 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Mar 25 2008
Message-Id: <Jy9rqp.1o1K@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-Shorten-ZoffixsModuleNames-0.002
http://search.cpan.org/~zoffix/Acme-Shorten-ZoffixsModuleNames-0.002/
use Zoffix Znet's modules without those uberly long names *har* *har*
----
App-PNGCrush-0.001
http://search.cpan.org/~zoffix/App-PNGCrush-0.001/
Perl wrapper around ``pngcrush'' program
----
B-C-1.04_13
http://search.cpan.org/~rurban/B-C-1.04_13/
Perl compiler's C backend
----
B-C-1.04_14
http://search.cpan.org/~rurban/B-C-1.04_14/
Perl compiler's C backend
----
B-Debugger-0.01_03
http://search.cpan.org/~rurban/B-Debugger-0.01_03/
optree debugger
----
Bundle-Lingua-PT-0.03
http://search.cpan.org/~ambs/Bundle-Lingua-PT-0.03/
install a set of useful modules for Natural Language Processing of the Portuguese
----
Bundle-Text-SenseClusters-0.98
http://search.cpan.org/~tpederse/Bundle-Text-SenseClusters-0.98/
Bundle of CPAN modules required for SenseClusters
----
Business-OnlinePayment-Vanco-0.01
http://search.cpan.org/~jef/Business-OnlinePayment-Vanco-0.01/
Vanco Services backend for Business::OnlinePayment
----
CPAN-Reporter-1.13
http://search.cpan.org/~dagolden/CPAN-Reporter-1.13/
Adds CPAN Testers reporting to CPAN.pm
----
CPAN-Reporter-Smoker-0.08
http://search.cpan.org/~dagolden/CPAN-Reporter-Smoker-0.08/
Turnkey CPAN Testers smoking
----
Class-MethodMaker-2.11
http://search.cpan.org/~schwigon/Class-MethodMaker-2.11/
Create generic methods for OO Perl
----
Class-Std-0.0.9
http://search.cpan.org/~dmuey/Class-Std-0.0.9/
Support for creating standard "inside-out" classes
----
Cookie-XS-0.09
http://search.cpan.org/~agent/Cookie-XS-0.09/
HTTP Cookie parser in C
----
DBI-1.604
http://search.cpan.org/~timb/DBI-1.604/
Database independent interface for Perl
----
DashProfiler-1.11
http://search.cpan.org/~timb/DashProfiler-1.11/
efficiently collect call count and timing data aggregated by context
----
DateTime-TimeZone-0.74
http://search.cpan.org/~drolsky/DateTime-TimeZone-0.74/
Time zone object base class and factory
----
Deliantra-Client-0.9967
http://search.cpan.org/~mlehmann/Deliantra-Client-0.9967/
----
Devel-NYTProf-1.11
http://search.cpan.org/~akaplan/Devel-NYTProf-1.11/
line-by-line code profiler and report generator
----
Emacs-Run-0.02
http://search.cpan.org/~doom/Emacs-Run-0.02/
utilities to assist in using emacs from perl via the shell
----
Email-Stuff-2.06
http://search.cpan.org/~adamk/Email-Stuff-2.06/
A more casual approach to creating and sending Email:: emails
----
Enumeration-0.02
http://search.cpan.org/~roode/Enumeration-0.02/
Yet Another enumeration class implementation.
----
File-Flat-1.04
http://search.cpan.org/~adamk/File-Flat-1.04/
Implements a flat filesystem
----
FreeBSD-Ports-INDEXhash-1.0.0
http://search.cpan.org/~vvelox/FreeBSD-Ports-INDEXhash-1.0.0/
Generates a hash out of the FreeBSD Ports index file.
----
FreeBSD-Ports-INDEXhash-1.0.1
http://search.cpan.org/~vvelox/FreeBSD-Ports-INDEXhash-1.0.1/
Generates a hash out of the FreeBSD Ports index file.
----
FreeBSD-Ports-INDEXhash-1.0.2
http://search.cpan.org/~vvelox/FreeBSD-Ports-INDEXhash-1.0.2/
Generates a hash out of the FreeBSD Ports index file.
----
FreeBSD-Ports-INDEXhash-1.0.3
http://search.cpan.org/~vvelox/FreeBSD-Ports-INDEXhash-1.0.3/
Generates a hash out of the FreeBSD Ports index file.
----
Geo-Direction-Distance-0.0.1
http://search.cpan.org/~kokogiko/Geo-Direction-Distance-0.0.1/
Process between Lat-Lng coordinates and direction - distance
----
Lingua-Jspell-1.50_06
http://search.cpan.org/~ambs/Lingua-Jspell-1.50_06/
Perl interface to the Jspell morphological analyser.
----
Lingua-PT-Abbrev-0.06
http://search.cpan.org/~ambs/Lingua-PT-Abbrev-0.06/
An abbreviations dictionary manager for NLP
----
Lyrics-Fetcher-Lyrics007-0.04
http://search.cpan.org/~jamesr/Lyrics-Fetcher-Lyrics007-0.04/
Fetcher module for David Precious' (BIGPRESH) Lyrics::Fetcher
----
Math-SparseMatrix-0.02
http://search.cpan.org/~tpederse/Math-SparseMatrix-0.02/
Provides basic sparse matrix operations such as creation, reading from file, reading transpose from file and writing to file.
----
Math-SparseVector-0.04
http://search.cpan.org/~tpederse/Math-SparseVector-0.04/
Supports sparse vector operations such as setting a value in a vector, reading a value at a given index, obtaining all indices, addition and dot product of two sparse vectors, and vector normalization
----
Module-Install-0.71
http://search.cpan.org/~adamk/Module-Install-0.71/
Standalone, extensible Perl module installer
----
Module-Install-RTx-0.22
http://search.cpan.org/~ruz/Module-Install-RTx-0.22/
RT extension installer
----
Muldis-DB-0.6.2
http://search.cpan.org/~duncand/Muldis-DB-0.6.2/
Full-featured truly relational DBMS in Perl
----
Net-FireEagle-0.8
http://search.cpan.org/~simonw/Net-FireEagle-0.8/
access Yahoo's new FireEagle developer service
----
OpenResty-0.1.9
http://search.cpan.org/~agent/OpenResty-0.1.9/
General-purpose web service platform for web applications
----
POE-Component-Client-Keepalive-0.1001
http://search.cpan.org/~rcaputo/POE-Component-Client-Keepalive-0.1001/
manage connections, with keep-alive
----
POE-Component-Client-Ping-1.14
http://search.cpan.org/~rcaputo/POE-Component-Client-Ping-1.14/
a non-blocking ICMP ping client
----
POE-Component-Supervisor-0.01
http://search.cpan.org/~nuffin/POE-Component-Supervisor-0.01/
Erlang inspired babysitting
----
POE-Test-Loops-0.98
http://search.cpan.org/~rcaputo/POE-Test-Loops-0.98/
Reusable tests for POE::Loop authors
----
Parse-Marpa-0.205_004
http://search.cpan.org/~jkegl/Parse-Marpa-0.205_004/
(Alpha) Earley's algorithm with LR(0) precomputation
----
RT-Client-Console-0.2.0
http://search.cpan.org/~dams/RT-Client-Console-0.2.0/
Text based RT console
----
RTx-Calendar-0.05
http://search.cpan.org/~nchuche/RTx-Calendar-0.05/
Calendar for RT due tasks
----
Regexp-Compare-0.07
http://search.cpan.org/~vbar/Regexp-Compare-0.07/
partial ordering for regular expressions
----
Slay-Makefile-0.11
http://search.cpan.org/~nodine/Slay-Makefile-0.11/
Wrapper to Slay::Maker that reads the rules from a file
----
TM-1.34
http://search.cpan.org/~drrho/TM-1.34/
Topic Maps, Base Class
----
Test-WWW-Selenium-0.15
http://search.cpan.org/~lukec/Test-WWW-Selenium-0.15/
Test applications using Selenium Remote Control
----
Text-NSP-1.07
http://search.cpan.org/~tpederse/Text-NSP-1.07/
Count and identify significant collocations and Ngrams in text
----
Tie-File-AnyData-0.03
http://search.cpan.org/~motif/Tie-File-AnyData-0.03/
Access the data of a disk file via a Perl array
----
Time-Format-1.03
http://search.cpan.org/~roode/Time-Format-1.03/
Easy-to-use date/time formatting.
----
Variable-Magic-0.14
http://search.cpan.org/~vpit/Variable-Magic-0.14/
Associate user-defined magic to variables from Perl.
----
WWW-OpenResty-0.02
http://search.cpan.org/~agent/WWW-OpenResty-0.02/
Client-side library for OpenResty servers
----
WWW-Pastebin-UbuntuNlOrg-Retrieve-0.001
http://search.cpan.org/~zoffix/WWW-Pastebin-UbuntuNlOrg-Retrieve-0.001/
retrieve pastes from http://paste.ubuntu-nl.org/ website
----
Win32-Env-Path-0.01
http://search.cpan.org/~adamk/Win32-Env-Path-0.01/
Manipulate environment PATH strings
----
ack-1.78
http://search.cpan.org/~petdance/ack-1.78/
grep-like text finder
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, 24 Mar 2008 21:50:37 -0700 (PDT)
From: Deepan Perl XML Parser <deepan.17@gmail.com>
Subject: Pattern matching
Message-Id: <9bff4a9a-bb3c-4c19-81fd-0f472a5d54f1@e6g2000prf.googlegroups.com>
Hi all,
I am having a file like below:
<?xml version="1.0" encoding="UTF-8"?>
<log xmlns="http://www.httpwatch.com/xml/log/5.1">
<entry method="GET" URL="http://www.google.com/sa/frame_main.cgi">
.
.
.
.
-------some text-------------
.
.
.
</entry>
<entry method="GET" URL="http://www.toogle.com/framer/main.cgi">
.
.
.
.
-------some text-------------
.
.
.
</entry>
<entry method="GET" URL="http://www.google.com/sa/frame_main.html">
.
.
.
.
-------some text-------------
.
.
.
</entry>
<page id="page_0" title="Sustaining Portal" dynamic="true"
unknown="false">
<started>00:00:00.000</started>
<startedDateTime>2008-03-25T09:52:12.791</startedDateTime>
</page>
<page id="page_1" title="Sustaining Portal" dynamic="true"
unknown="false">
<started>00:00:08.455</started>
<startedDateTime>2008-03-25T09:52:21.246</startedDateTime>
</page>
<page id="page_2" title="Sustaining Portal" dynamic="true"
unknown="false">
<started>00:00:20.296</started>
<startedDateTime>2008-03-25T09:52:33.087</startedDateTime>
</page>
<page id="page_3" title="Sustaining Portal" dynamic="true"
unknown="false">
<started>00:00:29.848</started>
<startedDateTime>2008-03-25T09:52:42.639</startedDateTime>
</page>
</log>
----------------------------------------------------------------------------------
Now how to get all those <entry ....> tags into an array? I mean
getting
<entry method="GET" URL="http://www.google.com/sa/
frame_main.cgi">
<entry method="GET" URL="http://www.toogle.com/framer/
main.cgi">
<entry method="GET" URL="http://www.google.com/sa/
frame_main.html">
into some array.
Thanks,
Deepan
------------------------------
Date: Mon, 24 Mar 2008 22:04:18 -0700 (PDT)
From: Deepan Perl XML Parser <deepan.17@gmail.com>
Subject: Re: Pattern matching
Message-Id: <c1224d4d-0972-45a7-8e67-7b7b8710226c@e10g2000prf.googlegroups.com>
On Mar 25, 9:50 am, Deepan Perl XML Parser <deepan...@gmail.com>
wrote:
> Hi all,
> I am having a file like below:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <log xmlns="http://www.httpwatch.com/xml/log/5.1">
> <entry method="GET" URL="http://www.google.com/sa/frame_main.cgi">
> .
> .
> .
> .
> -------some text-------------
> .
> .
> .
> </entry>
> <entry method="GET" URL="http://www.toogle.com/framer/main.cgi">
> .
> .
> .
> .
> -------some text-------------
> .
> .
> .
> </entry>
> <entry method="GET" URL="http://www.google.com/sa/frame_main.html">
> .
> .
> .
> .
> -------some text-------------
> .
> .
> .
> </entry>
> <page id="page_0" title="Sustaining Portal" dynamic="true"
> unknown="false">
> <started>00:00:00.000</started>
> <startedDateTime>2008-03-25T09:52:12.791</startedDateTime>
> </page>
> <page id="page_1" title="Sustaining Portal" dynamic="true"
> unknown="false">
> <started>00:00:08.455</started>
> <startedDateTime>2008-03-25T09:52:21.246</startedDateTime>
> </page>
> <page id="page_2" title="Sustaining Portal" dynamic="true"
> unknown="false">
> <started>00:00:20.296</started>
> <startedDateTime>2008-03-25T09:52:33.087</startedDateTime>
> </page>
> <page id="page_3" title="Sustaining Portal" dynamic="true"
> unknown="false">
> <started>00:00:29.848</started>
> <startedDateTime>2008-03-25T09:52:42.639</startedDateTime>
> </page>
> </log>
>
> ----------------------------------------------------------------------------------
>
> Now how to get all those <entry ....> tags into an array? I mean
> getting
>
> <entry method="GET" URL="http://www.google.com/sa/
> frame_main.cgi">
> <entry method="GET" URL="http://www.toogle.com/framer/
> main.cgi">
> <entry method="GET" URL="http://www.google.com/sa/
> frame_main.html">
>
> into some array.
>
> Thanks,
> Deepan
while($string =~ m#<entry method=.* URL="http://(.*)">#g)
{
..................
..................
}
I am able to do this by using the above expr. Is there any fair way of
doing it other than this?
------------------------------
Date: Tue, 25 Mar 2008 05:40:47 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Pattern matching
Message-Id: <ps3hu3pr51620glsk58m906cpjkadnr0c9@4ax.com>
Deepan Perl XML Parser <deepan.17@gmail.com> wrote:
> I am having a file like below:
><?xml version="1.0" encoding="UTF-8"?>
[...]
>Now how to get all those <entry ....> tags into an array? I mean
You would use an XML parser to parse XML.
Has nothing to do with pattern matching at all.
jue
------------------------------
Date: Mon, 24 Mar 2008 22:54:37 -0700 (PDT)
From: Deepan Perl XML Parser <deepan.17@gmail.com>
Subject: Re: Pattern matching
Message-Id: <06888ec6-e3e7-409b-83a8-17bdcbeace4e@e10g2000prf.googlegroups.com>
On Mar 25, 10:40 am, J=FCrgen Exner <jurge...@hotmail.com> wrote:
> Deepan Perl XML Parser <deepan...@gmail.com> wrote:
>
> > I am having a file like below:
> ><?xml version=3D"1.0" encoding=3D"UTF-8"?>
> [...]
> >Now how to get all those <entry ....> tags into an array? I mean
>
> You would use an XML parser to parse XML.
> Has nothing to do with pattern matching at all.
>
> jue
No i am writing my own XML parser.
------------------------------
Date: Tue, 25 Mar 2008 06:17:52 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <kO0Gj.8267$Rq1.4217@nlpi068.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: Mon, 24 Mar 2008 21:53:09 -0700 (PDT)
From: "falconzyx@gmail.com" <falconzyx@gmail.com>
Subject: Re: The huge amount response data problem
Message-Id: <9040a4a7-9a22-432e-83ec-16c38ddda5cd@s37g2000prg.googlegroups.com>
On Mar 25, 10:44 am, "falcon...@gmail.com" <falcon...@gmail.com>
wrote:
> I have a issue:
> 1. I want to open a file and use the data from the file to construct
> the url.
> 2. After I constructed the url and sent it, I got the response html
> data and some parts are what I want store inot the files.
>
> It seems like a very easy thing, however, the issue is that the data
> from the file that I have to open are too huge, which I have to
> consturct almost 200000 url address to send and parse response data.
> And the speed is very very slow.
>
> I have no idea with thread or db cache, so I want some help .
>
> Please give me some advices that what I should do to improve the speed
>
> Thanks very much.
this is my code:
use threads;
use LWP::UserAgent;
use LWP::Simple;
use Data::Dumper;
use strict;
use threads::shared;
my $wordsList = &get_request;
#print Dumper( @wordsList );
my @words = split("\n", $wordsList);
#print Dumper(@words);
my @url = &get_url(@words);
#print Dumper(@url);
my @thr;
foreach my $i (1..100000) {
push @thr, threads->new(\&get_html, $url[$i]);
}
foreach (@thr) {
$_->detach; # it doesn't work!!!!!!!!!!!!!!!!
}
sub get_html {
my (@url) = @_;
}
sub get_request {
..........
return $wordsList;
}
sub get_url {
my (@words) = @_;
................
return @url;
}
------------------------------
Date: Tue, 25 Mar 2008 00:06:19 -0700 (PDT)
From: Ben Bullock <benkasminbullock@gmail.com>
Subject: Re: The huge amount response data problem
Message-Id: <1c6f8814-d689-4f71-9c0b-52edaa3fe1fe@i12g2000prf.googlegroups.com>
Your code is hopelessly inefficient. 100,000 strings of even twenty
characters is at least two megabytes of memory. Then you've doubled
that number with the creation of the URL, and then you are creating
arrays of all these things, so you've used several megabytes of
memory.
Instead of first creating a huge array of names, then a huge array of
URLs, why don't you just read in one line of the file at a time, then
try to get data from each URL? Read in one line of the first file,
create its URL, get the response data, store it, then go back and get
the next line of the file, etc. A 100,000 line file actually isn't
that big.
But if you are getting all these files from the internet, the biggest
bottleneck is probably the time the code spends waiting for a response
from the web servers it's requested. You'd have to think about making
parallel requests somehow to solve that.
------------------------------
Date: Mon, 24 Mar 2008 21:46:30 -0700 (PDT)
From: bigmattstud@gmail.com
Subject: Re: use base and @ISA with package re-definition
Message-Id: <2f49d04d-ba69-438c-9321-5aa28a973a89@s13g2000prd.googlegroups.com>
On Mar 25, 2:57 pm, Uri Guttman <u...@stemsystems.com> wrote:
> >>>>> "b" == bigmattstud <bigmatts...@gmail.com> writes:
>
> you seem to be going about this in a very bizarre and tricky way. it is
> much easier to dynamically load modules with different names (maybe
> under the same higher level namespace) and use OO polymorphism to call
> into them as needed. no muss no fuss!
>
Yes, I'd agree with that. I probably need to include some background,
this is actually a system for handling deployment of code from a
source control system. All code needs to be extracted from source
control (based on tags) and copied to some target directory, but some
file types need to have some sort of 'execution ready' behaviour
performed on them after extraction, eg Java programs need to be
compiled and SQL files need to be executed in a database. Our current
system does this using Ant, by placing a build.xml file in the target
directory. The build.xml file serves two purposes: (a) its presence
indicates that some further action is required and (b) the contents
specify what action(s) to perform. If a build.xml is found in the
target directory Ant gets invoked and the required actions are
performed.
I started to get sick of the limitations of Ant, and since the wrapper
script which was handling this deploy was in Perl I decided to try and
implement a similar concept. Each target directory would contain a
very small Perl class which could extend various base classes to
implement specific deployment behaviours. Since there are many of
these directories, and the classes are not required after that
directory has been processed, I thought it was easier to keep the same
name rather than trying to manage the namespace clashes within the
modules.
>
> what decides which of these modules (or more than one?) to load?
>
As above, the wrapper script moves through the target deploy
directories and loads the module if it finds one.
> b> # Clean out the previous definition of MyMod by deleting the entries
> b> from the INC hash and the global symbol
> b> # table
> b> delete $INC{"MyMod.pm"} ;
> b> delete $main::{'MyMod::'} ;
> b> pop @INC ;
>
> ewww.
>
Yes, I thought the same, that's why I asked the question. It did seem
to work though.
------------------------------
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 1389
***************************************
