[23272] in Perl-Users-Digest
Perl-Users Digest, Issue: 5492 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 12 06:09:51 2003
Date: Fri, 12 Sep 2003 03:05:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 12 Sep 2003 Volume: 10 Number: 5492
Today's topics:
Re: "between" function equivalent in Perl? (Tad McClellan)
Re: "between" function equivalent in Perl? (Tad McClellan)
Re: caturing ftp standard output while using system() a <me@privacy.net>
Re: IO:Select - what did I do wrong? (Heinrich Mislik)
Re: not able to access a URL with LWP::UserAgent. (Tad McClellan)
parenp process controlling child (Monika Talwar)
Re: parenp process controlling child (Anno Siegel)
Re: Perl DBMS <jwillmore@cyberia.com>
Re: Perl DBMS <noreply@gunnar.cc>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing a hash of hashes using an array for the he (Anno Siegel)
Re: Speeding up LWP::Simple <me@privacy.net>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 11 Sep 2003 23:15:10 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: "between" function equivalent in Perl?
Message-Id: <slrnbm2i2e.8h1.tadmc@magna.augustmail.com>
Alexandra <sagittaur@ftml.net> wrote:
> Would it be accurate to
No.
> assume that most Perl expressions/functions will evaluate "at large" and
They have 2 different behaviors.
If called in a scalar context, they do one thing.
If called in a list context, they do something else.
They are often "related" things, but that is convention rather
than requirement. They could do wildly different unconnected
things, such as send an email in scalar context and return
the contents of a database table in list context.
It is up to the author of the function to decide what it is that
their function will do in each context. (So you cannot use the
function intelligently without reading the functions' docs.)
You can write your own context-sensitive subroutines too. Here's
one that outputs what context it was called in:
---------------------------------------------
#!/usr/bin/perl
use strict;
use warnings;
foreach ( context() ) {} # list
$_ = 2 + context(); # scalar
context(); # void
sub context {
my $context = wantarray();
if ( $context )
{ print "list context\n" }
elsif ( defined $context )
{ print "scalar context\n" }
else
{ print "void context\n" }
}
---------------------------------------------
> then look to "format" (for lack of a better term) the return value depending
> on the context of the assignment variable or operand?
^^^^^^^^^^
You should have left that word out. Context matters for operators
other than assignment as well.
> I read somewhere that you do not have to declare variables in Perl, you just
> use them.
Right (but not recommended, other than in one-liners).
> Getting a grasp on contexts, even a tiny one, explains now how
> that can work.
No it doesn't.
Context has nothing whatsoever to do with either of Perl's two
systems of variables.
If you can explain why you think context relates to declaring (or not)
variables, then perhaps we can help fix the misunderstanding.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 11 Sep 2003 23:18:49 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: "between" function equivalent in Perl?
Message-Id: <slrnbm2i99.8h1.tadmc@magna.augustmail.com>
Alexandra <sagittaur@ftml.net> wrote:
> I've since discovered the count
> function.
What is the count function?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 12 Sep 2003 19:21:53 +1200
From: "Tintin" <me@privacy.net>
Subject: Re: caturing ftp standard output while using system() and cron
Message-Id: <bjrs45$l5mgs$1@ID-172104.news.uni-berlin.de>
"Dave Saville" <dave.nospam@ntlworld.com> wrote in message
news:qnirfnivyyragyjbeyqpbz.hl2m0um.pminews@text.news.ntlworld.com...
> On Thu, 11 Sep 2003 21:53:51 +0530, Thens wrote:
>
> >On 11 Sep 2003 09:17:31 -0700
> >mrtortoise@yahoo.com (Nathan Pryor) wrote:
> >
> ># I need to capture all standard output of an ftp session that is run
> ># inside a perl program. Short example:
> >#
> ># #!/usr/bin/perl
> ># system("ftp -i ftp.gnu.org > results");
> >
> > Why dont you use Net::FTP and save yourself the trouble of Portability
> >and other issues.
> >
> > The thumb rule is use perl modules wherever you can.
>
> Assuming you know that there *is* one :-)
Hence the reason everyone uses http://search.cpan.org/
------------------------------
Date: 12 Sep 2003 09:26:06 GMT
From: Heinrich.Mislik@univie.ac.at (Heinrich Mislik)
Subject: Re: IO:Select - what did I do wrong?
Message-Id: <3f619128$0$18038$3b214f66@usenet.univie.ac.at>
In article <0d58b.19738$Os1.159146@news.easynews.com>, dodgynewsgroups@ewildgoose.demon.co.uk says...
>> : Anything else I should look at...?
>>
>> Install an operating system? :-) :-) :-)
>
>Yeah, fair enough....
>
>...It's going to be used by other people though, and the spec indicates MS
>windows....
Try cygwin. http://www.cygwin.com/
It's perl port runs fine with your test program.
--
Heinrich Mislik
Zentraler Informatikdienst der Universitaet Wien
A-1010 Wien, Universitaetsstrasse 7
Tel.: (+43 1) 4277-14056, Fax: (+43 1) 4277-9140
------------------------------
Date: Thu, 11 Sep 2003 23:21:45 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: not able to access a URL with LWP::UserAgent.
Message-Id: <slrnbm2iep.8h1.tadmc@magna.augustmail.com>
ko <kuujinbo@hotmail.com> wrote:
> danglesocket <danglesocket@no_spam> wrote in message news:<3f60cda7@shknews01>...
>> Rather than responding with a half assed answer that proves that you didn't
>> read the question and
>> tries to make me look like an idiot, either don't respond or offer somthing
>> more 'insightful'.
>
> Whoa, don't take things so personally
I plonked him when I saw his followup.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 11 Sep 2003 23:06:15 -0700
From: monikatalwar@hotmail.com (Monika Talwar)
Subject: parenp process controlling child
Message-Id: <e71b773.0309112206.67ad804a@posting.google.com>
How can parent process control a child??
I tried to kill the child, but the code didn;t worked to my
expectation.
Actually i wrote the following code -
# fork first child
if(defined($pid= fork))
{
print "1) pare $pid \n\n";
if($pid) ## If parent process then fork another child to start
timer
{ # fork new child
my $child_pid = fork;
# if parent process then wait for one of the child to terminate
if($child_pid)
{ # wait for children
my $terminated_id = wait;
# kill the still active child
if($terminated_id == $pid)
{ kill 9, $child_pid; }
else
{ kill 9, $pid ; }
}
else ## child that start the timer
{
print "2 start child $child_pid \n";
my ($luser_time,$lsys_time,$lcu_time,$lcs_time) = times;
LOOP_ON_TIMER :
print "\nLOOOOOOOP
($luser_time,$lsys_time,$lcu_time,$lcs_time)\n\n";
($luser_time,$lsys_time,$lcu_time,$lcs_time) = times;
goto LOOP_ON_TIMER if ($luser_time <= 2);
print "\t\t 2) child $pid exiting\n\n";
}
}
else # if first child, then fire the test case
{ print "1 start child $pid";
&run_test_case($i);
$flag =1;
}
}
Here parent forks two childeren,- One childeren is suppose to simulate
some system task ..
another child works as watch dog.
bothchilderen and paren should terminate once any of the child
terminates....
Can anyone suggest me better way to implement this ??
Thanks in advance ...
------------------------------
Date: 12 Sep 2003 09:04:26 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: parenp process controlling child
Message-Id: <bjs26q$j04$1@mamenchi.zrz.TU-Berlin.DE>
Monika Talwar <monikatalwar@hotmail.com> wrote in comp.lang.perl.misc:
> How can parent process control a child??
> I tried to kill the child, but the code didn;t worked to my
> expectation.
>
> Actually i wrote the following code -
>
> # fork first child
> if(defined($pid= fork))
> {
> print "1) pare $pid \n\n";
> if($pid) ## If parent process then fork another child to start
> timer
> { # fork new child
> my $child_pid = fork;
>
> # if parent process then wait for one of the child to terminate
> if($child_pid)
> { # wait for children
> my $terminated_id = wait;
>
> # kill the still active child
> if($terminated_id == $pid)
> { kill 9, $child_pid; }
> else
> { kill 9, $pid ; }
> }
Signal 9 is a little radical. It should only be used when a process
can't be killed by other means. I'd use a TERM signal.
> else ## child that start the timer
> {
> print "2 start child $child_pid \n";
> my ($luser_time,$lsys_time,$lcu_time,$lcs_time) = times;
>
> LOOP_ON_TIMER :
> print "\nLOOOOOOOP
> ($luser_time,$lsys_time,$lcu_time,$lcs_time)\n\n";
> ($luser_time,$lsys_time,$lcu_time,$lcs_time) = times;
>
> goto LOOP_ON_TIMER if ($luser_time <= 2);
> print "\t\t 2) child $pid exiting\n\n";
> }
> }
I don't think this loop times what you want to time. You are waiting
for this child process to accumulate two seconds of CPU time. Depending
on system load, this could take any amount of real time from two seconds
upwards. I expect you actually want to wait for two seconds real time.
Also, what you have there is a busy loop -- the process will continuously
be actively querying its CPU time and produce system load.
To repair both, use the sleep() command (see perldoc -f sleep).
> else # if first child, then fire the test case
> { print "1 start child $pid";
> &run_test_case($i);
> $flag =1;
>
> }
> }
>
> Here parent forks two childeren,- One childeren is suppose to simulate
> some system task ..
> another child works as watch dog.
You don't need a separate process to establish a time limit for a
process. Simply set an alarm timer (perldoc -f alarm). It will
kill your process after a set time.
If you need to do things after the alarm timer fires, there is
"perldoc -q 'slow event'" which shows how to catch the timer
signal.
> bothchilderen and paren should terminate once any of the child
> terminates....
>
> Can anyone suggest me better way to implement this ??
You don't need a separate process for the timeout. Set an alarm timer
in the working child process. Your use of "wait" to let the parent die
with the kid looks fine (I didn't run your progeam). It will be
simplified when there is only one process to wait for.
Anno
------------------------------
Date: Fri, 12 Sep 2003 05:49:11 GMT
From: James Willmore <jwillmore@cyberia.com>
Subject: Re: Perl DBMS
Message-Id: <20030912014919.6cc1b82e.jwillmore@cyberia.com>
On Thu, 11 Sep 2003 22:22:33 +0100
"Dave" <dave334234@inter.com> wrote:
<snip>
> Does anyone know what the problem is. I can post a sample database
> if required.
No, but code would be helpful :)
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
[Sir Stafford Cripps] has all the virtues I dislike and none of
the vices I admire. -- Winston Churchill
------------------------------
Date: Fri, 12 Sep 2003 09:06:17 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Perl DBMS
Message-Id: <bjrs0u$n0sbu$1@ID-184292.news.uni-berlin.de>
Dave wrote:
> I have a ikonboard messageboard ( which is written in perl), and I
> have all the databases saved locally.
>
> However they are in a *.db, *.dnt.db format, and i cannot access
> them via the standard dbmopen(%hash, $database, 0666).
>
> It simply creates a new file instead of accessing the current one.
>
> I had a suspicion that the version of dbm on the server ( ie the
> one that created the databases at the start) is a diffenent on to
> the one on my windows machine.
Are you sure they are DBM files? Or can they be plain text files that
happen to have .db file extentions? (Have you tried to open one of
them with e.g. Notepad?)
If that doesn't help, you'd better do as James suggested and post some
code, such as a code fragment that creates or read the databases.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 12 Sep 2003 02:22:08 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <uwadneJfT6a96fyiXTWJjQ@august.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.4 $)
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.
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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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: 12 Sep 2003 08:31:01 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Printing a hash of hashes using an array for the headings and getting the columns to line up
Message-Id: <bjs085$g9i$1@mamenchi.zrz.TU-Berlin.DE>
David K. Wall <usenet@dwall.fastmail.fm> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
>
> [regarding Text::Table]
>
> > In fact there's too little user control over alignment in more respects,
> > title-to-body alignment is just one of them. It will be the first thing
> > to fix if there is another release, but I'm not yet sure how to do it.
> >
> > The problem isn't that these features are hard to implement, but how
> > to squeeze them into the user interface, which isn't exactly a beauty
> > to begin with. In fact, that's why I left them out in the first place,
> > that, and that I'd have to describe them all. I thought I'd get away
> > with it, but you're not the first to complain.
>
> I haven't examined the internals closely, so I may be way off-base here, but
> since it already allows users to define columns with hashes, wouldn't that be
> the obvious place to add new features for column formats?
That is very probably what will happen.
> you're looking at far more features than I have in mind, so I'll shut up
> before I embarrass myself *too* much. :-)
I'm also playing with a more radical redesign where table columns would
become independent objects, but I think I'll go for a quick fix.
Anno
------------------------------
Date: Fri, 12 Sep 2003 19:16:07 +1200
From: "Tintin" <me@privacy.net>
Subject: Re: Speeding up LWP::Simple
Message-Id: <bjrrpa$lesdf$1@ID-172104.news.uni-berlin.de>
"Trent Curry" <tcurrey@no.no.no.i.said.no> wrote in message
news:bjqm2a$gt4$1@news.astound.net...
> Tintin wrote:
> > "John Bokma" <postmaster@castleamber.com> wrote in message
> > news:1063246517.512524@halkan.kabelfoon.nl...
> >> I recently read a mail I wrote, complaining like mad about 5 or 6
> >> spam mails a day... those where the days (1997). I receive now 200+
> >> unwanted mails a day :-(. Yet I never going as far as changing my
> >> email address or munging the ones in the headers.
> >
> > Time for you to use http://www.spamassassin.org/
> >
> > Written in Perl of course :-)
>
> I had recently read an article (somewhere in groups.google.com) claiming
> that, while it cna block some spam, in reality, it will not block
> everything and many spams cna get through it. Though nice to know these
> solutions are being attempted in Perl ;p
Using spamassassin "out of the box", it will stop about 95% of spam. With a
little tuning, you should be able to get that to >99%
I've been using it for over a year, and it saves me a great deal of pain.
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 5492
***************************************
