[27908] in Perl-Users-Digest
Perl-Users Digest, Issue: 9272 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 9 06:05:50 2006
Date: Fri, 9 Jun 2006 03:05:04 -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 Fri, 9 Jun 2006 Volume: 10 Number: 9272
Today's topics:
Re: FAQ 2.12 Which magazines have Perl content? <eflorac@imaginet.fr>
Re: HOST - dreamhost.com / Liberality (Hosting, Basic R <jurgenex@hotmail.com>
Inverse Sequence Matching bilaribilari@yahoo.com
Re: Inverse Sequence Matching <David.Squire@no.spam.from.here.au>
Re: m///x and slashes in comments: bug or feature? <ro.naldfi.scher@gmail.com>
new CPAN modules on Fri Jun 9 2006 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Returning the first n elements of a list <ro.naldfi.scher@gmail.com>
Re: split a big program into multiple files <josef.moellers@fujitsu-siemens.com>
Re: split a big program into multiple files <filippo2991@virgilio.it>
Re: split a big program into multiple files <josef.moellers@fujitsu-siemens.com>
Re: split a big program into multiple files <filippo2991@virgilio.it>
Re: split a big program into multiple files <josef.moellers@fujitsu-siemens.com>
Still error coming when connecting to database using Wi <madan.narra@gmail.com>
What is Expressiveness in a Computer Language <xah@xahlee.org>
Why the speed of reading data from ramdisk is slower th <sonet.all@msa.hinet.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 09 Jun 2006 09:23:10 +0200
From: Emmanuel Florac <eflorac@imaginet.fr>
Subject: Re: FAQ 2.12 Which magazines have Perl content?
Message-Id: <pan.2006.06.09.07.23.10.610486@imaginet.fr>
Le Thu, 08 Jun 2006 18:03:02 -0700, PerlFAQ Server a écrit :
>
> 2.12: Which magazines have Perl content?
This one needs to be updated. The Perl Journal is dead, and the Perl
Review is entirely devoted to perl.
--
Ne pas savoir de quoi on parle est un avantage dont il ne faut pas
abuser.
R.Debray
------------------------------
Date: Fri, 09 Jun 2006 06:25:29 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: HOST - dreamhost.com / Liberality (Hosting, Basic Requirement)
Message-Id: <tv8ig.18530$9c7.17416@trnddc06>
Ilias Lazaridis wrote:
> crossposted to 5 groups, which are affected by this case.
>
[some random ramblings about a troll being silenced for the moment]
And your article has exactly what relationship to Perl?
*PLONK*
jue
------------------------------
Date: 9 Jun 2006 02:06:30 -0700
From: bilaribilari@yahoo.com
Subject: Inverse Sequence Matching
Message-Id: <1149843990.001373.196650@i40g2000cwc.googlegroups.com>
Hello,
I have the following text:
<SP>http://poplet.com/laseaer<SP><SP>some:text with colon<SP>
I am trying to come up with a regular expression that
1. Matches anything between <SP> tags, and
2. Does NOT match if the text contains ://
I.e. the regex should match 'some:text with colon' but NOT the url.
I have tried a lot of possiblities, but am not able to get the result I
require. Please help me crack this one. It must be pretty trivial for
many people.
Thanks in advance.
Best regards,
B.
------------------------------
Date: Fri, 09 Jun 2006 10:33:26 +0100
From: David Squire <David.Squire@no.spam.from.here.au>
Subject: Re: Inverse Sequence Matching
Message-Id: <e6bf96$jao$1@news.ox.ac.uk>
bilaribilari@yahoo.com wrote:
> Hello,
> I have the following text:
>
> <SP>http://poplet.com/laseaer<SP><SP>some:text with colon<SP>
>
> I am trying to come up with a regular expression that
> 1. Matches anything between <SP> tags, and
> 2. Does NOT match if the text contains ://
>
> I.e. the regex should match 'some:text with colon' but NOT the url.
>
Hmmm. This does not look like a very stable mark-up, unless there are
constraints you have not mentioned. The code below seems to do what you
want, but see the caveats embedded in the example.
----
#!/usr/bin/perl
use strict;
use warnings;
while (<DATA>) {
my @Matches = m{<SP>(?!http://|<SP>)(.*?)<SP>}g;
print "$_\n" for @Matches;
}
__DATA__
<SP>http://poplet.com/laseaer<SP><SP>some:text with colon<SP>
what if there is leading
text?<SP>http://poplet.com/laseaer<SP><SP>some:text with colon<SP>
<SP>Are the beginning and end <SP> tags really
identical?<SP><SP><SP><SP>I can imagine that causing problems http://<SP>
----
Output:
some:text with colon
some:text with colon
Are the beginning and end
Regards,
DS
------------------------------
Date: 9 Jun 2006 01:16:48 -0700
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: Re: m///x and slashes in comments: bug or feature?
Message-Id: <1149841008.257203.320740@c74g2000cwc.googlegroups.com>
Ben Morrow schrieb:
> Quoth Mirco Wahab <peace.is.our.profession@gmx.de>:
> > "dummy" =~ qr{
> > first|
> > second| # this comment has a/slash
> > third
> > }x and print 1;
>
> You don't need to use qr//, you can just use m//:
>
> "dummy" =~ m{...}x and print 1;
But in any case, though this would make a slash possible in
the comment, it would make a single closing brace in a
comment spoil the whole code:
"dummy" =~ m{
first|
second| # this comment has a brace}
third
}x and print 1;
I understand the parsing problem. The crucial point to observe here is
that
within m//x, comments can not be as arbitrary as they would be outside
a regexp. Thank you for enlighting me.
Ronald
------------------------------
Date: Fri, 9 Jun 2006 04:42:09 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Jun 9 2006
Message-Id: <J0Kt29.1p2w@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.
Chart-Clicker-0.9.6
http://search.cpan.org/~gphat/Chart-Clicker-0.9.6/
Powerful, extensible charting.
----
Class-Accessor-Class-0.500
http://search.cpan.org/~rjbs/Class-Accessor-Class-0.500/
simple class variable accessors
----
Email-Valid-0.170
http://search.cpan.org/~rjbs/Email-Valid-0.170/
Check validity of Internet email addresses
----
Text-MeCab-0.07
http://search.cpan.org/~dmaki/Text-MeCab-0.07/
Alternate Interface To libmecab
----
version-0.64
http://search.cpan.org/~jpeacock/version-0.64/
Perl extension for Version Objects
----
File-LockDir-0.01
http://search.cpan.org/~mcmahon/File-LockDir-0.01/
basic filename-level lock utility
----
App-SimpleScan-1.08
http://search.cpan.org/~mcmahon/App-SimpleScan-1.08/
simple_scan's core code
----
Log-Dispatch-Spread-0.9
http://search.cpan.org/~brthomas/Log-Dispatch-Spread-0.9/
Perl extension for logging Log::Dispatch messages to a Spread cluster
----
OpenGuides-0.54_02
http://search.cpan.org/~dom/OpenGuides-0.54_02/
A complete web application for managing a collaboratively-written guide to a city or town.
----
CGI-Ex-2.02
http://search.cpan.org/~rhandom/CGI-Ex-2.02/
CGI utility suite - makes powerful application writing fun and easy
----
Data-Hive-0.02
http://search.cpan.org/~hdp/Data-Hive-0.02/
convenient access to hierarchical data
----
Bundle-HTMLWikiConverter-0.04
http://search.cpan.org/~diberri/Bundle-HTMLWikiConverter-0.04/
A bundle to install HTML::WikiConverter and all its dialects
----
HTML-WikiConverter-0.55
http://search.cpan.org/~diberri/HTML-WikiConverter-0.55/
Convert HTML to wiki markup
----
Finance-QuoteHist-1.09
http://search.cpan.org/~msisk/Finance-QuoteHist-1.09/
Perl module for fetching historical stock quotes.
----
SVN-Pusher-0.03001
http://search.cpan.org/~shlomif/SVN-Pusher-0.03001/
Propagate changesets between two different svn repositories.
----
HTML-TableExtract-2.09
http://search.cpan.org/~msisk/HTML-TableExtract-2.09/
Perl module for extracting the content contained in tables within an HTML document, either as text or encoded element trees.
----
Test-Harness-2.62
http://search.cpan.org/~petdance/Test-Harness-2.62/
Run Perl standard test scripts with statistics
----
Xmldoom-0.0.12
http://search.cpan.org/~dsnopek/Xmldoom-0.0.12/
The XML Document Object-Oriented Model
----
DBIx-Romani-0.0.12
http://search.cpan.org/~dsnopek/DBIx-Romani-0.0.12/
----
Term-ShellUI-0.85
http://search.cpan.org/~bronson/Term-ShellUI-0.85/
A fully-featured shell-like command line environment
----
Solaris-Lgrp-0.1.4
http://search.cpan.org/~akolb/Solaris-Lgrp-0.1.4/
Perl interface to Solaris liblgrp(3LIB) library.
----
Games-Cards-Bridge-Contract-0.02
http://search.cpan.org/~davidrw/Games-Cards-Bridge-Contract-0.02/
Bridge (card game) contract and scoring class
----
Class-DBI-AutoIncrement-Simple-0.02
http://search.cpan.org/~davidrw/Class-DBI-AutoIncrement-Simple-0.02/
Add autoincrementing to a Class::DBI subclass
----
Verilog-Perl-2.351
http://search.cpan.org/~wsnyder/Verilog-Perl-2.351/
----
Net-Delicious-0.99
http://search.cpan.org/~ascope/Net-Delicious-0.99/
OOP for the del.icio.us API
----
Cache-Memcached-Tie-0.02
http://search.cpan.org/~gugu/Cache-Memcached-Tie-0.02/
Using Cache::Memcached as hash
----
Data-Report-0.05
http://search.cpan.org/~jv/Data-Report-0.05/
Framework for flexible reporting
----
Data-Report-0.04
http://search.cpan.org/~jv/Data-Report-0.04/
Framework for flexible reporting
----
Nagios-Plugin-0.10
http://search.cpan.org/~tonvoon/Nagios-Plugin-0.10/
Object oriented helper routines for your Nagios plugin
----
Class-DBI-AutoIncrement-0.05
http://search.cpan.org/~erwan/Class-DBI-AutoIncrement-0.05/
Emulate auto-incrementing columns on Class::DBI subclasses
----
HTTP-SimpleLinkChecker-1.10
http://search.cpan.org/~bdfoy/HTTP-SimpleLinkChecker-1.10/
Check the HTTP response code for a link
----
HTTP-Size-1.11
http://search.cpan.org/~bdfoy/HTTP-Size-1.11/
Get the byte size of an internet resource
----
Mac-Errors-1.12
http://search.cpan.org/~bdfoy/Mac-Errors-1.12/
constants for Mac error codes
----
Mac-Path-Util-0.23
http://search.cpan.org/~bdfoy/Mac-Path-Util-0.23/
convert between darwin and Mac paths
----
Convert-Bencode_XS-0.05
http://search.cpan.org/~giulienk/Convert-Bencode_XS-0.05/
Faster conversions to/from Bencode format
----
Module-Release-1.10
http://search.cpan.org/~bdfoy/Module-Release-1.10/
Automate software releases
----
Polyglot-0.12
http://search.cpan.org/~bdfoy/Polyglot-0.12/
a little language interpreter
----
Object-Iterate-1.09
http://search.cpan.org/~bdfoy/Object-Iterate-1.09/
iterators for objects that know the next element
----
WWW-Babelfish-0.15
http://search.cpan.org/~durist/WWW-Babelfish-0.15/
Perl extension for translation via Babelfish or Google
----
CSS-Squish-0.02
http://search.cpan.org/~tsibley/CSS-Squish-0.02/
Compact many CSS files into one big file
----
ack-1.20
http://search.cpan.org/~petdance/ack-1.20/
grep-like text finder for large trees of text
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.
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: 09 Jun 2006 07:22:25 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <448921b0$0$50704$ae4e5890@news.nationwide.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.5 $)
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://mail.augustmail.com/~tadmc/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
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: 9 Jun 2006 01:05:19 -0700
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: Re: Returning the first n elements of a list
Message-Id: <1149840318.960753.151540@u72g2000cwu.googlegroups.com>
Ted Zlatanov schrieb:
> On 7 Jun 2006, ro.naldfi.scher@gmail.com wrote:
>
> > Assume that I have a function f expecting a list of arguments, and
> > an expression E returning a list. Of course one way to call this
> > function is just: f(E)
> >
> > Example: f(`ls -l foo`);
> >
> > Now suppose that I want to pass to the function only the first $n
> > elements of E.
>
> You should consider why you only need to pass the first few elements.
> It complicates things, as you see. Why not just
>
> my @results = `command`;
> f(\@results); # passes an array reference
The problem originated from the following situation:
I do a qx(COMMAND) and want to print the first $N lines of the command
only.
Note that the COMMAND may output any number of lines, even zero.
Of course I could have done a
print (qx(COMMAND|head -n $N));
or in this case a
system(COMMAND|head -n $N)
but for various reasons I didn't want to use system and I wanted to do
the "head -n" part within Perl, and without using an auxiliary
variable.
This made me think about the problem in general, how to obtain
the first n elements of a list or of an array.
Thanks to everyone here for giving me good ideas and insights!
Ronald
------------------------------
Date: Fri, 09 Jun 2006 09:19:39 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: split a big program into multiple files
Message-Id: <e6b7if$ame$1@nntp.fujitsu-siemens.com>
filippo wrote:
> ok John and Xho, you convinced me :-)
>=20
> In fact I have just a couple of global variables so I can easily
> redesign my subroutines to manage these as arguments.
>=20
> Which is the best method to have a C-like splitting method?
What on earth is a "C-like splitting method"?
In C (and in Perl, and in Modula2, and in any other language that allows =
to spread source code over more than a single source file), you split by =
grouping things that belong together.
When using #include, you put only definitions (types, structures,=20
function prototypes, constants) into the files that are included.
Otherwise you put code that belongs together into a C source file and=20
compile each source file independently into object files which are then=20
linked together into an executable. The .h-files included provide some=20
glue between these source files.
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 9 Jun 2006 00:44:20 -0700
From: "filippo" <filippo2991@virgilio.it>
Subject: Re: split a big program into multiple files
Message-Id: <1149839060.284139.299840@f6g2000cwb.googlegroups.com>
Josef Moellers ha scritto:
ok, you're right.
My application is a Tk GUI based perl program to manage a touristic
campsite. I have some windows:
Main Menu
createGroup
manageGroup
Bill
others (tools)
and I want to split such a big code (~10.000rows) into separate files.
I have no global variables (no more), just subroutines: more or less a
main subroutine plus a couple of service for each windows. Which is the
'best' method to split my program?
Thanks,
Filippo
------------------------------
Date: Fri, 09 Jun 2006 10:09:57 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: split a big program into multiple files
Message-Id: <e6baha$kuj$1@nntp.fujitsu-siemens.com>
filippo wrote:
> Josef Moellers ha scritto:
>=20
> ok, you're right.
>=20
> My application is a Tk GUI based perl program to manage a touristic
> campsite. I have some windows:
>=20
> Main Menu
> createGroup
> manageGroup
> Bill
> others (tools)
>=20
> and I want to split such a big code (~10.000rows) into separate files.
> I have no global variables (no more), just subroutines: more or less a
> main subroutine plus a couple of service for each windows. Which is the=
> 'best' method to split my program?
It's indeed probably the most complicated task: to decide which=20
functions should be grouped together.
I'm not sure if there is a clean-cut approach to do this.
Maybe you could group according to "window"?
Josef
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 9 Jun 2006 02:15:29 -0700
From: "filippo" <filippo2991@virgilio.it>
Subject: Re: split a big program into multiple files
Message-Id: <1149844529.392422.218280@h76g2000cwa.googlegroups.com>
I know more or less how to split. I'd like to know the best way to
import. I know the 'do' way, are there problems to do this using do?
Thanks,
Filippo
------------------------------
Date: Fri, 09 Jun 2006 11:24:22 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: split a big program into multiple files
Message-Id: <e6betm$4gu$1@nntp.fujitsu-siemens.com>
filippo wrote:
> I know more or less how to split. I'd like to know the best way to
> import. I know the 'do' way, are there problems to do this using do?
Oh, sorry for the misunderstanding.
As for the technicality: I really don't know what's the best way to do.=20
I usually use "use" which is based on "require" which is based on "do".
Hopefully others know better.
Josef
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 8 Jun 2006 21:22:25 -0700
From: "madan" <madan.narra@gmail.com>
Subject: Still error coming when connecting to database using Win32::ODBC
Message-Id: <1149826945.151183.320050@f6g2000cwb.googlegroups.com>
The following error is coming only when i use Win32::ODBC module..
when i removed it the program is working fine..I checked the dsn,user
name and password all are right...
the following error is shown on the browser..
##########################################################################
Undefined subroutine &Scalar::Util::blessed called at
W:/usr/lib/overload.pm line 89.
Compilation failed in require at W:/usr/lib/Config.pm line 70.
Compilation failed in require at W:/usr/site/lib/Win32/ODBC.pm line 27.
Compilation failed in require at W:/cgi-bin/dbtest.pl line 8.
BEGIN failed--compilation aborted at W:/cgi-bin/dbtest.pl line 8.
line 8 in the pgm is :: "use Win32::ODBC;"
##########################################################################
i am new to perl...so i dont have enough stuff to write a good
syntax...
thanks in advance
------------------------------
Date: 8 Jun 2006 22:04:47 -0700
From: "Xah Lee" <xah@xahlee.org>
Subject: What is Expressiveness in a Computer Language
Message-Id: <1149829487.457604.17510@i40g2000cwc.googlegroups.com>
in March, i posted a essay =E2=80=9CWhat is Expressiveness in a Computer
Language=E2=80=9D, archived at:
http://xahlee.org/perl-python/what_is_expresiveness.html
I was informed then that there is a academic paper written on this
subject.
On the Expressive Power of Programming Languages, by Matthias
Felleisen, 1990.
http://www.ccs.neu.edu/home/cobbe/pl-seminar-jr/notes/2003-sep-26/expressiv=
e-slides.pdf
Has anyone read this paper? And, would anyone be interested in giving a
summary?
thanks.
Xah
xah@xahlee.org
=E2=88=91 http://xahlee.org/
------------------------------
Date: Fri, 9 Jun 2006 15:54:09 +0800
From: "sonet" <sonet.all@msa.hinet.net>
Subject: Why the speed of reading data from ramdisk is slower than harddisk?
Message-Id: <e6ba52$6b6$1@netnews.hinet.net>
/dev/sda2 49594228 1373972 45660300 3% /usr/local
/dev/ram0 96828 11976 84852 13%
/usr/local/Portal/cache
/usr/local/Portal/tesing (real filesystem)
/usr/local/Portal/cache/testing (ramdisk)
The file size is about 6M.
#--------------------------result-------------------------------
open file on ramdisk:6.38961791992188e-05
write file on ramdisk:0.0180280208587646
close file on ramdisk:3.91006469726562e-05
read data on ramdisk:0.178893089294434
=====================================
open file on disk:0.000104904174804688
write file on disk:0.0201010704040527
close file on disk:4.50611114501953e-05
read data on disk:0.0465281009674072
#---------------------------code--------------------------------
#!/usr/bin/perl
use strict;
use warnings;
use Time::HiRes();
my $t1=Time::HiRes::gettimeofday;
open(my $HH,">/usr/local/Portal/cache/testing");
print "open file on ramdisk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
my $str='';
for (my $i=0;$i<=1000000;$i++){
$str.=$i;
}
$t1=Time::HiRes::gettimeofday;
print $HH $str;
print "write file on ramdisk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$t1=Time::HiRes::gettimeofday;
close($HH);
print "close file on ramdisk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$t1=Time::HiRes::gettimeofday;
open($HH,"/usr/local/Portal/cache/testing");
my $a=join('',<$HH>);
close($HH);
print "read data on ramdisk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$a='';
print "=====================================\n";
$t1=Time::HiRes::gettimeofday;
open($HH,">/usr/local/Portal/testing");
print "open file on disk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$str='';
for (my $i=0;$i<=1000000;$i++){
$str.=$i;
}
$t1=Time::HiRes::gettimeofday;
print $HH $str;
print "write file on disk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$t1=Time::HiRes::gettimeofday;
close($HH);
print "close file on disk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$t1=Time::HiRes::gettimeofday;
open($HH,"/usr/local/Portal/testing");
$a=join('',<$HH>);
close($HH);
print "read data on disk:" . (Time::HiRes::gettimeofday -$t1) . "\n";
$a='';
------------------------------
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 V10 Issue 9272
***************************************
