[30806] in Perl-Users-Digest
Perl-Users Digest, Issue: 2051 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Dec 12 11:09:49 2008
Date: Fri, 12 Dec 2008 08:09:07 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 12 Dec 2008 Volume: 11 Number: 2051
Today's topics:
Re: Is there a port of Perl for Win* platforms? <stoupa@practisoft.cz>
new CPAN modules on Fri Dec 12 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Processing Multiple Large Files <1usa@llenroc.ude.invalid>
Re: Processing Multiple Large Files <cartercc@gmail.com>
Re: The single biggest STUPIDITY in Perl ... <afmcc@btinternet.com>
Re: The single biggest STUPIDITY in Perl ... <cartercc@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 12 Dec 2008 09:27:52 +0100
From: "Petr Vileta \"fidokomik\"" <stoupa@practisoft.cz>
Subject: Re: Is there a port of Perl for Win* platforms?
Message-Id: <ght7b8$mvc$1@ns.felk.cvut.cz>
Ilya Zakharevich wrote:
> Is there a port of Perl for Win* platforms? The minimal functionality
> required is to read @ARGV, open() files for read and write, and get a
> directory listing.
>
> Thanks,
> Ilya
>
> P.S. I carry ActiveState port on a memory stick (age = couple of
> years), but it is not able to do any of these...
I'm using ActiveState Perl on WindowsXP and MS-IIS2 and it work well.
After installation please check Windows registry if "perl.exe" key is
registered. You should see some like
[HKEY_CLASSES_ROOT\Applications\perl.exe]
[HKEY_CLASSES_ROOT\Applications\perl.exe\shell]
[HKEY_CLASSES_ROOT\Applications\perl.exe\shell\Open]
[HKEY_CLASSES_ROOT\Applications\perl.exe\shell\Open\command]
@="\"C:\\Perl\\bin\\perl.exe\" \"%1\" %*"
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail.
Send me your mail from another non-spammer site please.)
Please reply to <petr AT practisoft DOT cz>
------------------------------
Date: Fri, 12 Dec 2008 05:42:23 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Dec 12 2008
Message-Id: <KBr16n.G3D@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-6502-0.74
http://search.cpan.org/~andya/Acme-6502-0.74/
Pure Perl 65C02 simulator.
----
Advent-Bundles-0.01
http://search.cpan.org/~davidrw/Advent-Bundles-0.01/
Collection of year-by-year Bundles of the Perl Advent Calendar modules
----
AnyEvent-CouchDB-1.05
http://search.cpan.org/~beppu/AnyEvent-CouchDB-1.05/
a non-blocking CouchDB client based on jquery.couch.js
----
Apache2-AuthCASSimple-0.06
http://search.cpan.org/~yvesago/Apache2-AuthCASSimple-0.06/
Apache2 module to authentificate trough a CAS server
----
App-ZofCMS-Plugin-YouTube-0.0101
http://search.cpan.org/~zoffix/App-ZofCMS-Plugin-YouTube-0.0101/
CRUD-type plugin to manage YouTube videos
----
Bluepay-Bluepay20DailyReport-0.20
http://search.cpan.org/~cpkois/Bluepay-Bluepay20DailyReport-0.20/
----
Bluepay-Bluepay20Post-0.15
http://search.cpan.org/~cpkois/Bluepay-Bluepay20Post-0.15/
----
CGI-Uploader-2.90_02
http://search.cpan.org/~rsavage/CGI-Uploader-2.90_02/
Manage CGI uploads using an SQL database
----
Catalyst-Plugin-Session-Store-BerkeleyDB-0.01
http://search.cpan.org/~jrockway/Catalyst-Plugin-Session-Store-BerkeleyDB-0.01/
store sessions in a berkeleydb
----
CatalystX-CRUD-Model-RDBO-0.18
http://search.cpan.org/~karman/CatalystX-CRUD-Model-RDBO-0.18/
Rose::DB::Object CRUD
----
Continuity-0.997
http://search.cpan.org/~awwaiid/Continuity-0.997/
Abstract away statelessness of HTTP, for stateful Web applications
----
Crypt-RC4-XS-0.02
http://search.cpan.org/~oyama/Crypt-RC4-XS-0.02/
Perl implementation of the RC4 encryption algorithm
----
DBIx-Class-DeleteAction-1.02
http://search.cpan.org/~maros/DBIx-Class-DeleteAction-1.02/
Define delete triggers
----
DBIx-Compare-1.6
http://search.cpan.org/~cjones/DBIx-Compare-1.6/
Compare database content
----
DBIx-Compare-1.6b
http://search.cpan.org/~cjones/DBIx-Compare-1.6b/
Compare database content
----
Devel-Declare-0.003004
http://search.cpan.org/~flora/Devel-Declare-0.003004/
Adding keywords to perl, in perl
----
Dynamic-Loader-1.08
http://search.cpan.org/~alexmass/Dynamic-Loader-1.08/
call a script without to know where is his location.
----
Email-Abstract-3.001
http://search.cpan.org/~rjbs/Email-Abstract-3.001/
unified interface to mail representations
----
FreeBSD-Pkgs-FindUpdates-0.0.0
http://search.cpan.org/~vvelox/FreeBSD-Pkgs-FindUpdates-0.0.0/
Finds updates for FreeBSD pkgs by checking the ports index.
----
HTTP-Engine-0.0.20
http://search.cpan.org/~yappo/HTTP-Engine-0.0.20/
Web Server Gateway Interface and HTTP Server Engine Drivers (Yet Another Catalyst::Engine)
----
IPC-Open3-Utils-0.3
http://search.cpan.org/~dmuey/IPC-Open3-Utils-0.3/
Functions for facilitating some of the most common open3() uses
----
Lingua-Identify-0.20
http://search.cpan.org/~ambs/Lingua-Identify-0.20/
Language identification
----
Log-Log4perl-1.20
http://search.cpan.org/~mschilli/Log-Log4perl-1.20/
Log4j implementation for Perl
----
Log-Report-0.20
http://search.cpan.org/~markov/Log-Report-0.20/
report a problem, pluggable handlers and language support
----
Mac-Finder-DSStore-0.90
http://search.cpan.org/~wiml/Mac-Finder-DSStore-0.90/
----
Mail-Box-2.085
http://search.cpan.org/~markov/Mail-Box-2.085/
manage a mailbox, a folder with messages
----
Mail-Box-2.086
http://search.cpan.org/~markov/Mail-Box-2.086/
manage a mailbox, a folder with messages
----
Module-Build-0.30_01
http://search.cpan.org/~ewilhelm/Module-Build-0.30_01/
Build and install Perl modules
----
Module-Install-ExtraTests-0.006
http://search.cpan.org/~rjbs/Module-Install-ExtraTests-0.006/
contextual tests that the harness can ignore
----
Music-Chord-Note-0.0.4
http://search.cpan.org/~bayashi/Music-Chord-Note-0.0.4/
get Chord Tone List from Chord Name
----
Net-fonolo-1.2
http://search.cpan.org/~mpultz/Net-fonolo-1.2/
Perl interface to fonolo (http://fonolo.com/developer)
----
Omega-DP41-Data-Current-0.3
http://search.cpan.org/~kerr/Omega-DP41-Data-Current-0.3/
----
Omega-DP41-Data-Current-0.3.1
http://search.cpan.org/~kerr/Omega-DP41-Data-Current-0.3.1/
----
PDL-Graphics-PLplot-0.46
http://search.cpan.org/~dhunt/PDL-Graphics-PLplot-0.46/
Object-oriented interface from perl/PDL to the PLPLOT plotting library
----
POE-Component-SimpleDBI-1.23
http://search.cpan.org/~apocal/POE-Component-SimpleDBI-1.23/
Asynchronous non-blocking DBI calls in POE made simple
----
Parse-Eyapp-1.135
http://search.cpan.org/~casiano/Parse-Eyapp-1.135/
Extensions for Parse::Yapp
----
Parse-Stallion-0.50
http://search.cpan.org/~arthur/Parse-Stallion-0.50/
EBNF based regexp backtracking parser and tree evaluator.
----
Pod-Advent-0.13
http://search.cpan.org/~davidrw/Pod-Advent-0.13/
POD Formatter for The Perl Advent Calendar
----
Pod-Advent-0.14
http://search.cpan.org/~davidrw/Pod-Advent-0.14/
POD Formatter for The Perl Advent Calendar
----
RDF-Simple-0.403
http://search.cpan.org/~mthurn/RDF-Simple-0.403/
read and write RDF without complication
----
Rubyish-0.31
http://search.cpan.org/~gugod/Rubyish-0.31/
Perl programming, the rubyish way.
----
SWISH-Prog-0.23
http://search.cpan.org/~karman/SWISH-Prog-0.23/
information retrieval application framework
----
Squatting-On-HTTP-Engine-0.01
http://search.cpan.org/~beppu/Squatting-On-HTTP-Engine-0.01/
run Squatting apps on top of HTTP::Engine
----
Syntax-Highlight-Perl6-0.01
http://search.cpan.org/~azawawi/Syntax-Highlight-Perl6-0.01/
Perl 6 source code highlighter
----
SysAdmin-0.11
http://search.cpan.org/~marr/SysAdmin-0.11/
Parent class for SysAdmin wrapper modules.
----
Tee-0.13_51
http://search.cpan.org/~dagolden/Tee-0.13_51/
Pure Perl emulation of GNU tee
----
Template-Declare-Anon-0.03
http://search.cpan.org/~nuffin/Template-Declare-Anon-0.03/
Deprecated Anonymous Template::Declare templates
----
Term-Sprog-0.01b
http://search.cpan.org/~keichner/Term-Sprog-0.01b/
Perl extension for displaying a progress indicator on a terminal.
----
Term-Sprog-0.02
http://search.cpan.org/~keichner/Term-Sprog-0.02/
Perl extension for displaying a progress indicator on a terminal.
----
Term-Sprog-0.02b
http://search.cpan.org/~keichner/Term-Sprog-0.02b/
Perl extension for displaying a progress indicator on a terminal.
----
Term-Sprog-0.03
http://search.cpan.org/~keichner/Term-Sprog-0.03/
Perl extension for displaying a progress indicator on a terminal.
----
WWW-Translate-Apertium-0.06
http://search.cpan.org/~enell/WWW-Translate-Apertium-0.06/
Open source machine translation
----
WWW-Translate-Apertium-0.07
http://search.cpan.org/~enell/WWW-Translate-Apertium-0.07/
Open source machine translation
----
WWW-YourFileHost-0.05
http://search.cpan.org/~yusukebe/WWW-YourFileHost-0.05/
Get video informations from YourFileHost
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Fri, 12 Dec 2008 08:11:14 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <C0p0l.7330$W06.4743@flpi148.ffdc.sbc.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 12 Dec 2008 13:09:21 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Processing Multiple Large Files
Message-Id: <Xns9B7252F5C6E7Aasu1cornelledu@127.0.0.1>
"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in
news:Xns9B71C0CDC9E12asu1cornelledu@127.0.0.1:
> "friend.05@gmail.com" <hirenshah.05@gmail.com> wrote in news:5f1e2237-
> b3f6-409c-aa95-b7ba57955265@q26g2000prq.googlegroups.com:
>
>> I analyzing some netwokr log files. There are around 200-300 files
>> and each file has more than 2 million entries in it.
>>
>> Currently my script is reading each file line by line. So it will
>> take lot of time to process all the files.
>>
>> Is there any efficient way to do it?
>>
>> May be Multiprocessing, Multitasking ?
>
> Here is one way to do it using Parallel::Forkmanager.
>
...
> Not very impressive. Between no forking vs max 20 instances, time
> required to process was reduced by 20% with most of the gains coming
> from running 2. That probably has more to do with the implementation
> of fork on Windows than anything else.
>
> In fact, I should probably have used threads on Windows. Anyway, I'll
> boot into Linux and see if the returns there are greater.
Hmmm ... I tried it on ArchLinux using perl from the repository on the
exact same hardware as the Windows tests:
[sinan@archardy large]$ time perl process.pl 0
real 0m29.983s
user 0m29.848s
sys 0m0.073s
[sinan@archardy large]$ time perl process.pl 2
real 0m15.281s
user 0m29.865s
sys 0m0.077s
with no changes going to 4, 8, 16 or 20 max instances. Exact same
program and data on the same hardware, yet the no fork version was 40%
faster. Running it in a shell window in xfce4 versus at boot-up on the
console and running it in an ntfs filesystem versus ext3 file system did
not make any meaningful difference.
The wireless connection was up but inactive in all scenarios.
-- Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://www.rehabitation.com/clpmisc/
------------------------------
Date: Fri, 12 Dec 2008 07:02:43 -0800 (PST)
From: cartercc <cartercc@gmail.com>
Subject: Re: Processing Multiple Large Files
Message-Id: <8a75619e-57fa-4e82-bb03-8ce717ae3771@o4g2000pra.googlegroups.com>
On Dec 11, 3:27=A0pm, "friend...@gmail.com" <hirenshah...@gmail.com>
wrote:
> I analyzing some netwokr log files. There are around 200-300 files and
> each file has more than 2 million entries in it.
> Currently my script is reading each file line by line. So it will take
> lot of time to process all the files.
Your question is really about data. The fact that your data is
contained in files which have rows and columns is totally irrelevant.
You would have the same problem if all the data were contained in just
one file. If you have 200,000,000 items of data, you have that much
data, and there's absolutely nothing you can do about it.
> Is there any efficient way to do it?
This is a good question, and the answer is, 'Maybe.' If you want to
generate reports from the data, you might want to look into putting in
into a database and writing queries against the database. That's what
companies like Wal-mart, Amazon.com, and eBay do. Write a script that
runs as a cron job at 2:00 am and reads all the data into a database.
Then write another script that queries the database at 4:00 am and
spits out the reports you want.
>
> May be Multiprocessing, Multitasking ?
If you are using an Intel-like processor, it multi processes, anyway.
There are only two ways to increase speed: increase the clocks of the
processor or increase the number of processors. With respect to the
latter, take a look at Erlang. I'd bet a lot of money that you could
write an Erlang script that would increase the speed by several orders
of magnitude. (On my machine, Erlang generates about 60,000 threads in
sevaral milliseconds, and I have an old, slow machine.)
CC
------------------------------
Date: Fri, 12 Dec 2008 11:11:14 +0000
From: Tony Mc <afmcc@btinternet.com>
Subject: Re: The single biggest STUPIDITY in Perl ...
Message-Id: <egh4k4ptm253b412sm668b9hs6lo3pgh37@4ax.com>
On Thu, 11 Dec 2008 12:16:21 -0800 (PST), jps <jpsweden@gmail.com>
wrote:
> mostly for what it was actually designed and where it truly *SHINES*
> -- i.e. "extraction and reports".
> How so many propellerheads came to the conclusion that Perl was a good
> tool for things like serving web-contents,
> is certainly beyond me -
Serving web contents *is* a kind of extraction and reporting,
especially if the web page contents depend on the state of a database.
In my experience, perl works fine for this purpose, where I use the
CGI::Application::* modules.
Tony
------------------------------
Date: Fri, 12 Dec 2008 07:57:49 -0800 (PST)
From: cartercc <cartercc@gmail.com>
Subject: Re: The single biggest STUPIDITY in Perl ...
Message-Id: <15fbdfe0-1074-45f4-9590-fbea12c4eb2c@s16g2000vbp.googlegroups.com>
On Dec 11, 3:27=A0pm, Tim Greer <t...@burlyhost.com> wrote:
> I still think it is. =A0After all, embedding Perl code in the web page an=
d
> web server process (not spawning a new process and creating the
> overhead of CGI -- which is CGI as the issue and not Perl) is why PHP
> came about in the first place. =A0I don't believe it's a terrible thing,
> and the difference is really about what content you want it to output
> and in what manner. =A0There are templates, mod_perl and Mason and a lot
> of things that put it on par for embedding and make it just as easy,
> but I don't believe a CGI script is the worst plan for web content
> anyway in most cases.
I've used both embedded technologies (PHP, JSP, ASP, etc) and
technologies that emit HTML (like traditional CGI). I strongly prefer
the latter. If you embed logic in HTML, you are mixing data, logic,
and document markup. If you use the Perl equivalent of servlets, you
separate logic and presentation.
Data should drive logic, and logic should drive presentation. As to
traditional CGI, mod_perl solves those kinds of problems.
As a general rule, I believe that The Best methodology for building
large web apps is to build a wall of separation between the data,
logic, and interface, using your logic components to control both the
data (and access to data) and the interface. Mixing interface with
logic isn't a good idea, IMO.
CC
------------------------------
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 2051
***************************************