[28922] in Perl-Users-Digest
Perl-Users Digest, Issue: 166 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Feb 26 19:16:52 2007
Date: Fri, 23 Feb 2007 06:09:06 -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, 23 Feb 2007 Volume: 11 Number: 166
Today's topics:
delete() on multi level hash <moritz.maisel@googlemail.com>
Re: delete() on multi level hash <someone@example.com>
enjoy this beautiful site <Janak.Mandowara@gmail.com>
Re: enjoy this beautiful site <john.swilting@wanadoo.fr>
Re: new method to test Perl code krakle@visto.com
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
problem cp <john.swilting@wanadoo.fr>
Re: problem cp <john.swilting@wanadoo.fr>
Re: problem cp <john.swilting@wanadoo.fr>
Re: problem cp <bik.mido@tiscalinet.it>
Re: problem cp <john.swilting@wanadoo.fr>
Re: problem cp <bik.mido@tiscalinet.it>
Re: problem cp <john.swilting@wanadoo.fr>
Re: problem cp <abigail@abigail.be>
sorting an array with associated values in separate arr <jbenjam@gmail.com>
Re: sorting an array with associated values in separate <jbenjam@gmail.com>
Re: sorting an array with associated values in separate <jbenjam@gmail.com>
Re: sorting an array with associated values in separate <paduille.4060.mumia.w+nospam@earthlink.net>
Re: sorting an array with associated values in separate <bik.mido@tiscalinet.it>
Re: sorting an array with associated values in separate anno4000@radom.zrz.tu-berlin.de
To get the HTTP response headers such as content length dhawangayash@gmail.com
Re: To get the HTTP response headers such as content le <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 23 Feb 2007 02:59:56 -0800
From: "moritz.maisel@googlemail.com" <moritz.maisel@googlemail.com>
Subject: delete() on multi level hash
Message-Id: <1172228396.141250.270650@v33g2000cwv.googlegroups.com>
Hi,
how (if at all) is the behaviour of delete() defined for "multi-level-
hash-references"?
What I expected from the code at the bootom was:
$VAR1 = {
'y' => {
'8' => {
'c' => 3,
}
},
'w' => {
'' => {},
'6' => {
'a' => 1,
}
},
'x' => {
'7' => {
'b' => 2,
}
},
'z' => {
'9' => {
'd' => 4,
}
}
};
But I got:
$VAR1 = {
'y' => {
'' => {},
'8' => {
'c' => 3,
'foo' => 'y'
}
},
'w' => {
'' => {},
'6' => {
'a' => 1,
'foo' => 'w'
}
},
'x' => {
'' => {},
'7' => {
'b' => 2,
'foo' => 'x'
}
},
'z' => {
'' => {},
'9' => {
'd' => 4,
'foo' => 'z'
}
}
};
It works as expected if I copy the reference to a helper variable and
doing the delete on that, but I would like to understand the behaviour
in the described case ...
Does anybody have an explanation? Or a hint where to find one on the
net?
Thanks in advance,
Moritz
-----
#!/usr/bin/perl
use Data::Dumper;
$list = [
{ "foo" => "w", "bar" => "6" , "a" => 1 } ,
{ "foo" => "x", "bar" => "7" , "b" => 2 } ,
{ "foo" => "y", "bar" => "8" , "c" => 3 } ,
{ "foo" => "z", "bar" => "9" , "d" => 4 }
];
print Dumper $list;
foreach (@{$list}) {
$temp->{$_->{'foo'}}->{$_->{'bar'}} = $_;
delete($temp->{$_->{'foo'}}->{$_->{'bar'}}->{'bar'});
delete($temp->{$_->{'foo'}}->{$_->{'bar'}}->{'foo'});
}
print Dumper $temp;
------------------------------
Date: Fri, 23 Feb 2007 12:00:58 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: delete() on multi level hash
Message-Id: <_HADh.123362$Y6.62891@edtnps89>
moritz.maisel@googlemail.com wrote:
>
> how (if at all) is the behaviour of delete() defined for "multi-level-
> hash-references"?
>
> What I expected from the code at the bootom was:
>
> $VAR1 = {
> 'y' => {
> '8' => {
> 'c' => 3,
> }
> },
[ snip ]
> };
>
> But I got:
>
> $VAR1 = {
> 'y' => {
> '' => {},
> '8' => {
> 'c' => 3,
> 'foo' => 'y'
> }
> },
[ snip ]
> };
>
> It works as expected if I copy the reference to a helper variable and
> doing the delete on that, but I would like to understand the behaviour
> in the described case ...
>
> Does anybody have an explanation? Or a hint where to find one on the
> net?
>
> #!/usr/bin/perl
>
> use Data::Dumper;
>
> $list = [
> { "foo" => "w", "bar" => "6" , "a" => 1 } ,
> { "foo" => "x", "bar" => "7" , "b" => 2 } ,
> { "foo" => "y", "bar" => "8" , "c" => 3 } ,
> { "foo" => "z", "bar" => "9" , "d" => 4 }
> ];
>
> print Dumper $list;
>
>
> foreach (@{$list}) {
> $temp->{$_->{'foo'}}->{$_->{'bar'}} = $_;
(Using the first element of @$list.)
$temp->{ "w" }->{ "6" } = { "foo" => "w", "bar" => "6", "a" => 1 };
> delete($temp->{$_->{'foo'}}->{$_->{'bar'}}->{'bar'});
delete( $temp->{ "w" }->{ "6" }->{ 'bar' } );
Which leaves $temp with:
$temp->{ "w" }->{ "6" } = { "foo" => "w", "a" => 1 };
> delete($temp->{$_->{'foo'}}->{$_->{'bar'}}->{'foo'});
Since you just deleted the key 'bar' this becomes:
delete( $temp->{ "w" }->{ "" }->{ 'foo' } );
Autovivification creates the "" key and there is no 'foo' under that key to
delete.
> }
You probably want something like:
my $temp;
for ( @$list ) {
$temp->{ delete $_->{ foo } }{ delete $_->{ bar } } = $_;
}
print Dumper $temp;
John
--
Perl isn't a toolbox, but a small machine shop where you can special-order
certain sorts of tools at low cost and in short order. -- Larry Wall
------------------------------
Date: 23 Feb 2007 03:54:47 -0800
From: "Janak" <Janak.Mandowara@gmail.com>
Subject: enjoy this beautiful site
Message-Id: <1172231687.541588.36630@a75g2000cwd.googlegroups.com>
http://baroda-beauty.bravehost.com/
------------------------------
Date: Fri, 23 Feb 2007 13:07:52 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: Re: enjoy this beautiful site
Message-Id: <45ded917$0$27389$ba4acef3@news.orange.fr>
Janak wrote:
> http://baroda-beauty.bravehost.com/
:-[
------------------------------
Date: 23 Feb 2007 03:04:35 -0800
From: krakle@visto.com
Subject: Re: new method to test Perl code
Message-Id: <1172228675.646550.304640@j27g2000cwj.googlegroups.com>
On Feb 21, 4:02 pm, dnikola...@gmail.com wrote:
> Here is the method to test perl program when you have no machine with
> perl:http://www.codeide.com
> You can do this in IDE mode in the site or run in CGI mode on your own
> home page like here:http://nick.codeide.com/hello.cgi?name=Visitor
It's crap.
my $blah = 1;
print $blah;
And the result:
0
In addition to not being able to run simplistic code properly you also
can't use modules and any other important Perl keyword... Actually..
the only thing this thing can do it print generic print statements...
I just tried a simple IF statement and it couldn't do that either...
If you are promoting this than you are....well.... a newbie
------------------------------
Date: 23 Feb 2007 08:10:17 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <45dea168$0$3156$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, 23 Feb 2007 12:25:10 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: problem cp
Message-Id: <45decf16$0$27391$ba4acef3@news.orange.fr>
how to make a function cp
who would go like
I read the name of the old file I it copis in a variable $variable I
re-elect the new file and I copy it towards the old file while keeping the
same name of the file
------------------------------
Date: Fri, 23 Feb 2007 12:26:36 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: Re: problem cp
Message-Id: <45decf6c$0$27391$ba4acef3@news.orange.fr>
john.swilting wrote:
> how to make a function cp
> who would go like
> I read the name of the old file I it copis in a variable $variable I
> re-elect the new file and I copy it towards the old file while keeping the
> same name of the file
en français
je lis le nom de l'ancien fichier je le copis dans une variable $variable je
renomme le nouveau fichier et je le copie vers l'ancien fichier tout en
gardant le meme nom du fichier
------------------------------
Date: Fri, 23 Feb 2007 12:54:05 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: Re: problem cp
Message-Id: <45ded5dd$0$5107$ba4acef3@news.orange.fr>
john.swilting wrote:
> how to make a function cp
> who would go like
> I read the name of the old file I it copis in a variable $variable I
> re-elect the new file and I copy it towards the old file while keeping the
> same name of the file
why not
open (FH , $old_fichier);
select(FH);
rename $new_fichier, $old_fichier;
`cp $new_ficier /image1`
its nice that
------------------------------
Date: Fri, 23 Feb 2007 13:37:19 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: problem cp
Message-Id: <vtntt2ptjjljafukbpp1bsiqse57i1vbg0@4ax.com>
On Fri, 23 Feb 2007 12:54:05 +0100, "john.swilting"
<john.swilting@wanadoo.fr> wrote:
>open (FH , $old_fichier);
>select(FH);
>rename $new_fichier, $old_fichier;
>`cp $new_ficier /image1`
>
>its nice that
IMHO you want either to do it all in Perl or use OS native commands
altogether. Personally, I would perfer the former.
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, 23 Feb 2007 13:39:12 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: Re: problem cp
Message-Id: <45dee070$0$5105$ba4acef3@news.orange.fr>
john.swilting wrote:
> john.swilting wrote:
>
>> how to make a function cp
>> who would go like
>> I read the name of the old file I it copis in a variable $variable I
>> re-elect the new file and I copy it towards the old file while keeping
>> the same name of the file
> why not
>
> open (FH , $old_fichier);
> select(FH);
> rename $new_fichier, $old_fichier;
> `cp $new_ficier /image1`
>
> its nice that
not
open (FH , $old_file);
select(FH);
rename $old_file ,$new_file;
`cp $new_file /image1`;
I had to reverse the files in the rename
------------------------------
Date: Fri, 23 Feb 2007 13:38:27 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: problem cp
Message-Id: <40ott21e78jdn09k7q5cg8klaffp2ajvgu@4ax.com>
On Fri, 23 Feb 2007 12:25:10 +0100, "john.swilting"
<john.swilting@wanadoo.fr> wrote:
>how to make a function cp
[snip]
IIUC, which I find increasingly hard to believe, you may be interested
in File::Copy.
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, 23 Feb 2007 13:41:01 +0100
From: "john.swilting" <john.swilting@wanadoo.fr>
Subject: Re: problem cp
Message-Id: <45dee0dd$0$25945$ba4acef3@news.orange.fr>
Michele Dondi wrote:
> On Fri, 23 Feb 2007 12:54:05 +0100, "john.swilting"
> <john.swilting@wanadoo.fr> wrote:
>
>>open (FH , $old_fichier);
>>select(FH);
>>rename $new_fichier, $old_fichier;
>>`cp $new_ficier /image1`
>>
>>its nice that
>
> IMHO you want either to do it all in Perl or use OS native commands
> altogether. Personally, I would perfer the former.
>
>
> Michele
ok
File::*
all
its nice
------------------------------
Date: 23 Feb 2007 12:41:38 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: problem cp
Message-Id: <slrnetto7f.gq5.abigail@alexandra.abigail.be>
Michele Dondi (bik.mido@tiscalinet.it) wrote on MMMMCMXXIV September
MCMXCIII in <URL:news:vtntt2ptjjljafukbpp1bsiqse57i1vbg0@4ax.com>:
&& On Fri, 23 Feb 2007 12:54:05 +0100, "john.swilting"
&& <john.swilting@wanadoo.fr> wrote:
&&
&& >open (FH , $old_fichier);
&& >select(FH);
&& >rename $new_fichier, $old_fichier;
&& >`cp $new_ficier /image1`
&& >
&& >its nice that
&&
&& IMHO you want either to do it all in Perl or use OS native commands
&& altogether. Personally, I would perfer the former.
I very much prefer the latter.
Abigail
--
$"=$,;*{;qq{@{[(A..Z)[qq[0020191411140003]=~m[..]g]]}}}=*_;
sub _ {push @_ => /::(.*)/s and goto &{ shift}}
sub shift {print shift; @_ and goto &{+shift}}
Hack ("Just", "Perl ", " ano", "er\n", "ther "); # 20070223
------------------------------
Date: 23 Feb 2007 00:23:04 -0800
From: "Ben" <jbenjam@gmail.com>
Subject: sorting an array with associated values in separate arrays
Message-Id: <1172218984.541904.215650@h3g2000cwc.googlegroups.com>
Hi,
I have the following arrays, each with the same number of elements.
Each element of @main is associated with each corresponding element of
@b, @c, and @d. i.e., the $main[1] is associated with $b[1],
$x[1], ..., $z[1].
@main = ( 1, 3, 2, 12, 5, 7, 2, 9); # these are likely to be non-
unique floating point values in my real application
@b = ( 1, 1, 2, 1, 1, 3, 1, 3); # the rest of these are
integer values
@x = ( 0, 9, 9, 9, 8, 8, 8, 1);
@d = ( 1, 1, 1, 1, 1, 1, 1, 1);
...
I would like to sort @main numerically in ascending order, and have
@b, @x, @d, ... rearranged according to the new sorted order while
maintaining the original association. Seems like a perfect job for
a hash, I'm just not that comfortable with how to set it up in this
case.
I think that I should create a hash of array references, but I don't
know how to sort the elements (values) of "@main" and subsequently
update the other arrays with the new order. A more brute force
option that occurrs to me is to simply sort the array @main, find the
new "positions" of the sorted array relative to the original and
reorder @b, @x, @d, ... according to the new positions, without using
a hash, but using some loops. Is there a better approach here?
Note: It may be a "completely obvious" different way, I'm a perl
novice, so it is quite probable to find an easy alternate approach.
Additional information:
To populate the hash named "tmp", I'm using:
%tmp = ( );
foreach $x (@main) {
push( @{$tmp{main}}, $x );
push( @{$tmp{b}}, $b[$i] );
push( @{$tmp{x}}, $x[$i] );
push( @{$tmp{d}}, $d[$i] );
...
$i++;
}
I know how to sort a key-value hash by value:
@sorted = sort { $hash{$a} <=> $hash{$b} } keys %hash;
Just not making the next perlogical step in how to do this in the way
described above.
Aside: For populating the hash, I also tried to use the module
Tie::Hash::MultiValue, but it complains that:
Can't locate object method "TIEHASH" via package
"Tie::Hash::Multivalue" at x.pl line 68. No idea what i'm doing
wrong. I installed Tie::Hash::Multivalue following the instructions
contained in the module's README file, no error messages or warnings
running perl -w. I'm not using strict.
Thanks for your advice.
-Ben
------------------------------
Date: 23 Feb 2007 01:10:15 -0800
From: "Ben" <jbenjam@gmail.com>
Subject: Re: sorting an array with associated values in separate arrays
Message-Id: <1172221815.660431.129680@z35g2000cwz.googlegroups.com>
On Feb 23, 3:23 am, "Ben" <jben...@gmail.com> wrote:
> Hi,
>
> I have the following arrays, each with the same number of elements.
> Each element of @main is associated with each corresponding element of
> @b, @c, and @d. i.e., the $main[1] is associated with $b[1],
> $x[1], ..., $z[1].
I believe I figured it out:
Create individual hashes: %mainhash, %bhash, %xhash, ..., sort
mainhash by value, and keep the sorted keys for use in %bhash, etc..
I didn't initially think that the "keys" would be necessarily the same
for different hashes (although I had no good reason to think this).
#populate hashes
for $i (0..$#main) {
$mainhash{$i} = $main[$i];
$bhash{$i} = $b[$i];
$xhash{$i} = $x[$i];
$dhash{$i} = $d[$i];
...
}
#sort mainhash by value
@sorted = sort { $mainhash{$a} <=> $mainhash{$b} } keys %mainhash;
# print sorted hashes
foreach $key (@sorted) {
print "a: $key => $mainhash{$key}\n";
print "b: $key => $bhash{$key}\n";
print "x: $key => $xhash{$key}\n";
print "d: $key => $dhash{$key}\n";
...
}
Additional comments welcome.
-Ben
------------------------------
Date: 23 Feb 2007 01:11:06 -0800
From: "Ben" <jbenjam@gmail.com>
Subject: Re: sorting an array with associated values in separate arrays
Message-Id: <1172221866.058006.164070@s48g2000cws.googlegroups.com>
On Feb 23, 3:23 am, "Ben" <jben...@gmail.com> wrote:
> Hi,
>
> I have the following arrays, each with the same number of elements.
> Each element of @main is associated with each corresponding element of
> @b, @c, and @d. i.e., the $main[1] is associated with $b[1],
> $x[1], ..., $z[1].
I believe I figured it out:
Create individual hashes: %mainhash, %bhash, %xhash, ..., sort
mainhash by value, and keep the sorted keys for use in %bhash, etc..
I didn't initially think that the "keys" would be necessarily the same
for different hashes (although I had no good reason to think this).
#populate hashes
for $i (0..$#main) {
$mainhash{$i} = $main[$i];
$bhash{$i} = $b[$i];
$xhash{$i} = $x[$i];
$dhash{$i} = $d[$i];
...
}
#sort mainhash by value
@sorted = sort { $mainhash{$a} <=> $mainhash{$b} } keys %mainhash;
# print sorted hashes
foreach $key (@sorted) {
print "a: $key => $mainhash{$key}\n";
print "b: $key => $bhash{$key}\n";
print "x: $key => $xhash{$key}\n";
print "d: $key => $dhash{$key}\n";
...
}
Additional comments welcome. Hey, I can go to sleep now. :)
-Ben
------------------------------
Date: Fri, 23 Feb 2007 10:44:25 GMT
From: "Mumia W." <paduille.4060.mumia.w+nospam@earthlink.net>
Subject: Re: sorting an array with associated values in separate arrays
Message-Id: <dAzDh.4915$_73.3334@newsread2.news.pas.earthlink.net>
On 02/23/2007 03:11 AM, Ben wrote:
> On Feb 23, 3:23 am, "Ben" <jben...@gmail.com> wrote:
>> Hi,
>>
>> I have the following arrays, each with the same number of elements.
>> Each element of @main is associated with each corresponding element of
>> @b, @c, and @d. i.e., the $main[1] is associated with $b[1],
>> $x[1], ..., $z[1].
>
> I believe I figured it out:
>
> Create individual hashes: %mainhash, %bhash, %xhash, ..., sort
> mainhash by value, and keep the sorted keys for use in %bhash, etc.. [...]
I'm glad you figured it out. Another, possibly simpler way would be to
compact the separate (parallel) arrays into a single, two-dimensional
array and sort that:
use strict;
use warnings;
my (@main, @b, @c, @d);
@main = ( 1, 3, 2, 12, 5, 7, 2, 9);
@b = ( 1, 1, 2, 1, 1, 3, 1, 3);
@c = ( 0, 9, 7, 9, 8, 2, 4, 1);
@d = ( 1, 2, 5, 7, 8, 1, 5, 6);
my @compact;
foreach my $pos (0..$#main) {
push @compact, [$main[$pos], $b[$pos], $c[$pos], $d[$pos]];
}
print "@$_\n" for (@compact);
@compact = sort { $a->[0] <=> $b->[0] } @compact;
print "--------------------\n";
print "@$_\n" for (@compact);
The data is printed transposed, but it is sorted properly.
You might need to read about references:
Start->Run->"perldoc perlreftut"
--
Windows Vista and your freedom in conflict:
http://techdirt.com/articles/20061019/102225.shtml
------------------------------
Date: Fri, 23 Feb 2007 13:36:34 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: sorting an array with associated values in separate arrays
Message-Id: <9rntt29hp7410qbfgulm37spg4mu7hp095@4ax.com>
On 23 Feb 2007 00:23:04 -0800, "Ben" <jbenjam@gmail.com> wrote:
>I have the following arrays, each with the same number of elements.
Then it's probably a bad idea. A AoA or HoA may be a better one.
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: 23 Feb 2007 14:06:43 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: sorting an array with associated values in separate arrays
Message-Id: <548anjF1vi3efU1@mid.dfncis.de>
Ben <jbenjam@gmail.com> wrote in comp.lang.perl.misc:
> Hi,
>
> I have the following arrays, each with the same number of elements.
> Each element of @main is associated with each corresponding element of
> @b, @c, and @d. i.e., the $main[1] is associated with $b[1],
> $x[1], ..., $z[1].
>
> @main = ( 1, 3, 2, 12, 5, 7, 2, 9); # these are likely to be non-
> unique floating point values in my real application
> @b = ( 1, 1, 2, 1, 1, 3, 1, 3); # the rest of these are
> integer values
> @x = ( 0, 9, 9, 9, 8, 8, 8, 1);
> @d = ( 1, 1, 1, 1, 1, 1, 1, 1);
> ...
>
> I would like to sort @main numerically in ascending order, and have
> @b, @x, @d, ... rearranged according to the new sorted order while
> maintaining the original association. Seems like a perfect job for
> a hash, I'm just not that comfortable with how to set it up in this
> case.
That's indirect sorting, and it's done with arrays, not hashes.
You first build an array of indices (@i below) that contains the
indices to @main in the desired order. Now Perl's array slices
come in handy to reconstruct @main in sorted order and the other
arrays in the corresponding order. Here is how:
my @main = ( 1, 3, 2, 12, 5, 7, 2, 9);
my @b = ( 1, 1, 2, 1, 1, 3, 1, 3);
my @x = ( 0, 9, 9, 9, 8, 8, 8, 1);
my @d = ( 1, 1, 1, 1, 1, 1, 1, 1);
# build the index array
my @i = sort { $main[ $a] <=> $main[ $b] } 0 .. $#main;
# now @main[ @i] is the ordered array, and @b[ @i] is the
# corresponding order of @b, etc.
# print the re-ordered arrays
my $fmt = join( ' ', ( '%2.0f') x @main) . "\n";
printf $fmt, @$_[ @i] for \ ( @main, @b, @x, @d);
Anno
------------------------------
Date: 23 Feb 2007 03:16:31 -0800
From: dhawangayash@gmail.com
Subject: To get the HTTP response headers such as content length from a web server
Message-Id: <1172229391.540406.4000@j27g2000cwj.googlegroups.com>
I would like to use Perl to help me download some files by using the
curl command like this
system("curl https://www.foo.com/ -o ~/sample/Test.exe");
I need to fasten this process by simultaneously running three threads
that run the same curl command but different parts of the file. Hence
speeding up the process.
But for this I need to find the size of the file that needs to be
downloaded I thought that by getting the HTTP response for the
particular GET request I shall get the file size.
Can somebody help me how to go about with this........
------------------------------
Date: Fri, 23 Feb 2007 06:30:25 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: To get the HTTP response headers such as content length from a web server
Message-Id: <slrnettnj1.l6s.tadmc@tadmc30.august.net>
dhawangayash@gmail.com <dhawangayash@gmail.com> wrote:
> Subject: To get the HTTP response headers such as content length from a web server
use the LWP::Simple module:
perl -MLWP::Simple '(undef, $len) = head "http://www.foo.com"; print $len'
> I would like to use Perl to help me download some files by using the
> curl command like this
You can download them with native Perl, no need for curl...
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
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 166
**************************************
