[28834] in Perl-Users-Digest
Perl-Users Digest, Issue: 78 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 26 06:06:21 2007
Date: Fri, 26 Jan 2007 03:05:09 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 26 Jan 2007 Volume: 11 Number: 78
Today's topics:
Re: appending to a global filehandle <bik.mido@tiscalinet.it>
Re: Bus error <bik.mido@tiscalinet.it>
Re: efficiency question about 'split' <g_m@remove-comcast.net>
Re: Hash of Hashes <josef.moellers@fujitsu-siemens.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: problems regexp <rvtol+news@isolution.nl>
Re: SOAP::Lite + wsdl misunderstanding? <stevel@bluetuna.com>
Sort on multiple values <ppi@searchy.net>
Re: Sort on multiple values anno4000@radom.zrz.tu-berlin.de
Re: Sort on multiple values <ppi@searchy.net>
Re: Statistics Extraction <josef.moellers@fujitsu-siemens.com>
Re: String Substitution question <rvtol+news@isolution.nl>
Re: Style questions <bik.mido@tiscalinet.it>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 26 Jan 2007 09:26:14 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: appending to a global filehandle
Message-Id: <icejr2dmmtjroiqumehfluakj7mfl4t76f@4ax.com>
On 25 Jan 2007 17:39:40 -0800, "markpark"
<mark.leeds@morganstanley.com> wrote:
>i have a function called writedata and, inside the function, some
>things
>get calculated ( details not important ) and then a file gets opened
>and written to. but this function
>is called over and over and what i want to do is keep appending to the
>same file.
>but, it seems like using the >> doesn't help because the files becomes
>empty
>once the routine is exited ?
Well, it simply *shouldn't*. Maybe something else is going wrong.
>i guess that i need to make the filehandle global somehow but i'm not
>clear on how to do that ?
Filehandles, but lexical ones, *are* global. And this is an option.
>or maybe send it in as a parameter ? thank you very much for any help
>that can be provided.
This is another option.
># MAIN PROGRAM ( not quite but this gives the idea )
>
>foreach (my $bin=$exchMap->{$Exch}{s2}; $bin<=$exchMap->{$Exch}{e2};
>$bin++) {
Although this is "not quite" your real program, it's still too verbose
and complex for me to want to dig through it. The general
recommendation is to prepare a minimal but complete example still
exhibiting the problem. Often in the course of doing so one finds the
solution by herself.
I'll try to provide some minimal code myself, in the hope it helps:
#!/usr/bin/perl
use strict;
use warnings;
sub writedata {
my ($fh,$data)=@_;
print $fh $data, "\n";
}
open my $fh, '>>', 'test.txt'
or die "Can't open `test.txt': $!\n";
writedata $fh, $_ for 1..10;
__END__
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 26 Jan 2007 09:35:57 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Bus error
Message-Id: <ivejr2h4cabh60d2s37nqi94j2v35mrupu@4ax.com>
On 25 Jan 2007 18:58:31 -0800, "pallav" <pallavgupta@gmail.com> wrote:
>!/usr/bin/perl -w
>
># $Id:$
>
>use strict;
[snip]
Whoa! That's 469 lines, and uses quite a lot of modules, not all of
which may be on anyone's system. BTW: not likely to be your problem,
but the shebang line misses a # at the beginning. As it is now it will
cause your script to not even compile. Whatever, can you trim it down
to a minimal but complete example still exhibiting the problem? If so,
your will immensely increase the chances people will be able to help
you: many of us surely want to, but they also want to be helped doing
so. Moreover, in the process of creating it, chances are that you will
find the solution yourself, well that's what often happens, although
admittedly it can possibly be more difficult in this specific case.
Incidentally, I didn't really read your code, but a quick peek into it
revealed lots of &-forms of sub call, which is now obsolete and
deprecated, unless you *really* know what you're doing. Well, this
will hardly have to do with your actual problem, but you may want to
know anyway...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 26 Jan 2007 03:51:12 -0500
From: "~greg" <g_m@remove-comcast.net>
Subject: Re: efficiency question about 'split'
Message-Id: <moqdnTpZZv2KXCTYnZ2dnUVZ_vupnZ2d@comcast.com>
thank you all!
although i am still not quite sure what the answer is, then again,
I am not quite sure what my question was either.
And I know I made factual mistakes in asking it.
Pretty silly in any case.
I've got a 2.8 ghz processor, 2gig of ram,
and about a terabyte of external storage.
It's just that, -late at night, -when I asked the question
about efficiency, -my heart had somehow gone back
to the commodore-64, -- 0.9875 mhz 6502 chip,
64k ram (expanded to 128)
360k floppies (-but unlimited memory on cassette.)
The only decent way to program back then
was in Forth and assembly.
And efficiency was everything.
so, I am sorry.
i was just having a senior moment.
~greg.
------------------------------
Date: Fri, 26 Jan 2007 09:40:28 +0100
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Hash of Hashes
Message-Id: <epcett$mrp$2@nntp.fujitsu-siemens.com>
doni wrote:
> Hi,
>=20
> I am having some problems in printing the Hash of Hashes.
Beg your pardon?
Why are you starting a new thread on almost the same subject as the old=20
thread? Are you not satisfied with the answers that you get? Or is=20
progress too slow and the deadline for your homework is nearing and you=20
are desperate to get answers?
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 26 Jan 2007 08:10:06 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <45b9b75d$0$82269$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.7 $)
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.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 that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 26 Jan 2007 11:13:55 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: problems regexp
Message-Id: <epcnqf.cc.1@news.isolution.nl>
john.swilting schreef:
> if($data{attachement} = ~m/$`\.gif/){
Or try substr:
if ( substr($data{attachement}, -4) eq q/.gif/ ) {
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Fri, 26 Jan 2007 01:43:38 -0800
From: Steve Leibel <stevel@bluetuna.com>
Subject: Re: SOAP::Lite + wsdl misunderstanding?
Message-Id: <stevel-D4A6EF.01433826012007@news.giganews.com>
In article <Xns98C1E9B023365castleamber@130.133.1.4>,
John Bokma <john@castleamber.com> wrote:
> Hi,
>
> I thought that the whole point of providing a wsdl file to SOAP::Lite was
> that SOAP::Lite could turn a structure like:
>
> foo => { bar => 1, baz => [ 0, 1, 2, 3, 4, 5 ] }
>
> into XML with the right types based on the information in the WSDL file
> (which I consider a grammar specification). Or am I severely mistaken and
> the Lite in SOAP::Lite means it doesn't do this?
SOAP::Lite does not appear to work very well with WSDL; nor does it
handle structured data in such a way as to be compatible with Java
interfaces generated from the same WSDL.
I posted about this recently and got only one comment. It troubles me
that Perl is falling so far behind in the SOAP world. It also troubles
me that nobody else seems troubled.
From www.soaplite.com:
"As a result, SOAP::Lite has a number of known interoperability issues
with more modern implementations of SOAP servers and clients."
It's a problem when you're working in a mixed Java/Perl shop, and the
Java guys have a web service, and you have to hand-code a client to talk
to it because the Perl WSDL support isn't there.
Likewise it's a problem when you can't mplement a Perl-based Web
service, despite the existence of an O'Reilly book saying you can.
------------------------------
Date: Fri, 26 Jan 2007 10:18:39 +0100
From: Frank <ppi@searchy.net>
Subject: Sort on multiple values
Message-Id: <45b9c77a$0$331$e4fe514c@news.xs4all.nl>
Hi,
I've been trying to sort an hash on multiple items, but at the moment
with no success.
I got this script:
%hash = (
'one' =>
{'1'=>'a','2'=>'m'},
'two' =>
{'1'=>'a','2'=>'k'},
'thr' =>
{'1'=>'b','2'=>'b'},
'fou' =>
{'1'=>'c','2'=>'l'},
'fiv' =>
{'1'=>'a','2'=>'d'},
'six' =>
{'1'=>'a','2'=>'f'},
'sev' =>
{'1'=>'b','2'=>'f'},
'eig' =>
{'1'=>'a','2'=>'e'},
);
%hash_sort = sort {
$hash{$a}{'1'} cmp $hash{$b}{'1'} || $hash{$a}{'1'} cmp $hash{$b}{'2'}
} keys(%hash);
foreach $key(%hash_sort) {
print "Test: ($key) ".$hash{$key}{'1'}." - " . $hash{$key}{'2'} . "\n";
}
But I seems to just return it in some random order.
What could be wrong?
Regards,
Frank
------------------------------
Date: 26 Jan 2007 09:30:16 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Sort on multiple values
Message-Id: <51u018F1mcj1lU1@mid.dfncis.de>
Frank <ppi@searchy.net> wrote in comp.lang.perl.misc:
> Hi,
>
> I've been trying to sort an hash on multiple items, but at the moment
> with no success.
Well, you *can't* sort a hash, so the lack of success is no surprise.
Hash entries have no defined order.
> I got this script:
>
> %hash = (
> 'one' =>
> {'1'=>'a','2'=>'m'},
> 'two' =>
> {'1'=>'a','2'=>'k'},
> 'thr' =>
> {'1'=>'b','2'=>'b'},
> 'fou' =>
> {'1'=>'c','2'=>'l'},
> 'fiv' =>
> {'1'=>'a','2'=>'d'},
> 'six' =>
> {'1'=>'a','2'=>'f'},
> 'sev' =>
> {'1'=>'b','2'=>'f'},
> 'eig' =>
> {'1'=>'a','2'=>'e'},
> );
>
> %hash_sort = sort {
> $hash{$a}{'1'} cmp $hash{$b}{'1'} || $hash{$a}{'1'} cmp $hash{$b}{'2'}
> } keys(%hash);
Your sort block looks fine, but it is nonsense to assign the list of
hash keys to another hash. You don't even know if there's an even or
odd number of elements in it.
Try this (untested):
my @ordered_keys = sort {
$hash{$a}{'1'} cmp $hash{$b}{'1'} ||
$hash{$a}{'1'} cmp $hash{$b}{'2'}
} keys %hash;
print "$_ => $hash{ $_}\n" for @ordered_keys;
Anno
------------------------------
Date: Fri, 26 Jan 2007 11:17:25 +0100
From: Frank <ppi@searchy.net>
Subject: Re: Sort on multiple values
Message-Id: <45b9d540$0$322$e4fe514c@news.xs4all.nl>
anno4000@radom.zrz.tu-berlin.de wrote:
> Frank <ppi@searchy.net> wrote in comp.lang.perl.misc:
>> Hi,
>>
>> I've been trying to sort an hash on multiple items, but at the moment
>> with no success.
>
> Well, you *can't* sort a hash, so the lack of success is no surprise.
> Hash entries have no defined order.
>
>> I got this script:
>>
>> %hash = (
>> 'one' =>
>> {'1'=>'a','2'=>'m'},
>> 'two' =>
>> {'1'=>'a','2'=>'k'},
>> 'thr' =>
>> {'1'=>'b','2'=>'b'},
>> 'fou' =>
>> {'1'=>'c','2'=>'l'},
>> 'fiv' =>
>> {'1'=>'a','2'=>'d'},
>> 'six' =>
>> {'1'=>'a','2'=>'f'},
>> 'sev' =>
>> {'1'=>'b','2'=>'f'},
>> 'eig' =>
>> {'1'=>'a','2'=>'e'},
>> );
>>
>> %hash_sort = sort {
>> $hash{$a}{'1'} cmp $hash{$b}{'1'} || $hash{$a}{'1'} cmp $hash{$b}{'2'}
>> } keys(%hash);
>
> Your sort block looks fine, but it is nonsense to assign the list of
> hash keys to another hash. You don't even know if there's an even or
> odd number of elements in it.
>
> Try this (untested):
>
> my @ordered_keys = sort {
> $hash{$a}{'1'} cmp $hash{$b}{'1'} ||
> $hash{$a}{'1'} cmp $hash{$b}{'2'}
> } keys %hash;
>
> print "$_ => $hash{ $_}\n" for @ordered_keys;
>
> Anno
Now it works fine ^O^
Assigning the list to an hash instead of an array was not very smart :P
thanks,
Frank
------------------------------
Date: Fri, 26 Jan 2007 09:36:50 +0100
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Statistics Extraction
Message-Id: <epcen3$mrp$1@nntp.fujitsu-siemens.com>
doni wrote:
> On Jan 25, 12:13 am, Josef Moellers
> <josef.moell...@fujitsu-siemens.com> wrote:
>=20
>>It is a common understanding in this group that we don't write code for=
>>you, but we're willing to comment on any code that you post. Our
>>comments may very well contain code e.g. when we want to suggest a
>>different approach, as I did in my reply.
>>So, play around with the code that was posted and come back if you have=
>>(unworking) code. Post that code and we're glad to suggest modification=
s.
>>--
>=20
>=20
> Joseph,
>=20
> Can you take a look at the code below...
>=20
>=20
> MAC, PHY and Network stats gets generated every 30 minutes and are
> copied to a file.
> I want to extract all the stats information that is copied to a file
> into an hash of hashes and print them.
> The file has multiple MAC, PHY and Network Statistics in it and I am
> extracting the MAC data in a MAC hash of hashes, PHY data in a PHY hash=
> of hashes and Network data in a Network hash of hashes.
> Here is how the data that is represented in a file. There will be
> multiple MAC, PHY and Network Statistics in the file but I am showing
> only one of them in here as an example.
>=20
> For example, if there were 10 MAC Statistics in the file, this is how I=
> want the data from the "frames with invalid header" stats message to be=
> copied to a hash.
> $mac{'frames with invalid header'}{1} =3D 0
> $mac{'frames with invalid header'}{2} =3D 0
> ....... $mac{'frames with invalid header'}{10} =3D 0
>=20
>=20
> Here is the program I wrote to do the above operation but its not
> working as expected. Can anyone let me know where I went wrong.
It's a very bad description: "its not working as expected".
Maybe you ask perl where you went wrong:
use warnings;
use strict;
When I defined those variables that you didn't ($key, %network, $value), =
I got:
Message Value is: 4
Message Value is: 61
Message Value is: 87
Message Value is: 4597
Message Value is: 1693
Message Value is: 0
Message Value is: 0
Message Value is: 542
Message Value is: 0
Message Value is: 851
Message Value is: 152
Message Value is: 546
Message Value is: 0
Message Value is: 763
Message Value is: 0
Message Value is: 549
What did you expect?
There are several other issues in your program (lexical filehandles,=20
unnecessary initializations), but rather than rewrite it as _I_ would=20
have written it (which may not be your style), again:
1. ask perl for help ("use ...")
2. specify exactly what you expect and what you get.
Josef
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Fri, 26 Jan 2007 11:37:41 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: String Substitution question
Message-Id: <epcp9i.1gk.1@news.isolution.nl>
Mirco Wahab schreef:
> my @stuff = qw'( ) [ ] ? * . $ + _ -';
> my $m = '[' . (join '', map quotemeta, @stuff) . ']';
Alternatives:
my $m = q:[: . quotemeta( q:()[]?*.$+_-: ) . q:]: ;
$ perl -wle'
my $m = q:][()?*.$+_-: ;
print qr/[$m]/
'
(?-xism:[][()?*.$+_-])
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: Fri, 26 Jan 2007 09:14:45 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Style questions
Message-Id: <hndjr21i8rtri8d7tokhnj6t667haut785@4ax.com>
On Thu, 25 Jan 2007 22:48:18 GMT, "Colin B."
<cbigam@somewhereelse.nucleus.com> wrote:
>I'm not a programmer, and never have been. I can grind out a decent shell
>script, and beat my head against perl until things work, but I'm seldom
>happy with the inelegance of the solution. Does anyone have any good style
>guides for perl?
There's the one that comes with Perl:
perldoc perlstyle
>And more specifically, I've got the following general case that keeps coming
>up routinely.
>
>foreach (`some_unix_command_that_puts_out_multiple_lines`) {
Nothing wrong with this. Personally I have an idiosincrasy with
backticks and prefer qx with alternative delimiters, but that's just
me. (That's also in shell scripts, where I prefer $() all the time,
but there the latter has the additional, *technical*, advantage of
allowing nesting.)
Other than that, if your unix command puts out *lots* of multiple
lines, you may want to use a "piped" open() instead, and read line by
line, although all in all it is a more verbose solution.
> chomp;
> split;
split() in void context is deprecated. Perl emits a warning if
warnings are on. I strongly recommend you put the following two lines
at the beginning of your scripts:
use strict;
use warnings;
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 78
*************************************
