[32864] in Perl-Users-Digest
Perl-Users Digest, Issue: 4132 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Feb 6 14:09:42 2014
Date: Thu, 6 Feb 2014 11:09:13 -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 Thu, 6 Feb 2014 Volume: 11 Number: 4132
Today's topics:
HTTP::Status - was Initialising a hash <dave@invalid.invalid>
Re: HTTP::Status <hjp-usenet3@hjp.at>
Re: HTTP::Status <dave@invalid.invalid>
Re: Initialising a hash <rweikusat@mobileactivedefense.com>
Re: Initialising a hash <john@castleamber.com>
Re: Initialising a hash <Huge@nowhere.much.invalid>
Re: Initialising a hash <jimsgibson@gmail.com>
Re: Initialising a hash <xhoster@gmail.com>
Re: Initialising a hash <derykus@gmail.com>
Re: Initialising a hash <dave@invalid.invalid>
Re: Initialising a hash <dave@invalid.invalid>
Re: Initialising a hash <dave@invalid.invalid>
Re: Initialising a hash <Huge@nowhere.much.invalid>
Re: Initialising a hash <ben@morrow.me.uk>
Re: Initialising a hash <ben@morrow.me.uk>
Re: Initialising a hash <dave@invalid.invalid>
Re: Initialising a hash <rweikusat@mobileactivedefense.com>
Re: Initialising a hash <rweikusat@mobileactivedefense.com>
Re: Initialising a hash (Tim McDaniel)
Re: Initialising a hash <rweikusat@mobileactivedefense.com>
Re: use MCE; <marioeroy@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 6 Feb 2014 13:20:38 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: HTTP::Status - was Initialising a hash
Message-Id: <fV45K0OBJxbE-pn2-J1DXcrhTOM0c@paddington.bear.den>
On Wed, 5 Feb 2014 21:02:03 UTC, John Bokma <john@castleamber.com>
wrote:
>
> use HTTP::Status;
>
> print status_message( $code ), "\n";
I have read and think I understood the code of this module. What I
don't understand is how does one make use of the mnemonics? I can't
find an example.
I thought what it did was setup subroutine(s) that take no paramteters
and return the code number. But anything I tried seems to want one to
code RC_LOCKED() rather than RC_LOCKED which I thought was the general
idea.
--
Regards
Dave Saville
------------------------------
Date: Thu, 6 Feb 2014 18:58:15 +0100
From: "Peter J. Holzer" <hjp-usenet3@hjp.at>
Subject: Re: HTTP::Status
Message-Id: <slrnlf7j9n.ial.hjp-usenet3@hrunkner.hjp.at>
On 2014-02-06 13:20, Dave Saville <dave@invalid.invalid> wrote:
> On Wed, 5 Feb 2014 21:02:03 UTC, John Bokma <john@castleamber.com>
> wrote:
>> use HTTP::Status;
>>
>> print status_message( $code ), "\n";
>
> I have read and think I understood the code of this module. What I
> don't understand is how does one make use of the mnemonics? I can't
> find an example.
>
> I thought what it did was setup subroutine(s) that take no paramteters
> and return the code number.
This works for me:
#!/usr/bin/perl
use warnings;
use strict;
use v5.10;
use HTTP::Status qw(:constants);
say HTTP_FOUND;
say "Location: http://example.com";
say "";
__END__
hp
--
_ | Peter J. Holzer | Fluch der elektronischen Textverarbeitung:
|_|_) | | Man feilt solange an seinen Text um, bis
| | | hjp@hjp.at | die Satzbestandteile des Satzes nicht mehr
__/ | http://www.hjp.at/ | zusammenpaßt. -- Ralph Babel
------------------------------
Date: Thu, 6 Feb 2014 18:58:12 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: HTTP::Status
Message-Id: <fV45K0OBJxbE-pn2-MuxpFDxiuKyu@paddington.bear.den>
On Thu, 6 Feb 2014 17:58:15 UTC, "Peter J. Holzer"
<hjp-usenet3@hjp.at> wrote:
> On 2014-02-06 13:20, Dave Saville <dave@invalid.invalid> wrote:
> > On Wed, 5 Feb 2014 21:02:03 UTC, John Bokma <john@castleamber.com>
> > wrote:
> >> use HTTP::Status;
> >>
> >> print status_message( $code ), "\n";
> >
> > I have read and think I understood the code of this module. What I
> > don't understand is how does one make use of the mnemonics? I can't
> > find an example.
> >
> > I thought what it did was setup subroutine(s) that take no paramteters
> > and return the code number.
>
> This works for me:
>
> #!/usr/bin/perl
> use warnings;
> use strict;
> use v5.10;
>
> use HTTP::Status qw(:constants);
>
> say HTTP_FOUND;
> say "Location: http://example.com";
> say "";
> __END__
>
Not on 5.8.2 :-) Seems you need to qw( <the ones you need> ). There
is no generic that gets the lot. Thanks for the pointer though.
--
Regards
Dave Saville
------------------------------
Date: Wed, 05 Feb 2014 20:18:51 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Initialising a hash
Message-Id: <87fvnx71p0.fsf@sable.mobileactivedefense.com>
"Dave Saville" <dave@invalid.invalid> writes:
> I have a script that processes apache log files.
>
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
>
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
Considering that RFC2616 defines 41 response codes, I think I'd just
grap them from the table of contents, use a perl one-liner to munge that
into 'hash syntax',
perl -ane '$F[0] =~ /(\d+\.){2}\d+/ or next; $e = $F[2]; $_ =~ /\./ and last or $e .= " $_" for @F[3 .. $#F]; print($F[1], "=> '\''$e'\'',\n");'
(works for a shell with 'bourne-style quoting rules')
and include that literally in the code (as 'body' of a hash
initialization, obviously).
------------------------------
Date: Wed, 05 Feb 2014 15:02:03 -0600
From: John Bokma <john@castleamber.com>
Subject: Re: Initialising a hash
Message-Id: <87zjm5xohg.fsf@castleamber.com>
"Dave Saville" <dave@invalid.invalid> writes:
> I have a script that processes apache log files.
>
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
>
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
4)
use HTTP::Status;
print status_message( $code ), "\n";
--
John Bokma j3b
Blog: http://johnbokma.com/ Perl Consultancy: http://castleamber.com/
Perl for books: http://johnbokma.com/perl/help-in-exchange-for-books.html
------------------------------
Date: 5 Feb 2014 21:41:33 GMT
From: Huge <Huge@nowhere.much.invalid>
Subject: Re: Initialising a hash
Message-Id: <blfpgdF6abfU1@mid.individual.net>
On 2014-02-05, Dave Saville <dave@invalid.invalid> wrote:
> I have a script that processes apache log files.
>
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
>
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
>
> 1 is out. I was doing it but forgot all about it and one day deleted
> the file on a "what;s that doing here?" thought.
Which is why I always code the ability to have comments into such files
and comment them "HTTP Error codes, used by /usr/local/bin/apache_log_report",
or whatever.
--
Today is Sweetmorn, the 36th day of Chaos in the YOLD 3180
"Mistake Not My Current State Of Joshing Gentle Peevishness For The
Awesome And Terrible Majesty Of The Towering Seas Of Ire That Are
Themselves The Milquetoast Shallows Fringing My Vast Oceans Of Wrath"
------------------------------
Date: Wed, 05 Feb 2014 16:47:09 -0800
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: Initialising a hash
Message-Id: <050220141647090555%jimsgibson@gmail.com>
In article <blfpgdF6abfU1@mid.individual.net>, Huge
<Huge@nowhere.much.invalid> wrote:
> On 2014-02-05, Dave Saville <dave@invalid.invalid> wrote:
> > I have a script that processes apache log files.
> >
> > One of the items it needs is a "number to english" look up of HTTP
> > error codes. There are around 80 of the things.
> >
> > Given "200 OK" etc. per line I can see three ways of doing it:
> >
> > 1) External file, read and parse into a hash with the number as the
> > key.
> > 2) Ditto but have the codes internally under __DATA__
> > 3) Actually init as a hash - "code" => "english".
> >
> > 1 is out. I was doing it but forgot all about it and one day deleted
> > the file on a "what;s that doing here?" thought.
>
> Which is why I always code the ability to have comments into such files
> and comment them "HTTP Error codes, used by /usr/local/bin/apache_log_report",
> or whatever.
Which is why I always create either a backup system or a configuration
control system, but usually both.
--
Jim Gibson
------------------------------
Date: Wed, 05 Feb 2014 20:08:35 -0800
From: Xho Jingleheimerschmidt <xhoster@gmail.com>
Subject: Re: Initialising a hash
Message-Id: <lcv1sm$ivt$1@dont-email.me>
On 02/05/14 10:38, Dave Saville wrote:
> I have a script that processes apache log files.
>
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
>
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
>
> 1 is out. I was doing it but forgot all about it and one day deleted
> the file on a "what;s that doing here?" thought.
>
> I have changed to 2, but just wonder about the pros and cons of 2 vs 3
> - if there are any.
The main trade off for 2 is that you might someday decide you need your
__DATA__ section for something less amenable to a 3-ish solution than
this is.
Also, I suppose you might one day see the __DATA__ section and say
"What's that doing here" and delete it. If you are prone to doing that
sort of thing.
Xho
------------------------------
Date: Wed, 5 Feb 2014 22:22:13 -0800 (PST)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: Initialising a hash
Message-Id: <e428224a-6cf5-4c9d-bb60-f91542a0ea5f@googlegroups.com>
On Wednesday, February 5, 2014 10:38:32 AM UTC-8, Dave Saville wrote:
> I have a script that processes apache log files.
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
>
> 1 is out. I was doing it but forgot all about it and one day deleted
> I have changed to 2, but just wonder about the pros and cons of 2 vs 3
>
I'd combine them:
my %CODE;
{ local($/,$_); $_=<DATA>; %CODE = /(...)...(...)/mg }
--
Charles DeRykus
------------------------------
Date: Thu, 6 Feb 2014 10:39:14 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Initialising a hash
Message-Id: <fV45K0OBJxbE-pn2-39JhYJ89RuME@paddington.bear.den>
On Thu, 6 Feb 2014 00:47:09 UTC, Jim Gibson <jimsgibson@gmail.com>
wrote:
> In article <blfpgdF6abfU1@mid.individual.net>, Huge
> <Huge@nowhere.much.invalid> wrote:
>
<snip>
> > Which is why I always code the ability to have comments into such files
> > and comment them "HTTP Error codes, used by /usr/local/bin/apache_log_report",
> > or whatever.
Unfortunately I did not look in the file - I just went by the name.
:-(
>
> Which is why I always create either a backup system or a configuration
> control system, but usually both.
>
I do have a backup - but the deletion was over a year ago and I don't
keep them that long.
--
Regards
Dave Saville
------------------------------
Date: Thu, 6 Feb 2014 10:47:17 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Initialising a hash
Message-Id: <fV45K0OBJxbE-pn2-7w96qq0eq9md@paddington.bear.den>
On Wed, 5 Feb 2014 21:02:03 UTC, John Bokma <john@castleamber.com>
wrote:
> "Dave Saville" <dave@invalid.invalid> writes:
>
> > I have a script that processes apache log files.
> >
> > One of the items it needs is a "number to english" look up of HTTP
> > error codes. There are around 80 of the things.
> >
> > Given "200 OK" etc. per line I can see three ways of doing it:
> >
> > 1) External file, read and parse into a hash with the number as the
> > key.
> > 2) Ditto but have the codes internally under __DATA__
> > 3) Actually init as a hash - "code" => "english".
>
> 4)
>
> use HTTP::Status;
>
> print status_message( $code ), "\n";
Thanks for that - Did not know of it - and I had it :-) Specific
solution but I was also after the general case. Which others have
commented on.
--
Regards
Dave Saville
------------------------------
Date: Thu, 6 Feb 2014 10:53:35 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Initialising a hash
Message-Id: <fV45K0OBJxbE-pn2-LWLq6OiuClY4@paddington.bear.den>
On Thu, 6 Feb 2014 04:08:35 UTC, Xho Jingleheimerschmidt
<xhoster@gmail.com> wrote:
<snip>
>
> Also, I suppose you might one day see the __DATA__ section and say
> "What's that doing here" and delete it. If you are prone to doing that
> sort of thing.
LOL. Much, much less likely to delete a chunk of a script without too
much thought than a data file that appeared in a cgi directory.
Actually the decision was slightly more complicated than "Why's that
here? rm" but the details are irrelevant to the discussion in hand.
--
Regards
Dave Saville
------------------------------
Date: 6 Feb 2014 11:12:38 GMT
From: Huge <Huge@nowhere.much.invalid>
Subject: Re: Initialising a hash
Message-Id: <blh916FfdsaU1@mid.individual.net>
On 2014-02-06, Jim Gibson <jimsgibson@gmail.com> wrote:
> In article <blfpgdF6abfU1@mid.individual.net>, Huge
><Huge@nowhere.much.invalid> wrote:
>
>> On 2014-02-05, Dave Saville <dave@invalid.invalid> wrote:
>> > I have a script that processes apache log files.
>> >
>> > One of the items it needs is a "number to english" look up of HTTP
>> > error codes. There are around 80 of the things.
>> >
>> > Given "200 OK" etc. per line I can see three ways of doing it:
>> >
>> > 1) External file, read and parse into a hash with the number as the
>> > key.
>> > 2) Ditto but have the codes internally under __DATA__
>> > 3) Actually init as a hash - "code" => "english".
>> >
>> > 1 is out. I was doing it but forgot all about it and one day deleted
>> > the file on a "what;s that doing here?" thought.
>>
>> Which is why I always code the ability to have comments into such files
>> and comment them "HTTP Error codes, used by /usr/local/bin/apache_log_report",
>> or whatever.
>
> Which is why I always create either a backup system or a configuration
> control system, but usually both.
Good ideas both, but they don't answer the question, "What's this file
for?"
--
Today is Boomtime, the 37th day of Chaos in the YOLD 3180
"Mistake Not My Current State Of Joshing Gentle Peevishness For The
Awesome And Terrible Majesty Of The Towering Seas Of Ire That Are
Themselves The Milquetoast Shallows Fringing My Vast Oceans Of Wrath"
------------------------------
Date: Thu, 6 Feb 2014 11:21:11 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Initialising a hash
Message-Id: <7q7csa-h2v2.ln1@anubis.morrow.me.uk>
Quoth "Dave Saville" <dave@invalid.invalid>:
> I have a script that processes apache log files.
>
> One of the items it needs is a "number to english" look up of HTTP
> error codes. There are around 80 of the things.
>
> Given "200 OK" etc. per line I can see three ways of doing it:
>
> 1) External file, read and parse into a hash with the number as the
> key.
> 2) Ditto but have the codes internally under __DATA__
> 3) Actually init as a hash - "code" => "english".
There have been a number of suggestions--including the right one,
HTTP::Status--but in the more general case I would say 1. there doesn't
seem to be any good reason not to write this as plain Perl code but 2.
this code should go in a module so it can be reused. That is, if
HTTP::Status didn't exist, you should have created it.
For the even-more-general case where the data to be represented is
complicated enough that it actually makes sense to store it in some
other format than Perl code and parse it every time, the fact that every
module gets its own __DATA__ section gives you a convenient place to put
things. For non-textual data or situations where multiple files are
required, you can use File::ShareDir.
Ben
------------------------------
Date: Thu, 6 Feb 2014 11:23:30 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Initialising a hash
Message-Id: <iu7csa-h2v2.ln1@anubis.morrow.me.uk>
Quoth usenet@huge.org.uk:
> On 2014-02-06, Jim Gibson <jimsgibson@gmail.com> wrote:
> >
> > Which is why I always create either a backup system or a configuration
> > control system, but usually both.
>
> Good ideas both, but they don't answer the question, "What's this file
> for?"
A properly-used VCS does. 'git log foo' (or whatever) should tell you
exactly what this file is, why it's here, and why it has the contents it
does.
Ben
------------------------------
Date: Thu, 6 Feb 2014 12:25:25 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Initialising a hash
Message-Id: <fV45K0OBJxbE-pn2-CPiBGUvKuZdh@paddington.bear.den>
On Thu, 6 Feb 2014 11:21:11 UTC, Ben Morrow <ben@morrow.me.uk> wrote:
>
> Quoth "Dave Saville" <dave@invalid.invalid>:
> > I have a script that processes apache log files.
> >
> > One of the items it needs is a "number to english" look up of HTTP
> > error codes. There are around 80 of the things.
> >
> > Given "200 OK" etc. per line I can see three ways of doing it:
> >
> > 1) External file, read and parse into a hash with the number as the
> > key.
> > 2) Ditto but have the codes internally under __DATA__
> > 3) Actually init as a hash - "code" => "english".
>
> There have been a number of suggestions--including the right one,
> HTTP::Status--but in the more general case I would say 1. there doesn't
> seem to be any good reason not to write this as plain Perl code but 2.
> this code should go in a module so it can be reused. That is, if
> HTTP::Status didn't exist, you should have created it.
>
> For the even-more-general case where the data to be represented is
> complicated enough that it actually makes sense to store it in some
> other format than Perl code and parse it every time, the fact that every
> module gets its own __DATA__ section gives you a convenient place to put
> things. For non-textual data or situations where multiple files are
> required, you can use File::ShareDir.
Thanks Ben.
Maybe I should not have mentioned what the data was as it was the
general case I was after. OTOH, if I had not mentioned what the data
was I would not have found out about HTTP::Status. :-)
--
Regards
Dave Saville
------------------------------
Date: Thu, 06 Feb 2014 16:11:50 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Initialising a hash
Message-Id: <87k3d8cjax.fsf@sable.mobileactivedefense.com>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth "Dave Saville" <dave@invalid.invalid>:
>> I have a script that processes apache log files.
>>
>> One of the items it needs is a "number to english" look up of HTTP
>> error codes. There are around 80 of the things.
>>
>> Given "200 OK" etc. per line I can see three ways of doing it:
>>
>> 1) External file, read and parse into a hash with the number as the
>> key.
>> 2) Ditto but have the codes internally under __DATA__
>> 3) Actually init as a hash - "code" => "english".
>
> There have been a number of suggestions--including the right one,
> HTTP::Status--
The 'right' solution (in the sense of 'sensibly engineered') would be to
have a textual database file similar to the already existing ones, eg,
protocols or services, which can be maintained independently of anything
executable which happens to use it and which is generally useful and not
tied to a particular 'executable code module' written in a particular
language.
If the mapping is hard-coded, anyway, the next most convenient
thing would to transfer the corresponding hasg from Status.pm to the script
using it and thus, at least avoid the useless function call and make
this list maintainble without having to futz around with some third
party code module prone to being replaced inadvertently without
realising the damage until a much less convenient later time.
"Someone else wrote it and I know how to get it for free!" may also be a
sensible approach, but only insofar this helps avoiding a 'critical'
competence deficit or to increase the billed_time / actual_work_time
quotient in order to make someones conslutancy more economically viable,
although it would be debatable if die-hard 'religious' short-termism is
such a good idea in the long run.
------------------------------
Date: Thu, 06 Feb 2014 16:20:41 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Initialising a hash
Message-Id: <87fvnwciw6.fsf@sable.mobileactivedefense.com>
Rainer Weikusat <rweikusat@mobileactivedefense.com> writes:
[...]
> increase the billed_time / actual_work_time quotient in order to make
> someones conslutancy more economically viable, although it would be
> debatable if die-hard 'religious' short-termism is such a good idea in
> the long run.
Personal addition: My arguably limited experience with these people is
one of 'Caveat emptor' with the 'Caveat' being such a huge part of this
that 'run away screaming' should be considered as more sound
alternative, ie, in the end, the code will have to be replaced, anyway,
if one doesn't want to keep losing deals, while the 'consultant' has long
since sought a greener pasture elsewhere. I apologize to everyone who
actually does this as an honest business instead of a 'promise castles
in the air, get $$$ in return, let someone else deal with the debris'
scam.
------------------------------
Date: Thu, 6 Feb 2014 17:49:04 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Re: Initialising a hash
Message-Id: <ld0hug$7sq$1@reader1.panix.com>
In article <fV45K0OBJxbE-pn2-CPiBGUvKuZdh@paddington.bear.den>,
Dave Saville <dave@invalid.invalid> wrote:
>Maybe I should not have mentioned what the data was as it was the
>general case I was after.
I think you should. In my experienc: almost always, when someone asks
a general question and later gets to the specific details, it turns
out that the specific details change the answer.
--
Tim McDaniel, tmcd@panix.com
------------------------------
Date: Thu, 06 Feb 2014 18:08:42 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Initialising a hash
Message-Id: <877g98cdw5.fsf@sable.mobileactivedefense.com>
tmcd@panix.com (Tim McDaniel) writes:
> In article <fV45K0OBJxbE-pn2-CPiBGUvKuZdh@paddington.bear.den>,
> Dave Saville <dave@invalid.invalid> wrote:
>>Maybe I should not have mentioned what the data was as it was the
>>general case I was after.
>
> I think you should. In my experienc: almost always, when someone asks
> a general question and later gets to the specific details, it turns
> out that the specific details change the answer.
There's a general answer to these kind of questions and it is "use a
textual database in a well-known format which can be maintained
indepdently of your present code and used independently of the
programming language your present code happens to be written in". In
case you'd rather have something simple, use a hard-coded hash _in
your script_. Suitable places for getting the data are ...
"Someone else already wrote a script with such a hard-coded list in it
and made it available for free download, so all you really have to do is
download it and tack the two scripts together somehow" is not among the
sensible answers, not even if the code attached to the other hard-coded
list happens to be useless for anything but accessing it in an
inefficient way.
Losely related question: Isn't there a newsgroup for all of this "OMG!
Free Download available!! Run to get there while stocks last!!!"
traffic? Or alternatively, is there a newsgroup for questions and
discussions about Perl and not about "OMG! ..."?
------------------------------
Date: Wed, 5 Feb 2014 22:56:39 -0800 (PST)
From: Mario <marioeroy@gmail.com>
Subject: Re: use MCE;
Message-Id: <8b62fb7e-9109-4c3e-89da-943054d08ddc@googlegroups.com>
Hi Gamo,
I'm delighted to know that you've received the news on MCE 1.509 and hoping that the Monte Carlo simulation using MCE is helpful.
In addition to https://metacpan.org/pod/MCE::Examples, various examples are documented under https://metacpan.org/pod/MCE::Core#SYNTAX-for-INPUT_DATA.
And sure, why not... we can see if MCE is able to maximize on all available cores for a couple more examples. No problem.
Thanks,
Mario
------------------------------
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 4132
***************************************
