[32063] in Perl-Users-Digest
Perl-Users Digest, Issue: 3327 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 22 09:09:29 2011
Date: Tue, 22 Mar 2011 06:09:09 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 22 Mar 2011 Volume: 11 Number: 3327
Today's topics:
Any JMeter / Grinder 3 equivalent in Perl? <simonsharry@gmail.com>
attns newbs: ignore the parent post <ralph@happydays.com>
Data::Dumper vs. UTF-8, as usual <jidanni@jidanni.org>
Re: Data::Dumper vs. UTF-8, as usual <nospam-abuse@ilyaz.org>
Re: Data::Dumper vs. UTF-8, as usual <hjp-usenet2@hjp.at>
Re: Data::Dumper vs. UTF-8, as usual <hjp-usenet2@hjp.at>
How to pass arguments to perl <moonhkt@gmail.com>
Re: How to pass arguments to perl <uri@StemSystems.com>
Parsing some pdf files failed <ldolan@thinkinghatbigpond.net.au>
polling TCP server on Win32 (with Tk) <JohnD@nowhere.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: variable/subroutine visibility <jurgenex@hotmail.com>
Re: variable/subroutine visibility <nospam.gravitalsun@hotmail.com.nospam>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 21 Mar 2011 02:32:31 -0700 (PDT)
From: Harry <simonsharry@gmail.com>
Subject: Any JMeter / Grinder 3 equivalent in Perl?
Message-Id: <b45e88b4-e0ca-48bd-b62c-df8a1bcb7344@r19g2000prm.googlegroups.com>
Hello,
I would like to leverage my familiarity with Perl 5 to stress / load /
performance test a Java Enterprise application.
Is there a JMeter / Grinder 3 equivalent in Perl world?
Regards,
/HS
------------------------------
Date: Tue, 22 Mar 2011 08:40:38 -0400
From: Ralph Malph <ralph@happydays.com>
Subject: attns newbs: ignore the parent post
Message-Id: <6bf6c$4d8898c6$ce534406$7957@news.eurofeeds.com>
Newbs: Ignore the parent post.
It gets auto-posted by mistake.
The guy who set it up to auto-post was thrown out of
his mother's basement to go live at the ymca. As such he
no longer has access to the machine which runs the auto-post script.
We are all hoping that perhaps one day the mother unplugs
the computer during her vacuuming and puts an end to this.
------------------------------
Date: Mon, 21 Mar 2011 08:28:15 -0700 (PDT)
From: jidanni <jidanni@jidanni.org>
Subject: Data::Dumper vs. UTF-8, as usual
Message-Id: <48edd49e-4a97-4a83-ba61-072179d022ca@glegroupsg2000goo.googlegroups.com>
Gentlemen, I need to use
use utf8;
use open qw/:std :encoding(utf8)/;
in my program, but it has the side effect of causing
print Dumper "=E9=BE=94";
to print
$VAR1 =3D "\x{9f94}";
instead of
$VAR1 =3D "=E9=BE=94";
like it would otherwise. I dare not touch the 'use' stuff, so how can I
tweak this?:
use strict;
use warnings FATAL =3D> 'all';
use open qw/:std :encoding(utf8)/;
use utf8;
use Data::Dumper;
print Dumper "=E9=BE=94";
------------------------------
Date: Mon, 21 Mar 2011 22:44:51 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Data::Dumper vs. UTF-8, as usual
Message-Id: <slrniofl73.1to.nospam-abuse@powdermilk.math.berkeley.edu>
On 2011-03-21, jidanni <jidanni@jidanni.org> wrote:
> Gentlemen, I need to use
> use utf8;
> use open qw/:std :encoding(utf8)/;
> in my program, but it has the side effect of causing
> print Dumper "?";
> to print
> $VAR1 = "\x{9f94}";
> instead of
> $VAR1 = "?";
> like it would otherwise. I dare not touch the 'use' stuff, so how can I
> tweak this?:
> use strict;
> use warnings FATAL => 'all';
> use open qw/:std :encoding(utf8)/;
> use utf8;
> use Data::Dumper;
> print Dumper "?";
What are you using for editing your files? Are you sure you use a
real question mark? Check with
od -tx1a -Ax your_script.pl
I see no problem here with 5.8.8,
Ilya
------------------------------
Date: Tue, 22 Mar 2011 00:56:18 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Data::Dumper vs. UTF-8, as usual
Message-Id: <slrniofpd2.828.hjp-usenet2@hrunkner.hjp.at>
On 2011-03-21 22:44, Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
> On 2011-03-21, jidanni <jidanni@jidanni.org> wrote:
>> Gentlemen, I need to use
>> use utf8;
>> use open qw/:std :encoding(utf8)/;
>> in my program, but it has the side effect of causing
>> print Dumper "?";
>> to print
>> $VAR1 = "\x{9f94}";
>> instead of
>> $VAR1 = "?";
>> like it would otherwise. I dare not touch the 'use' stuff, so how can I
>> tweak this?:
>> use strict;
>> use warnings FATAL => 'all';
>> use open qw/:std :encoding(utf8)/;
>> use utf8;
>> use Data::Dumper;
>> print Dumper "?";
>
> What are you using for editing your files? Are you sure you use a
> real question mark?
The only question mark in jidanni's posting was at the end of "how can I
tweak this?". The character jidanni wants to be displayed is a CJK
character: http://unicode.org/cgi-bin/GetUnihanData.pl?codepoint=9F94
> I see no problem here with 5.8.8,
I see a problem with your newsreader ;-).
Unfortunately I don't know a solution for the OP's problem. This may be
a case where writing a custom dumping routine (and uploading it to CPAN)
may be worthwhile.
hp
------------------------------
Date: Tue, 22 Mar 2011 12:45:15 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Data::Dumper vs. UTF-8, as usual
Message-Id: <slrnioh2ub.23g.hjp-usenet2@hrunkner.hjp.at>
On 2011-03-21 23:56, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
> On 2011-03-21 22:44, Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
>> On 2011-03-21, jidanni <jidanni@jidanni.org> wrote:
>>> Gentlemen, I need to use
>>> use utf8;
>>> use open qw/:std :encoding(utf8)/;
>>> in my program, but it has the side effect of causing
>>> print Dumper "?";
[? was a Chinese character in the OP]
>>> to print
>>> $VAR1 = "\x{9f94}";
>>> instead of
>>> $VAR1 = "?";
>>> like it would otherwise. I dare not touch the 'use' stuff, so how can I
>>> tweak this?:
[...]
> Unfortunately I don't know a solution for the OP's problem. This may be
> a case where writing a custom dumping routine (and uploading it to CPAN)
> may be worthwhile.
Forgot to add: It also depends very much on what Data::Dumper is used
for in the OP's script: Is the output supposed to be readable by humans
or by other programs? Is the output only used for debugging purposes or
is the part of the "real" output of the program?
hp
------------------------------
Date: Mon, 21 Mar 2011 20:15:05 -0700 (PDT)
From: moonhkt <moonhkt@gmail.com>
Subject: How to pass arguments to perl
Message-Id: <6170ff6c-82d6-4d37-a63b-fc0b0c362a4e@f2g2000yqf.googlegroups.com>
Hi All
In kshell, how to past argument to perl ?
In kshell, I have Funciton PROECSS(), how to pass string1 and string2
to perl ?
PROCESS ()
{
S1="ABC"
S2="testing"
perl -ni -e -v 1' $_ =~ s/ABC/testing/;
{
print $_ ;
}
' $FN
}
moonhkt
------------------------------
Date: Mon, 21 Mar 2011 23:51:31 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: How to pass arguments to perl
Message-Id: <87pqpj95j0.fsf@quad.sysarch.com>
>>>>> "m" == moonhkt <moonhkt@gmail.com> writes:
m> Hi All
m> In kshell, how to past argument to perl ?
m> In kshell, I have Funciton PROECSS(), how to pass string1 and string2
m> to perl ?
read perldoc perlrun and it tells you how to pass args to perl on the
command line.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 22 Mar 2011 09:00:27 +1100
From: "Peter Jamieson" <ldolan@thinkinghatbigpond.net.au>
Subject: Parsing some pdf files failed
Message-Id: <7UPhp.13635$MF5.12354@viwinnwfe02.internal.bigpond.com>
I am using the following script to parse a collection of
supplied pdf files. Most of the files parsed as expected but
with some the script fell over, no output was produced,
as though the file was invisible. The files are only
alpha-numeric text, no images or graphics.
On looking at the file Properties I noticed the succesfully
parsed files had PDF Producer: doPDF Ver 6.0 Build 262
PDF Version 1.4
whilst the failures had PDF Producer: GPL Ghostscript 8.15
PDF Version 1.3
Anyone have a clue as to how I could get these errant files parsed?
Any suggestions appreciated!, Cheers, Peter
#!/usr/bin/perl -w
use strict;
use warnings;
use CAM::PDF;
my $file = 'C:/test.pdf';
my $pdf = CAM::PDF->new($file);
for my $page (1 .. $pdf->numPages()) {
my $text = $pdf->getPageText($page);
my @lines = split (/\n/, $text);
foreach my $line (@lines) {
# parse out useful information
}
}
------------------------------
Date: 22 Mar 2011 10:35:14 GMT
From: JohnD <JohnD@nowhere.com>
Subject: polling TCP server on Win32 (with Tk)
Message-Id: <4d887b62$0$9483$e4fe514c@dreader19.news.xs4all.nl>
I posted this in comp.lang.perl.tk but would like to give it a try over
here.
The problem is Win32 (Unix works). I do not understand the very
details of the differences between sockets on Unix and Windows. I just
want working code, the socket part (server).
If this socket part works I can get my real program working.
Who can help me producing a working program on Windows?
One server, one client. The client connects, sends strings (1-30 bytes)
once every few seconds, the server processes these strings within 0.1
seconds, and the connection remains open for an hour or so. If a fixed
string-length would be better: fine. If UDP is much easier: please show me.
My code so far (runs on Linux, freezes on Windows while processing the
first message)
#!/usr/bin/perl
use strict;
use warnings;
use IO::Socket;
use Tk;
$| = 1;
$SIG{PIPE} = 'IGNORE';
my $listen = IO::Socket::INET->new(
Proto => 'tcp',
LocalPort => 7777,
Listen => 1,
Reuse => 1,
) or die "Can't create listen socket : $!\n";
my $mw = MainWindow->new();
my $text = $mw->Scrolled( 'Text', )->pack();
my ($sel);
if ( $^O eq 'MSWin32' ) {
$mw->repeat( 50, [ \&new_connection, $listen ] );
}
else {
$mw->fileevent( $listen, 'readable' => [ \&new_connection, $listen ]
);
}
Tk::MainLoop;
sub new_connection {
my ($listen) = shift;
my ($sel);
my $client = $listen->accept() or warn "Can't accept connection";
$client->autoflush(1);
if ( $^O eq 'MSWin32' ) {
use IO::Select;
$sel = IO::Select->new;
$sel->add($listen);
$mw->repeat( 50, [ \&handle_connection, $client, $sel ] );
}
else {
$mw->fileevent( $client,
'readable' => [ \&handle_connection, $client, $sel ] );
}
$text->insert( 'end', "Connected\t" );
$text->see('end');
}
sub handle_connection {
my ( $client, $sel ) = shift;
if ( $^O eq 'MSWin32' ) {
my (@ready) = $sel->can_read(0);
return if $#ready == -1;
$client = $ready[0];
}
my $message = <$client>;
if ( defined $message and $message !~ /^quit/ ) {
$message =~ s/[\r\n]+$//;
$text->insert( 'end', "Got message [$message]\t" );
$text->see('end');
}
else {
$text->insert( 'end', "Connection Closed\n" );
$text->see('end');
$client->close();
}
}
A client (as simple as I could maker it)
#!/usr/bin/perl
use IO::Socket;
my $machine_addr = 'localhost';
$sock = new IO::Socket::INET(PeerAddr=>$machine_addr,
PeerPort=>7777,
Proto=>'tcp',
);
die "Could not connect: $!" unless $sock;
foreach my $count(1..100){
print $sock "$count\n";
print "$count\n";
#select(undef,undef,undef,.1) ;
}
close ($sock);
------------------------------
Date: Tue, 22 Mar 2011 02:15:01 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <1I2dnXDhg6vo0RXQnZ2dnUVZ5sSdnZ2d@giganews.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.9 $)
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_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.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Sun, 20 Mar 2011 20:18:21 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: variable/subroutine visibility
Message-Id: <3cgdo6puuju2nv05cfhueep8ffs5rsds65@4ax.com>
"ela" <ela@yantai.org> wrote:
>Previously, George has kindly designed and revised codes for "voting" the
>most representative candidate from __DATA__ below. His initial design is to
>separate subroutines query and ReadData, but as a file of million rows is to
>read, I tried to embed subroutine query into ReadData but failed. There are
>two problems (relevant lines marked with *************).
>
>1) While $a[0] is printed as '02', I don't know why it can't be passed into
>subroutine successfully
>2) When the subroutine query is called inside subroutine ReadData, error
>message "Can't coerce array into hash" will prompt during execution. In the
>debug process, I hardcode it to "01" but in real case I wanna pass a[0] as
>argument. The strange point is, if I pass a[0], the error message won't
>prompt but still nothing is to print out.
You are missing
use strict; use warnings;
Had you done so then perl would have told you:
Global symbol "$firsttime" requires explicit package name at C:\tmp\t.pl
line 5.
Global symbol "$pre_a" requires explicit package name at C:\tmp\t.pl
line 6.
Global symbol "@a" requires explicit package name at C:\tmp\t.pl line 9.
Global symbol "$thr" requires explicit package name at C:\tmp\t.pl line
9.
Global symbol "$thr" requires explicit package name at C:\tmp\t.pl line
11.
Global symbol "$pre_a" requires explicit package name at C:\tmp\t.pl
line 34.
Global symbol "$pre_a" requires explicit package name at C:\tmp\t.pl
line 35.
Global symbol "$firsttime" requires explicit package name at C:\tmp\t.pl
line 36
.
Global symbol "$thr" requires explicit package name at C:\tmp\t.pl line
37.
Global symbol "$firsttime" requires explicit package name at C:\tmp\t.pl
line 40
.
Execution of C:\tmp\t.pl aborted due to compilation errors.
I would suggest to fix those first and then ask again.
Furthermore the indentation of your code is -shall we say- imaginative,
making it very hard to read your code.
>my @col;
>my %data;
>$firsttime = 1;
>$pre_a = "dummy";
>
>ReadData();
> $_ = query($a[0],$thr); # *************
However it appears to me that you didn't declared nor defined @a
anywhere on this level. Of course I may be mistaken, it is difficult to
tell what is top level code and what are subs because of poor
indentation.
jue
------------------------------
Date: Mon, 21 Mar 2011 15:12:36 +0200
From: "George Mpouras" <nospam.gravitalsun@hotmail.com.nospam>
Subject: Re: variable/subroutine visibility
Message-Id: <im7iql$1olr$1@news.ntua.gr>
It is not possible to start answer questions before read all the data,
because the last lines may affect the the processed values of the previous
IDs
So you can not combine read/ask at one logical step.
I assume what you want is not to spent for every execution the time to read
and process all input data again and again. There are four answers to this.
1) keep the program alive after reading, looping around the STDIN
2) Keep the program alive implementimg a multithread client/server SOCKET
solution
3) Write the data structure to a permanent file/dir structure at hard disk
4) Load your parsed data to a BerkleyDB
Below you can find an implementation of 1)
---------------------------------------------------------
my @col;
my %data;
ReadData();
select((select(STDOUT),$|=1)[0]);
print <<stop_printing;
Wellcome to LCA shell. Ready to answer questions.
Type "exit" or "quit" any moment to exit this shell.
please type your question at the format.
ID, THESHOLD
to receive your answer.
stop_printing
print 'LCA> ';
while (<STDIN>)
{
chomp;
if (/(?i)(quit|exit)/){print "Exit LCA.\n"; exit 0}
if (/^\s*$/){print 'LCA> ';next}
if ( /^\s*(.*?)\s*,\s*(\d+)\s*/ )
{
if ( exists $data{$1})
{
if (( $2 >= 0 ) && ( $2 <= 100 ))
{
$_ = query('01',10);
print "ANSWER> Field=$_->[0],Value=@{$_->[1]}\n"
}
else
{
print "ERROR> THRESHOLD \"$2\" should be an integer between 0 and 100\n"
}
}
else
{
print "ERROR> The ID \"$1\" does not exist\n";
}
}
else
{
print "ERROR> Bad query format, please use the syntax: ID, THRESHOLD\n"
}
print 'LCA> ';
}
sub ReadData
{
print STDOUT "Please wait, while creating knowledge base.\n";
while (<DATA>) { chomp;
my @a = split /\s*\|\s*/, $_, -1;
if (-1 == $#col){push @col, @a[1..$#a] ;next}
unless (1+$#col==$#a) {warn "Skip line number $. \"$_\" because it have
".(1+$#a)." fields, while it should have ".(1+$#col)."\n";next}
$data{$a[0]}->[0]++;
for(my $i=1;$i<=$#a;$i++){$data{$a[0]}->[1]->[$i-1]->[0]->{$a[$i]}++}}
foreach my $id (keys %data)
{
foreach my $f ( @{$data{$id}->[1]} )
{
foreach my $v ( keys %{$f->[0]} )
{
push @{ $f->[1]->{int 100*( $f->[0]->{$v}/$data{$id}->[0])} }, $v
}
# remove unnecessary structures
$f = $f->[1]
}
# remove unnecessary structures
$data{$id} = $data{$id}->[1]
}
#use Data::Dumper; print Dumper(\%data);exit;
print STDOUT (((scalar keys %data).' entries loaded and
calculated.')."\n\n");
}
sub query
{
for(my $i=$#{$data{$_[0]}}; $i>=0; $i--)
{
foreach my $RANK (sort {$b <=> $a} keys %{$data{$_[0]}->[$i]})
{
return [$col[$i], $data{$_[0]}->[$i]->{$RANK}] if $RANK >= $_[1]
}
}
['',[]]
}
__DATA__
ID|B|C|D|E|F|G|H
01|3|7|9|3|4|2|3
01|3|7|9|3|4|2|2
01|3|7|9|5|8|6|6
01|3|7|9|3|4|2|3
02|4|7|9|3|4|2|1
02|4|7|9|3|4|2|2
02|4|7|9|3|4|2|3
02|4|7|9|3|4|2|3
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 3327
***************************************
