[32695] in Perl-Users-Digest
Perl-Users Digest, Issue: 3959 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jun 5 11:09:22 2013
Date: Wed, 5 Jun 2013 08:09:08 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 5 Jun 2013 Volume: 11 Number: 3959
Today's topics:
BEGIN, eval and $^S <adrien.barreau@live.fr>
Re: BEGIN, eval and $^S <ben@morrow.me.uk>
if you told everyone they can learn perl and skip high <visphatesjava@gmail.com>
Is there a better way than this? <daves@orpheusmail.co.uk>
Re: Is there a better way than this? <hhr-m@web.de>
Re: Is there a better way than this? <jurgenex@hotmail.com>
Re: Is there a better way than this? <rweikusat@mssgmbh.com>
Re: Is there a better way than this? <ben@morrow.me.uk>
Re: Is there a better way than this? <m@rtij.nl.invlalid>
Re: Is there a better way than this? <derykus@gmail.com>
Re: Is there a better way than this? <ben@morrow.me.uk>
Re: Is there a better way than this? <daves@orpheusmail.co.uk>
perl and openMPI vs noSQL crap <visphatesjava@gmail.com>
perl hey perl why oo but not functinal? <visphatesjava@gmail.com>
Re: perl hey perl why oo but not functinal? <rweikusat@mssgmbh.com>
Re: perl hey perl why oo but not functinal? <rweikusat@mssgmbh.com>
Re: perl hey perl why oo but not functinal? <visphatesjava@gmail.com>
Re: perl hey perl why oo but not functinal? <visphatesjava@gmail.com>
Re: so how much money do perl programmers make? <visphatesjava@gmail.com>
Re: starman fastest perl web server? <visphatesjava@gmail.com>
unzip Zip file in a remote drive <davidgerardomx@gmail.com>
Re: unzip Zip file in a remote drive <jurgenex@hotmail.com>
Re: unzip Zip file in a remote drive <ben@morrow.me.uk>
why all this queue stuff in the java world lately? <visphatesjava@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 05 Jun 2013 12:39:40 +0200
From: Adrien BARREAU <adrien.barreau@live.fr>
Subject: BEGIN, eval and $^S
Message-Id: <kon48r$9n5$1@dont-email.me>
Hi all.
If I run that piece of code:
=====
#!/usr/bin/perl
use strict;
use warnings;
BEGIN {
$SIG{ __DIE__ } = sub { print "Defined\n" if defined $^S; print
($^S ? "True\n" : "False\n"); };
eval { die };
}
print "Done\n";
=====
It prints:
False
Done
Well, that, I understand.
If I change eval { die } to eval 'die', it prints:
Defined
True
Done
Which I don't get.
My only guess: since eval "" is described as a "little Perl program",
$^S is set to 1 because it refers to the "running" part of the eval,
after it has been successfully parsed. But, my "main" program is in
compilation time, so it seems strange.
Did I missed something about all that in the documentation?
Adrien.
------------------------------
Date: Wed, 5 Jun 2013 15:20:21 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: BEGIN, eval and $^S
Message-Id: <52u38a-4mk.ln1@anubis.morrow.me.uk>
Quoth Adrien BARREAU <adrien.barreau@live.fr>:
> Hi all.
>
> If I run that piece of code:
>
> =====
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
>
> BEGIN {
> $SIG{ __DIE__ } = sub { print "Defined\n" if defined $^S; print
> ($^S ? "True\n" : "False\n"); };
> eval { die };
> }
>
> print "Done\n";
> =====
>
> It prints:
> False
> Done
>
> Well, that, I understand.
Hmm, well, that's the one that doesn't quite make sense to me. Perl
isn't parsing that BEGIN block, it's running it, so I would expect $^S
to be true. (Defined because we're running code, true because we're
inside an eval{} so exceptions are being caught.)
> If I change eval { die } to eval 'die', it prints:
> Defined
> True
> Done
>
> Which I don't get.
>
> My only guess: since eval "" is described as a "little Perl program",
> $^S is set to 1 because it refers to the "running" part of the eval,
> after it has been successfully parsed. But, my "main" program is in
> compilation time, so it seems strange.
Yes, that's basically right. Not entirely right, since that would mean
the first example should have $^S true as well, but I suspect that's an
inconsistency or an accident of some kind.
You can have as many layers of BEGIN{}/eval"" as you like, each invoking
a new level of running-at-compile-time or compiling-at-runtime. I think
this covers all the important cases:
#!/usr/bin/perl
use 5.012;
sub st {
say "$_[0] ", defined $^S
? $^S ? "true" : "false"
: "undef";
}
BEGIN {
st "BEGIN";
eval { st "BEGIN eval{}" };
eval q{ st q/BEGIN eval""/ };
}
st "runtime";
eval { st "eval{}" };
eval q{
BEGIN { st q/eval"" BEGIN/ }
st q/eval""/;
};
and it gives
BEGIN undef
BEGIN eval{} undef
BEGIN eval"" true
runtime false
eval{} true
eval"" BEGIN undef
eval"" true
The BEGIN entries don't entirely make sense to me: I would have said,
before trying it, that you could only get $^S=undef during a __DIE__
handler handling an exception from a syntax error. That's certainly what
the documentation implies, not to mention the blue Camel.
If you have 5.14 you can use ${^GLOBAL_PHASE} to get the 'main'
interpreter state. On earlier perls you can use Devel::GlobalPhase to
emulate the core variable.
> Did I missed something about all that in the documentation?
Yes, you missed the bit in perlvar that says 'don't use $SIG{__DIE__} or
$^S' :). What are you actually trying to do here? There's probably an
easier way to do it.
Ben
------------------------------
Date: Mon, 3 Jun 2013 18:10:48 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: if you told everyone they can learn perl and skip high school.......
Message-Id: <83500c5b-2df9-4698-9ba5-7c25d384418f@googlegroups.com>
what would happen?
I would call it a net productivity gain for society!
------------------------------
Date: Tue, 04 Jun 2013 16:07:52 +0100
From: Dave Stratford <daves@orpheusmail.co.uk>
Subject: Is there a better way than this?
Message-Id: <535692806edaves@orpheusmail.co.uk>
Hi folks,
I've got a bit of code, three lines actually, that it seems to me ought to
be able to be done far simpler and better, but I can't see how.
Background first though.
A UK postcode is made up of two parts, outcode and incode. The incode has
a standard format: 9AA, that is, it's always three characters long, a
digit followed by two letters.
The Outcode however, has six possible formats, excluding some odd ones
that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and AA9A.
My requirements are to extract the initial letter(s) from the outcode. So
if a user entered HP13, I want to extract just the HP, equally if they
emtered WC1A, I want just the WC.
My current code, which works perfectly fine, looks like this:
my $oc = substr($outcode,0,2);
my $ocr = substr($oc,1,1);
$oc = substr($outcode,0,1) if ($ocr =~ /\d/);
So take the first two character, then see if the second one is a digit,
and if so take just the first character.
It works, it just seems to me that it ought to be simpler.
Any ideas please?
TIA,
Dave
--
Dave Stratford - ZFCB
http://daves.orpheusweb.co.uk/
------------------------------
Date: Tue, 4 Jun 2013 17:12:19 +0200
From: Helmut Richter <hhr-m@web.de>
Subject: Re: Is there a better way than this?
Message-Id: <alpine.LNX.2.00.1306041710050.6041@badwlrz-clhri01.ws.lrz.de>
On Tue, 4 Jun 2013, Dave Stratford wrote:
> My requirements are to extract the initial letter(s) from the outcode. So
> if a user entered HP13, I want to extract just the HP, equally if they
> emtered WC1A, I want just the WC.
>
> My current code, which works perfectly fine, looks like this:
>
> my $oc = substr($outcode,0,2);
> my $ocr = substr($oc,1,1);
>
> $oc = substr($outcode,0,1) if ($ocr =~ /\d/);
What about
$outcode =~ /^([A-Z]+)\d/;
$oc = $1;
--
Helmut Richter
------------------------------
Date: Tue, 04 Jun 2013 09:03:42 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Is there a better way than this?
Message-Id: <ej3sq8lnf33rtts1asjdiuk0en1ss1hiv8@4ax.com>
Dave Stratford <daves@orpheusmail.co.uk> wrote:
>The Outcode however, has six possible formats, excluding some odd ones
>that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and AA9A.
>
>My requirements are to extract the initial letter(s) from the outcode. So
>if a user entered HP13, I want to extract just the HP, equally if they
>emtered WC1A, I want just the WC.
>
>My current code, which works perfectly fine, looks like this:
>
> my $oc = substr($outcode,0,2);
> my $ocr = substr($oc,1,1);
> $oc = substr($outcode,0,1) if ($ocr =~ /\d/);
Trust the magic of REs (untested):
$outcode =~ /(\D*)/;
$oc = $1;
Or maybe
$outcode =~ /(\w*)/;
$oc = $1;
As long as the outcode is valid both variations should yield the same
result. Only if you have a non-valid code then they will return
different results.
jue
------------------------------
Date: Tue, 04 Jun 2013 19:00:53 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Is there a better way than this?
Message-Id: <87wqq9iwmi.fsf@sapphire.mobileactivedefense.com>
Helmut Richter <hhr-m@web.de> writes:
> On Tue, 4 Jun 2013, Dave Stratford wrote:
>
>> My requirements are to extract the initial letter(s) from the outcode. So
>> if a user entered HP13, I want to extract just the HP, equally if they
>> emtered WC1A, I want just the WC.
>>
>> My current code, which works perfectly fine, looks like this:
>>
>> my $oc = substr($outcode,0,2);
>> my $ocr = substr($oc,1,1);
>>
>> $oc = substr($outcode,0,1) if ($ocr =~ /\d/);
>
> What about
>
> $outcode =~ /^([A-Z]+)\d/;
> $oc = $1;
If the regex didn't match, $oc will now contain the value captured by
the last successful regex match before this line. This may not be a
problem in this case but in general, it is prudent to use the $n only when the
corresponding match was successful. Assuming that $oc is guaranteed to
be intially uninitialized, I would use something like
$outcode =~ /^([A-Z]{1,2})\d/ and $oc = $1; [*]
$oc will now have the correct value if outcode really started with one
or two letters followed by a digit. Depending on where the input came
from, [0-9] instead of \d might be a better choice as UK postcodes
certainly use arabic numerals but \d might match anything the Unicode
consortium considers a digit now or in future.
[*]
The obivious other way to write this is
($oc) = $outcode =~ /^([A-Z]{1,2})\d/;
------------------------------
Date: Tue, 4 Jun 2013 20:15:33 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Is there a better way than this?
Message-Id: <lvq18a-orn.ln1@anubis.morrow.me.uk>
Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>
> $oc will now have the correct value if outcode really started with one
> or two letters followed by a digit. Depending on where the input came
> from, [0-9] instead of \d might be a better choice as UK postcodes
> certainly use arabic numerals but \d might match anything the Unicode
> consortium considers a digit now or in future.
If you have 5.14 you can squash this particular bit of stupidity with
the /a switch. /\d/a, /\w/a and /\s/a all match what they used to in
5.6. (Except that I believe in 5.18 \s matches \v, that is, vertical
tab, both with and without /a.)
You can also turn on /a for all patterns in a lexical scope with
use re "/a";
> The obivious other way to write this is
>
> ($oc) = $outcode =~ /^([A-Z]{1,2})\d/;
I would consider this better style; there's no point mucking about with
magic globals if you don't need to.
Ben
------------------------------
Date: Tue, 4 Jun 2013 21:58:50 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Is there a better way than this?
Message-Id: <qgt18a-8d6.ln1@news.rtij.nl>
On Tue, 04 Jun 2013 09:03:42 -0700, Jürgen Exner wrote:
> Dave Stratford <daves@orpheusmail.co.uk> wrote:
>>The Outcode however, has six possible formats, excluding some odd ones
>>that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and
>>AA9A.
>>
>>My requirements are to extract the initial letter(s) from the outcode.
>>So if a user entered HP13, I want to extract just the HP, equally if
>>they emtered WC1A, I want just the WC.
>>
>>My current code, which works perfectly fine, looks like this:
>>
>> my $oc = substr($outcode,0,2);
>> my $ocr = substr($oc,1,1);
>> $oc = substr($outcode,0,1) if ($ocr =~ /\d/);
>
> Trust the magic of REs (untested):
> $outcode =~ /(\D*)/;
> $oc = $1;
>
> Or maybe
> $outcode =~ /(\w*)/;
> $oc = $1;
>
> As long as the outcode is valid both variations should yield the same
> result. Only if you have a non-valid code then they will return
> different results.
If validation is a concern (and it probably should be)
$outcode =~ /^(\w+)\d+\w*$/ or die "Invalid code";
$oc = $1;
Disclaimer, untested.
HTH,
M4
------------------------------
Date: Tue, 04 Jun 2013 15:01:35 -0700
From: Charles DeRykus <derykus@gmail.com>
Subject: Re: Is there a better way than this?
Message-Id: <kolo41$b62$1@speranza.aioe.org>
On 6/4/2013 8:07 AM, Dave Stratford wrote:
> Hi folks,
>
> I've got a bit of code, three lines actually, that it seems to me ought to
> be able to be done far simpler and better, but I can't see how.
>
> Background first though.
>
> A UK postcode is made up of two parts, outcode and incode. The incode has
> a standard format: 9AA, that is, it's always three characters long, a
> digit followed by two letters.
>
> The Outcode however, has six possible formats, excluding some odd ones
> that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and AA9A.
>
> My requirements are to extract the initial letter(s) from the outcode. So
> if a user entered HP13, I want to extract just the HP, equally if they
> emtered WC1A, I want just the WC.
>
> My current code, which works perfectly fine, looks like this:
>
> my $oc = substr($outcode,0,2);
> my $ocr = substr($oc,1,1);
>
> $oc = substr($outcode,0,1) if ($ocr =~ /\d/);
>
> So take the first two character, then see if the second one is a digit,
> and if so take just the first character.
>
> It works, it just seems to me that it ought to be simpler.
>
Another possibility:
($oc) = $outcode =~ /^ ([A-Z]+) (?=\d) /ax;
--
Charles DeRykus
------------------------------
Date: Tue, 4 Jun 2013 23:11:15 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Is there a better way than this?
Message-Id: <39528a-sop.ln1@anubis.morrow.me.uk>
Quoth Martijn Lievaart <m@rtij.nl.invlalid>:
> On Tue, 04 Jun 2013 09:03:42 -0700, Jürgen Exner wrote:
> > Dave Stratford <daves@orpheusmail.co.uk> wrote:
> >>The Outcode however, has six possible formats, excluding some odd ones
> >>that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and
> >>AA9A.
>
> If validation is a concern (and it probably should be)
>
> $outcode =~ /^(\w+)\d+\w*$/ or die "Invalid code";
> $oc = $1;
That won't work, since digits are included in \w. You would need
something more like
/^([A-Z]{1,2})[0-9]{1,2}[A-Z]? [0-9][A-Z]{2}/
You could also test that the 'W1A 1AA' format are valid London postal
districts, and indeed that the initial letters are a valid combination.
Ben
------------------------------
Date: Wed, 05 Jun 2013 10:46:29 +0100
From: Dave Stratford <daves@orpheusmail.co.uk>
Subject: Re: Is there a better way than this?
Message-Id: <5356f8ea00daves@orpheusmail.co.uk>
In article <39528a-sop.ln1@anubis.morrow.me.uk>,
Ben Morrow <ben@morrow.me.uk> wrote:
> Quoth Martijn Lievaart <m@rtij.nl.invlalid>:
> > On Tue, 04 Jun 2013 09:03:42 -0700, Jürgen Exner wrote:
> > > Dave Stratford <daves@orpheusmail.co.uk> wrote:
> > >>The Outcode however, has six possible formats, excluding some odd ones
> > >>that I know I won't have to worry about: A9, AA9, A99, AA9, A9A and
> > >>AA9A.
> >
> > If validation is a concern (and it probably should be)
> >
> > $outcode =~ /^(\w+)\d+\w*$/ or die "Invalid code";
> > $oc = $1;
> That won't work, since digits are included in \w. You would need
> something more like
> /^([A-Z]{1,2})[0-9]{1,2}[A-Z]? [0-9][A-Z]{2}/
> You could also test that the 'W1A 1AA' format are valid London postal
> districts, and indeed that the initial letters are a valid combination.
That's partly what this is about. We actually have a table with all the
letter parts, so we extract that from the outcode entered to validate.
Many thanks guys, I'll have a play with all the suggestions made and see
how they work.
Dave
--
Dave Stratford - ZFCB
http://daves.orpheusweb.co.uk/
------------------------------
Date: Sat, 1 Jun 2013 10:55:30 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: perl and openMPI vs noSQL crap
Message-Id: <d1d886f3-61fe-41dd-8494-b551e6c1b6c9@googlegroups.com>
can perl and openMPI or hek perl controlling a beowulf beat performance of these noSQL wanna be www.prevayerl.org apps becoming more populaR?
anyone running openMPI please post results
beowulf ++
------------------------------
Date: Sat, 1 Jun 2013 14:26:19 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: perl hey perl why oo but not functinal?
Message-Id: <8a4b381d-eef9-45bd-a3b5-e60c77f0717b@googlegroups.com>
wondring
------------------------------
Date: Sun, 02 Jun 2013 13:59:56 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: perl hey perl why oo but not functinal?
Message-Id: <87d2s4y8fn.fsf@sapphire.mobileactivedefense.com>
johannes falcone <visphatesjava@gmail.com> writes:
> wondring
The extremly simple answer is that the set of people who can write
useful/ working code is far larger than the set of people who can't
except when using a 'fat' emulation layer supposed to shield them from
real-world concepts such as complex objects whose state changes over
time which don't exist in 'mathetics'.
Unfortunately, the same people who spend their days preaching that
'statefulness' is inherently evil will won't mind eating dinners
cooked by someone else instead of demonstrating the supriority of
their theories by ... starving themselves to death.
------------------------------
Date: Sun, 02 Jun 2013 19:11:00 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: perl hey perl why oo but not functinal?
Message-Id: <87li6sqt6z.fsf@sapphire.mobileactivedefense.com>
Rainer Weikusat <rweikusat@mssgmbh.com> writes:
> johannes falcone <visphatesjava@gmail.com> writes:
>> wondring
>
> The extremly simple answer is that the set of people who can write
> useful/ working code is far larger than the set of people who can't
> except when using a 'fat' emulation layer supposed to shield them from
> real-world concepts such as complex objects whose state changes over
> time
Since this is sort-of an important topic: In the past, I used to know
a guy who - according to his e-mail address - worked for a German
university in some 'auxiliary teaching' role who liked to boast on
USENET that putting undergraduates through a course in functional
programming meant that people who already learnt to program in some
imperative language had an extremely hard time getting past that (I'm
not going to post his name here since it doesn't matter). He was
actually halfway convinced that no one could possibly be capable of
learning both.
In an ideal universe, the purpose of 'higher education' would be to
enable people to exploit their potentials, not to get rid of unwelcome
competitors for relatively well-paid and comfortable positions ...
------------------------------
Date: Mon, 3 Jun 2013 18:09:08 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: Re: perl hey perl why oo but not functinal?
Message-Id: <cd4b68cb-b5a7-4852-968e-ad5dcc9deda4@googlegroups.com>
> their theories by ... starving themselves to death.
I don't get it.
------------------------------
Date: Mon, 3 Jun 2013 18:09:34 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: Re: perl hey perl why oo but not functinal?
Message-Id: <d6ae5852-1eef-4649-9dd8-63b13a82d555@googlegroups.com>
> competitors for relatively well-paid and comfortable positions ...
so what? functional programming is bs?
------------------------------
Date: Mon, 3 Jun 2013 18:10:05 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: Re: so how much money do perl programmers make?
Message-Id: <6582bc06-9f50-4c64-90b4-1a434510d6a9@googlegroups.com>
> the avverage is 81,000
weak
I make 75/h
------------------------------
Date: Sat, 1 Jun 2013 10:52:40 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: Re: starman fastest perl web server?
Message-Id: <76d07d8b-73c4-4ba7-a858-09c5cba828bb@googlegroups.com>
anyone compare vs an epoll kquee server like perlbal?
------------------------------
Date: Tue, 4 Jun 2013 18:25:20 -0700 (PDT)
From: Gerardo D <davidgerardomx@gmail.com>
Subject: unzip Zip file in a remote drive
Message-Id: <e4007ee1-cbbb-4020-b374-5d463c3d6deb@googlegroups.com>
Hi all,
I would like to know in Perl how to unzip a zip file thru 7 zip where origin is a local drive and destiny is a remote drive something like this:
7z e c:\temp\file.zip -o \\190.150.123.1\temp
Any thoughts?
Thanks
------------------------------
Date: Tue, 04 Jun 2013 19:48:31 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: unzip Zip file in a remote drive
Message-Id: <ck9tq85e576gmjb3nm57us4ba7t5m900je@4ax.com>
Gerardo D <davidgerardomx@gmail.com> wrote:
>I would like to know in Perl how to unzip a zip file thru 7 zip where origin is a local drive and destiny is a remote drive something like this:
[Please limit your line length to approx 74 characters as has been
proven Usenet custom for over 2 decades. Thank you]
There are numerous modules on CPAN regarding ZIP management, see
http://search.cpan.org/search?query=zip&mode=module
jue
------------------------------
Date: Wed, 5 Jun 2013 14:10:55 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: unzip Zip file in a remote drive
Message-Id: <vvp38a-6dj.ln1@anubis.morrow.me.uk>
Quoth Gerardo D <davidgerardomx@gmail.com>:
>
> I would like to know in Perl how to unzip a zip file thru 7 zip where
> origin is a local drive and destiny is a remote drive something like
> this:
>
> 7z e c:\temp\file.zip -o \\190.150.123.1\temp
(Do you really have neither DNS nor Netbios name resolution?)
If you actually need to run 7z (say, because you're unzipping a .7z
file) you use system(). The question of local or remote drives is
irrelevant: they're just arguments to 7z. Be careful about backslashes,
though: even in a single-quoted string, you have to double them.
As Jue says, if you're dealing with an ordinary (pkzip) zip file, you
would be better off using one of the Perl modules. You can specify a UNC
path in Perl just like any other path; you can also use forward slashes
instead of backslashes, which makes the string handling easier.
Ben
------------------------------
Date: Sat, 1 Jun 2013 12:55:39 -0700 (PDT)
From: johannes falcone <visphatesjava@gmail.com>
Subject: why all this queue stuff in the java world lately?
Message-Id: <dce5851e-bc40-4305-8c6c-e5cb24dfc01b@googlegroups.com>
I know hornetq embeds eralng
but what up with al this queue stuff??
------------------------------
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 3959
***************************************
