[32472] in Perl-Users-Digest
Perl-Users Digest, Issue: 3737 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jul 18 06:09:08 2012
Date: Wed, 18 Jul 2012 03:09:05 -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, 18 Jul 2012 Volume: 11 Number: 3737
Today's topics:
easiest way to set $1 $2 $3... jidanni@jidanni.org
Re: easiest way to set $1 $2 $3... <NoSpamPleaseButThisIsValid3@gmx.net>
Learning XML::LibXML::XPathContext <rodbass63@gmail.com>
Re: LibXML element->toString vs document->toString (Seymour J.)
Re: LibXML element->toString vs document->toString <ben@morrow.me.uk>
Re: LibXML element->toString vs document->toString (Fergus McMenemie)
Re: LibXML element->toString vs document->toString (Fergus McMenemie)
Overriding and extending the given/when construct <klaus03@gmail.com>
Re: Overriding and extending the given/when construct <ben@morrow.me.uk>
Re: Overriding and extending the given/when construct <klaus03@gmail.com>
Re: Overriding and extending the given/when construct <ben@morrow.me.uk>
Re: Regex: match double OR single quote <cartercc@gmail.com>
Re: Regex: match double OR single quote <jwcarlton@gmail.com>
Re: Regex: match double OR single quote <ben@morrow.me.uk>
Stupid regex problem, s/// catching extra letter <jwcarlton@gmail.com>
Re: Stupid regex problem, s/// catching extra letter <thepoet_nospam@arcor.de>
Re: Stupid regex problem, s/// catching extra letter <jwcarlton@gmail.com>
Re: Why Lisp macros are cool, a Perl perspective (2005) <cartercc@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 18 Jul 2012 17:25:03 +0800
From: jidanni@jidanni.org
Subject: easiest way to set $1 $2 $3...
Message-Id: <ju5vf7$ah$1@news.datemas.de>
In /bin/sh it merely takes a
$ set a b c
to set $1 $2 $3.
So what is the easiest way to do the same in perl?
Yes in perl they are related to regexps. No don't ask me why I want to
set them, Just pretend I need to use them on the next line and want to
try some different values.
If it takes more than just a one-liner, then perl has problems.
$ perl -wle '"abc" =~ /(.)(.)(.)/; print $1, $2, $3;'
abc
Big drag.
So we see on perlvar there is no array that can give us even read-only
access to
$<digits> ($1, $2, ...)
not of course even to think of an easy way to set them by all directly by hand
if we need to.
Well maybe perlvar should mention what the best way so-far to access
them all (like /bin/sh's $@, $*), and set them all (like /bin/sh's set) is!
------------------------------
Date: Wed, 18 Jul 2012 11:58:11 +0200
From: Wolf Behrenhoff <NoSpamPleaseButThisIsValid3@gmx.net>
Subject: Re: easiest way to set $1 $2 $3...
Message-Id: <500688b4$0$9522$9b4e6d93@newsspool1.arcor-online.net>
Am 18.07.2012 11:25, schrieb jidanni@jidanni.org:
> In /bin/sh it merely takes a
> $ set a b c
> to set $1 $2 $3.
>
> So what is the easiest way to do the same in perl?
>
> Yes in perl they are related to regexps. No don't ask me why I want to
> set them, Just pretend I need to use them on the next line and want to
> try some different values.
I do ask: why would you want to do that? Just put different values in
the next line?
> If it takes more than just a one-liner, then perl has problems.
Don't understand!
> So we see on perlvar there is no array that can give us even read-only
> access to
> $<digits> ($1, $2, ...)
> not of course even to think of an easy way to set them by all directly by hand
> if we need to.
There are @+ and @- and (it is in pervar)
$1 is the same as "substr($var, $-[1], $+[1] - $-[1])"
$2 is the same as "substr($var, $-[2], $+[2] - $-[2])"
and so on.
- Wolf
------------------------------
Date: Sun, 15 Jul 2012 20:05:40 -0700 (PDT)
From: Nene <rodbass63@gmail.com>
Subject: Learning XML::LibXML::XPathContext
Message-Id: <3acd4e96-3398-480c-bead-2195cf75afe9@googlegroups.com>
Hi,
I'm learning this module today and I'm getting 'invalid expression' every time I run it. The error seems to be related to my syntax/code rather than the contents of the test.xml file. Any help would be greatly appreciated, thank you in advance.
#!/usr/local/bin/perl
use warnings;
use Data::Dumper;
use XML::LibXML;
my $parser = XML::LibXML->new();
my $xc = $parser->parse_file("test.xml");
my $xpc = XML::LibXML::XPathContext->new($xc);
my @x = $xpc->find('/Something//Child::*');
------------------------------
Date: Sat, 14 Jul 2012 22:28:22 -0400
From: Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid>
Subject: Re: LibXML element->toString vs document->toString
Message-Id: <50022ac6$3$fuzhry+tra$mr2ice@news.patriot.net>
In <l906d9-niu2.ln1@anubis.morrow.me.uk>, on 07/13/2012
at 05:51 PM, Ben Morrow <ben@morrow.me.uk> said:
>It can certainly be difficult, given that Usenet officially doesn't
>support anything but ASCII.
What gives you that idea? RFC 5536 explicitly allows MIME-encoded
data, e.g.,
1.2. Scope
This document specifies the syntax of Netnews articles in the
context
of the Internet Message Format [RFC5322] and Multipurpose Internet
Mail Extensions (MIME) [RFC2045]. This document obsoletes
[RFC1036],
2.2. Header Fields
o The character set for header fields is US-ASCII. Where the
use of non-ASCII characters is required, they MUST be encoded
using the MIME mechanisms defined in [RFC2047] and [RFC2231].
2.3. MIME Conformance
User agents MUST meet the definition of MIME conformance in
[RFC2049]
and MUST also support [RFC2231]. This level of MIME conformance
provides support for internationalization and multimedia in message
bodies [RFC2045], [RFC2046], and [RFC2231], and support for
internationalization of header fields [RFC2047] and [RFC2231].
Note
that [Errata] currently exist for [RFC2045], [RFC2046], [RFC2047]
and
[RFC2231].
3.2. Optional Header Fields
The MIME header fields MIME-Version, Content-Type,
Content-Transfer-
Encoding, Content-Disposition, and Content-Language are used in
Netnews articles in the same circumstances and with the same
meanings
as those specified in [RFC2045], [RFC2183], and [RFC3282], with the
added restrictions detailed above in Section 2.2.
4. Internationalization Considerations
Internationalization of Netnews article header fields and bodies is
provided using the MIME mechanisms discussed in Section 2.3. Note
that the generation of internationalized <newsgroup-name>s for use
in
header fields is not addressed in this document.
Now, admittedly there's still a lot of software written to RFC 1036
and son-of-1036, but 5536 is a few years old and is on the standards
track, so I officially MIME is allowed.
> Unofficially, if you can get your newsreader to produce it,
>articles in UTF-8 with 'Content-type: text/plain; charset=UTF-8'
>seem to work perfectly well.
Not just defacto but de jure; see above for what is officially
allowed.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>
Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spamtrap@library.lspace.org
------------------------------
Date: Sun, 15 Jul 2012 23:02:45 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: LibXML element->toString vs document->toString
Message-Id: <59rbd9-e1v2.ln1@anubis.morrow.me.uk>
Quoth Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid>:
> In <l906d9-niu2.ln1@anubis.morrow.me.uk>, on 07/13/2012
> at 05:51 PM, Ben Morrow <ben@morrow.me.uk> said:
>
> >It can certainly be difficult, given that Usenet officially doesn't
> >support anything but ASCII.
>
> What gives you that idea? RFC 5536 explicitly allows MIME-encoded
> data, e.g.,
Ooh, they've actually published an update. I didn't know that.
Ben
------------------------------
Date: Tue, 17 Jul 2012 07:21:11 +0100
From: fergus@twig-me-uk.not.here (Fergus McMenemie)
Subject: Re: LibXML element->toString vs document->toString
Message-Id: <1knd7af.1e602xit3x7eN%fergus@twig-me-uk.not.here>
Ben Morrow <ben@morrow.me.uk> wrote:
> > What gives you that idea? RFC 5536 explicitly allows MIME-encoded
> > data, e.g.,
>
> Ooh, they've actually published an update. I didn't know that.
My newsreader does not properly upport UTF8 I guess lots of others still
dont either.
MacSoup - my soups gone off!
------------------------------
Date: Tue, 17 Jul 2012 07:21:13 +0100
From: fergus@twig-me-uk.not.here (Fergus McMenemie)
Subject: Re: LibXML element->toString vs document->toString
Message-Id: <1knd7dr.1yquoexuj7i9sN%fergus@twig-me-uk.not.here>
Ben Morrow <ben@morrow.me.uk> wrote:
> Yes, it works as documented for me. Are you getting confused by the fact
> that ->toString produces a byte string for whole documents, but a
> character string for just an element? Read the 'ENCODINGS SUPPORT'
> section in perldoc XML::LibXML: you don't want a :utf8 layer if you're
> printing a whole document, because the document isn't necessarily in
> UTF-8.
Duh!
Thanks I dont know how I managed to miss that bit.
------------------------------
Date: Mon, 16 Jul 2012 13:34:49 -0700 (PDT)
From: Klaus <klaus03@gmail.com>
Subject: Overriding and extending the given/when construct
Message-Id: <c0442033-4114-4f30-a620-04119a41ae9e@e20g2000vbm.googlegroups.com>
Hello everybody
I want to write a CPAN module that overrides / extends the given/when
construct.
I am a Perl programmer with a little knowledge of C, but no knowledge
of XS,
Is there any documentation (perldoc, blogs, documents on the internet,
etc...) that could start me off writing a given/when extension on
CPAN ? (I prefer a pure perl aproach, but I am willing to learn XS if
needed).
Thanks.
-- Klaus
------------------------------
Date: Mon, 16 Jul 2012 23:36:55 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Overriding and extending the given/when construct
Message-Id: <7lhed9-ipa.ln1@anubis.morrow.me.uk>
Quoth Klaus <klaus03@gmail.com>:
>
> I want to write a CPAN module that overrides / extends the given/when
> construct.
>
> I am a Perl programmer with a little knowledge of C, but no knowledge
> of XS,
>
> Is there any documentation (perldoc, blogs, documents on the internet,
> etc...) that could start me off writing a given/when extension on
> CPAN ? (I prefer a pure perl aproach, but I am willing to learn XS if
> needed).
How, exactly, do you want to extend it? For some cases, creating a class
with an overloaded ~~ operator will be sufficient. Otherwise, I would
strongly recommend finding some other way of doing whatever you're
trying to do: smartmatch is hairy enough as it is, without adding more.
Ben
------------------------------
Date: Mon, 16 Jul 2012 16:56:07 -0700 (PDT)
From: Klaus <klaus03@gmail.com>
Subject: Re: Overriding and extending the given/when construct
Message-Id: <39202ae4-72fa-471d-adae-38b9742cd3f5@f30g2000vbz.googlegroups.com>
On 17 juil, 00:36, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth Klaus <klau...@gmail.com>:
> > I want to write a CPAN module that overrides / extends the given/when
> > construct.
>
> > I am a Perl programmer with a little knowledge of C, but no knowledge
> > of XS,
>
> > Is there any documentation (perldoc, blogs, documents on the internet,
> > etc...) that could start me off writing a given/when extension on
> > CPAN ? (I prefer a pure perl aproach, but I am willing to learn XS if
> > needed).
>
> How, exactly, do you want to extend it?
I want to add a qualifier to "when()" (i.e. when true (...), when eq
(...), when == (...)) as described in a post on perl5.porters
http://groups.google.com/group/perl.perl5.porters/msg/c0ee23905fe59030?hl=fr
given( $foo ) {
when true ($_ eq 'abc') { blah } ;
# evaluates condition as is
when true (/regex/) { blah } ;
# translates naturally into $_ =~/regex/
when eq ('str1', 'str2') { blah } ;
# translates into $_ in ('str1', 'str2'), which
# translates into $_ eq 'str1' or $_ eq 'str2'
when eq ('str1') { blah } ;
# translates into $_ in ('str1'), which
# translates into $_ eq 'str1'
when == (4, 5) { blah } ;
# translates into $_ in_== (4, 5), which
# translates into $_ == 4 or $_ == 5
when == (4) { blah } ;
# translates into $_ in_== (4), which
# translates into $_ == 4
> For some cases, creating a class
> with an overloaded ~~ operator will be sufficient. Otherwise, I would
> strongly recommend finding some other way of doing whatever you're
> trying to do: smartmatch is hairy enough as it is, without adding more.
I don't want to overload smartmatch, but I need to implement the new
operators "in" and "in_==" as follows:
$var in ('str1', 'str2') is equivalent to $var eq 'str1' or $vat eq
'str2'
$var in_== (4,5) is equivalent to $var == 4 or $var == 5
-- Klaus
------------------------------
Date: Tue, 17 Jul 2012 13:12:06 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Overriding and extending the given/when construct
Message-Id: <md1gd9-9mi.ln1@anubis.morrow.me.uk>
Quoth Klaus <klaus03@gmail.com>:
> On 17 juil, 00:36, Ben Morrow <b...@morrow.me.uk> wrote:
> > Quoth Klaus <klau...@gmail.com>:
> > > I want to write a CPAN module that overrides / extends the given/when
> > > construct.
> >
> > > I am a Perl programmer with a little knowledge of C, but no knowledge
> > > of XS,
> >
> > > Is there any documentation (perldoc, blogs, documents on the internet,
> > > etc...) that could start me off writing a given/when extension on
> > > CPAN ? (I prefer a pure perl aproach, but I am willing to learn XS if
> > > needed).
> >
> > How, exactly, do you want to extend it?
>
> I want to add a qualifier to "when()" (i.e. when true (...), when eq
> (...), when == (...)) as described in a post on perl5.porters
> http://groups.google.com/group/perl.perl5.porters/msg/c0ee23905fe59030?hl=fr
>
> given( $foo ) {
> when true ($_ eq 'abc') { blah } ;
> # evaluates condition as is
> when true (/regex/) { blah } ;
> # translates naturally into $_ =~/regex/
> when eq ('str1', 'str2') { blah } ;
> # translates into $_ in ('str1', 'str2'), which
> # translates into $_ eq 'str1' or $_ eq 'str2'
There are four possible approaches to something like this:
- A core patch (in C and yacc). This would require consensus on p5p,
which is unlikely to happen. There has been enough mucking around
with the semantics of ~~/given/when already, and this proposal has
already been made and, presumably, rejected.
- A source filter, in Perl or XS. This is how Switch was implemented
in the old days, and it was perennially unreliable due to the
inherent difficulty of parsing Perl without using the perl parser.
- A Devel::Declareish PL_check hook (in XS). This requires an
intimate knowledge of the details of the perl parsing process,
and, while the potential damage is likely to be more limited,
still suffers from the source filter problem. It's possible some
of the new lexer APIs might help with that.
- Zefram's new lexer/parser API, using PL_keyword_plugin and the
PLUGSTMT rule in perly.y (in XS). I haven't really looked into
this, so I don't know whether it could do what you want, but I
believe this is the sort of thing it was *intended* to make
possible. This would, again, require that you learn a great deal
about the details of the perl parser and the optree building
process.
More generally, what does this do for you that can't be done better with
if/elsif? Defining appropriate subs to allow
if ($foo eq "abc") { ... }
elsif ($foo =~ /regex/) { ... }
elsif (in $foo, qw/1 2 3/) { ... }
elsif (in_eq $foo, qw/str1 str2/) { ... }
elsif (in_rx $foo, qr/x/, qr/y/) { ... }
would seem like a much more sensible approach to me. In fact,
List::MoreUtils::any is already pretty close, though a little verbose.
Ben
------------------------------
Date: Mon, 16 Jul 2012 10:20:07 -0700 (PDT)
From: ccc31807 <cartercc@gmail.com>
Subject: Re: Regex: match double OR single quote
Message-Id: <ac79b28e-8d01-4ba0-89f3-fbbc1fafbaa6@j4g2000yqj.googlegroups.com>
On Jul 12, 6:12=A0pm, Jason C <jwcarl...@gmail.com> wrote:
> I'm struggling with what I thought was a simple thing, and I'm hoping you=
guys can help.
>
> I have a string that may contain a ", ', or neither. So, I wrote this in =
the regex:
If you process CSV files, this can get real hairy. CSV files can
contain one or more double quotes, one or more single quotes, pairs of
double and/or single quotes, and commas embedded within quotation
marks. The best help, and one that I strongly recommend to you, is to
examine the Perl source for one or more of the CSV modules. The
contain regular expressions for dis-entangling CSV strings, and trying
to understand how they work will strengthen your RE chops.
I normally follow two strategies when faced with this situation.
First, is to replace all non-delimiting or non-qulaifying quotation
marks with some unusual character that's unlikely to appear in the
string, such as
s/["']/#/g
and then later, after I've processed the string, reverse the change
like this
s\s/#/'/g
which converts all the quotations to single quotes, which may or may
not work for you (it normally works for me).
Or, I escape the quotations with either single or double backslashes,
depending on whatever subsequent processing you plan to do, like this
s/(["'])/\$1/g
This has the advantage of preserving the kinds of quotes.
I'm posting from memory so the above might have errors, but you
understand the idea.
In practice, I find that single quotes turn up in the oddest places,
where you would never expect them. For this reason, when I process a
string, out of pure defensiveness, I usually escape quotes (as well as
some other potentially trouble makers).
CC
------------------------------
Date: Tue, 17 Jul 2012 21:12:26 -0700 (PDT)
From: Jason C <jwcarlton@gmail.com>
Subject: Re: Regex: match double OR single quote
Message-Id: <73754bd3-8ff8-498c-b370-cfc7d939dc9f@googlegroups.com>
On Friday, July 13, 2012 5:49:03 AM UTC-4, Ben Morrow wrote:
> > > $text =~ s{
> > > &lt;img ([^&gt;]*) src=[&quot;&#39;] \s*
> ^^^^ ^^^^ ^^^^^^^^^^^
> If you're going to be posting to programming newsgroups you need to find
> a way to stop that from happening. Dropping Google in favour of a real
> newsreader might be a good start.
Blech, why did Google start doing that?? I really don't use NG's that often, but those substitutions sure make it hard to talk about regex!
I guess I'll have to grab a copy of Forte Agent or something...
> 'Optional' is ?, not *. Presumably you don't want to allow
Maybe I really am confused. Regex isn't really my strong point, though, so I appreciate the clarification.
I thought that ? made it not greedy; meaning, instead of catching the next reference, it would find the last reference.
Example:
$text = "Example >->->";
$text = s/>?//;
would return:
Example ->->
But this:
$text = "Example >->->";
$text = s/>//;
would return:
Example --
Then, I thought that * meant "0 or more times", which would essentially make it optional?
------------------------------
Date: Wed, 18 Jul 2012 09:25:37 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Regex: match double OR single quote
Message-Id: <1h8id9-v121.ln1@anubis.morrow.me.uk>
Quoth Jason C <jwcarlton@gmail.com>:
> On Friday, July 13, 2012 5:49:03 AM UTC-4, Ben Morrow wrote:
>
> > 'Optional' is ?, not *. Presumably you don't want to allow
>
> Maybe I really am confused. Regex isn't really my strong point, though,
> so I appreciate the clarification.
>
> I thought that ? made it not greedy; meaning, instead of catching the
> next reference, it would find the last reference.
? does sometimes make something not greedy, but that isn't what 'not
greedy' means.
Suppose I have a section of pattern, A. Then
/A/ matches A once
/A?/ matches A 0-or-1 times
/A*/ matches A 0-or-more times
/A+/ matches A 1-or-more times
Greedyness controls what to do when there is a choice about how many
times to match. The greedy quantifiers above will all match as much as
possible whenever there's a choice. These non-greedy quantifiers:
/A??/ matches A 0-or-1 times, not greedy
/A*?/ matches A 0-or-more times, not greedy
/A+?/ matches A 1-or-more times, not greedy
will all instead match as *little* as possible.
> Then, I thought that * meant "0 or more times", which would essentially
> make it optional?
Well, yes, in a sense. 'Optional' is ambiguous; in this case, as I said,
I believe you want 0-or-1-times rather than 0-or-more-times.
Ben
------------------------------
Date: Tue, 17 Jul 2012 21:01:58 -0700 (PDT)
From: Jason C <jwcarlton@gmail.com>
Subject: Stupid regex problem, s/// catching extra letter
Message-Id: <822b6b4c-b75b-46fc-adac-36d86846e5fc@googlegroups.com>
I know better than to work late at night, but sometimes it just can't be helped :-)
I'm doing a simple s///, converting "www." to "http://www." when "www." occurs without a preceding "http://". Here's what I'm doing:
$text = "www.example.com";
$text =~ s#[^(http://)]www\.#http://www\.#gi;
print $text;
If $text is this, though:
$text = "<div>www.example.com</div>";
the regex is catching the > in <div>, printing:
<divhttp://www.example.com</div>
Where am I screwing up?
------------------------------
Date: Wed, 18 Jul 2012 06:57:00 +0200
From: Christian Winter <thepoet_nospam@arcor.de>
Subject: Re: Stupid regex problem, s/// catching extra letter
Message-Id: <5006421e$0$9505$9b4e6d93@newsspool1.arcor-online.net>
Am 18.07.2012 06:01, schrieb Jason C:
> I know better than to work late at night, but sometimes it just can't be helped :-)
>
> I'm doing a simple s///, converting "www." to "http://www."
> when "www." occurs without a preceding "http://". Here's what I'm doing:
>
> $text = "www.example.com";
> $text =~ s#[^(http://)]www\.#http://www\.#gi;
> print $text;
>
> If $text is this, though:
>
> $text = "<div>www.example.com</div>";
>
> the regex is catching the > in <div>, printing:
>
> <divhttp://www.example.com</div>
>
> Where am I screwing up?
You don't want to use a character class (square brackets).
[^(http://)] tells perl to look for any character not listed
inside the square brackets after the negation (^), so this
might as well read [^)(/:hpt].
What you're trying to do is a zero width negative look-behind
assertion.
s#(?<!http://)www\.#http://www.#gi should do the trick.
The "(?<!...)" tells the regex engine to only match the following
pattern if it is not preceded by the pattern in the look-behind,
without capturing anything.
"perldoc perlre" has good explanations for character classes
and look-around assertions.
-Chris
------------------------------
Date: Tue, 17 Jul 2012 22:05:20 -0700 (PDT)
From: Jason C <jwcarlton@gmail.com>
Subject: Re: Stupid regex problem, s/// catching extra letter
Message-Id: <b043f839-eb7b-45ff-aea1-0aee5d78a1f4@googlegroups.com>
On Wednesday, July 18, 2012 12:57:00 AM UTC-4, thepoet wrote:
> What you're trying to do is a zero width negative look-behind
> assertion.
> s#(?<!http://)www\.#http://www.#gi should do the trick.
> The "(?<!...)" tells the regex engine to only match the following
> pattern if it is not preceded by the pattern in the look-behind,
> without capturing anything.
>
> "perldoc perlre" has good explanations for character classes
> and look-around assertions.
>
> -Chris
Thanks for the help, Chris. Character classes aren't exactly intuitive when a symbol changes definition completely based on context, so I'm still struggling with that a little.
The modification you suggested was perfect, though! Thanks again :-)
------------------------------
Date: Mon, 16 Jul 2012 10:22:08 -0700 (PDT)
From: ccc31807 <cartercc@gmail.com>
Subject: Re: Why Lisp macros are cool, a Perl perspective (2005)
Message-Id: <a4d7eafd-3734-45f6-87e3-cc41f023af2d@e37g2000yqn.googlegroups.com>
On Jul 15, 1:19=A0am, Steve Graham <jsgraha...@yahoo.com> wrote:
> http://lists.warhead.org.uk/pipermail/iwe/2005-July/000130.html
cross posted to clpm
------------------------------
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 3737
***************************************
