[32604] in Perl-Users-Digest
Perl-Users Digest, Issue: 3877 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Feb 9 09:09:30 2013
Date: Sat, 9 Feb 2013 06:09:08 -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 Sat, 9 Feb 2013 Volume: 11 Number: 3877
Today's topics:
Re: A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages <news@lawshouse.org>
Re: A little help with Perl & Email Messages <ben@morrow.me.uk>
Re: A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages <news@lawshouse.org>
Re: A little help with Perl & Email Messages <ben@morrow.me.uk>
Re: help with regexp <marc.girod@gmail.com>
Re: help with regexp <marc.girod@gmail.com>
Re: help with regexp <ben@morrow.me.uk>
Re: help with regexp <marc.girod@gmail.com>
Re: help with regexp <ben@morrow.me.uk>
Parsing Process Log files - looking for Perl Modules <sssdevelop@gmail.com>
Re: Parsing Process Log files - looking for Perl Module <news@lawshouse.org>
Re: taking a look at some examples of web automation sc <cal@example.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 7 Feb 2013 12:26:28 -0800 (PST)
From: artmerar@gmail.com
Subject: Re: A little help with Perl & Email Messages
Message-Id: <40623463-bb96-4134-bdc6-bbaa625e43f1@googlegroups.com>
On Thursday, February 7, 2013 10:42:41 AM UTC-6, Henry Law wrote:
> On 07/02/13 16:27, artmerar@gmail.com wrote:
>
> >
>
> > That does work, but is there a way to get rid of all the header information:
>
> >
>
> > Here is the subject: 'TEST'.
>
> > ------BODY-------
>
> > This is a multipart message in MIME format.
>
> >
>
> > ------=_NextPart_000_12F3_01CE045C.72E20340
>
> > Content-Type: text/plain;
>
> > charset="us-ascii"
>
> > Content-Transfer-Encoding: 7bit
>
>
>
> If it's in MIME format then you need Email::MIME. It extends
>
> Email::Simple to allow you to separate the different MIME parts, and
>
> fiddle around with their Content-Type and Transfer-Encoding and so
>
> forth. It will also (as I recall) return the body (with or without
>
> decoding), which presumably is what you want.
>
>
>
> Please have a go at that -- write some code -- and if it doesn't do what
>
> you expect then you can get help here.
>
>
>
> --
>
>
>
> Henry Law Manchester, England
Henry,
Thanks for the pointer. It is almost working, but still have the MIME content:
my $txt;
$txt .= $_ while <>;
my $parsed = Email::MIME->new($txt);
my $decoded = $parsed->body;
my $non_decoded = $parsed->body_raw;
print "DECODED: $decoded\n";
print "NON: $non_decoded\n";
DECODED: This is a multipart message in MIME format.
NON: This is a multipart message in MIME format.
------=_NextPart_000_1500_01CE053E.2ADE0E30
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
STUFF
MORE STUFF
------=_NextPart_000_1500_01CE053E.2ADE0E30
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------------------------------
Date: Thu, 07 Feb 2013 20:47:13 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <J7CdnXrVV8VOj4nMnZ2dnUVZ8gmdnZ2d@giganews.com>
On 07/02/13 20:26, artmerar@gmail.com wrote:
> Thanks for the pointer. It is almost working, but still have the MIME content:
>
> my $txt;
> $txt .= $_ while <>;
>
> my $parsed = Email::MIME->new($txt);
> my $decoded = $parsed->body;
> my $non_decoded = $parsed->body_raw;
>
> print "DECODED: $decoded\n";
> print "NON: $non_decoded\n";
>
>
> DECODED: This is a multipart message in MIME format.
>
>
> NON: This is a multipart message in MIME format.
>
> ------=_NextPart_000_1500_01CE053E.2ADE0E30
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
<snipped>
It is working perfectly. Look up the structure of multipart MIME
messages and read the documentation.
Hint: you'll find some help in the third line of the code snippet in the
Synopsis section of the perldoc for Email::MIME. There's another broad
hint in the section describing the "body" method.
--
Henry Law Manchester, England
------------------------------
Date: Thu, 7 Feb 2013 20:47:41 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <dggdu9-8vl2.ln1@anubis.morrow.me.uk>
Quoth artmerar@gmail.com:
> On Thursday, February 7, 2013 10:42:41 AM UTC-6, Henry Law wrote:
> > On 07/02/13 16:27, artmerar@gmail.com wrote:
> >
> > >
> >
One more chance: STOP DOING THAT.
> > If it's in MIME format then you need Email::MIME. It extends
> > Email::Simple to allow you to separate the different MIME parts, and
> > fiddle around with their Content-Type and Transfer-Encoding and so
> > forth. It will also (as I recall) return the body (with or without
> > decoding), which presumably is what you want.
> >
> > Please have a go at that -- write some code -- and if it doesn't do what
> > you expect then you can get help here.
>
> Henry,
>
> Thanks for the pointer. It is almost working, but still have the MIME
> content:
>
> my $txt;
> $txt .= $_ while <>;
>
> my $parsed = Email::MIME->new($txt);
> my $decoded = $parsed->body;
> my $non_decoded = $parsed->body_raw;
>
> print "DECODED: $decoded\n";
> print "NON: $non_decoded\n";
>
>
> DECODED: This is a multipart message in MIME format.
>
>
> NON: This is a multipart message in MIME format.
>
> ------=_NextPart_000_1500_01CE053E.2ADE0E30
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
Go and read RFCs 2045-9 until you understand how MIME works. Then come
back and look at how to use Email::MIME to do what you want. (I'll give
you a hint: it's not as easy as you think.)
Ben
------------------------------
Date: Thu, 7 Feb 2013 22:17:35 -0800 (PST)
From: artmerar@gmail.com
Subject: Re: A little help with Perl & Email Messages
Message-Id: <897bc860-c638-4033-8f6c-950aaec08ed2@googlegroups.com>
On Thursday, February 7, 2013 2:47:13 PM UTC-6, Henry Law wrote:
> On 07/02/13 20:26, artmerar@gmail.com wrote:
>
> > Thanks for the pointer. It is almost working, but still have the MIME content:
>
> >
>
> > my $txt;
>
> > $txt .= $_ while <>;
>
> >
>
> > my $parsed = Email::MIME->new($txt);
>
> > my $decoded = $parsed->body;
>
> > my $non_decoded = $parsed->body_raw;
>
> >
>
> > print "DECODED: $decoded\n";
>
> > print "NON: $non_decoded\n";
>
> >
>
> >
>
> > DECODED: This is a multipart message in MIME format.
>
> >
>
> >
>
> > NON: This is a multipart message in MIME format.
>
> >
>
> > ------=_NextPart_000_1500_01CE053E.2ADE0E30
>
> > Content-Type: text/plain;
>
> > charset="us-ascii"
>
> > Content-Transfer-Encoding: 7bit
>
> <snipped>
>
>
>
> It is working perfectly. Look up the structure of multipart MIME
>
> messages and read the documentation.
>
>
>
> Hint: you'll find some help in the third line of the code snippet in the
>
> Synopsis section of the perldoc for Email::MIME. There's another broad
>
> hint in the section describing the "body" method.
>
>
>
> --
>
>
>
> Henry Law Manchester, England
Thanks for all the pointers Henry. I did the reading and changed the code. Looking at the @parts array, it contains some hashes:
PARTS: Email::MIME=HASH(0x16465de0) Email::MIME=HASH(0x164660c0)
I looked at the content type and got this:
CONTENT: multipart/alternative; boundary="----=_NextPart_000_1574_01CE0591.17983190"
Still looking to get just the text, but making some slow progress. This stuff is a bit more complex than I originally thought.
------------------------------
Date: Fri, 8 Feb 2013 10:37:42 -0800 (PST)
From: artmerar@gmail.com
Subject: Re: A little help with Perl & Email Messages
Message-Id: <6b5008b3-a7d8-4646-9038-51be25831db2@googlegroups.com>
On Thursday, February 7, 2013 2:47:13 PM UTC-6, Henry Law wrote:
> On 07/02/13 20:26, artmerar@gmail.com wrote:
>
> > Thanks for the pointer. It is almost working, but still have the MIME content:
>
> >
>
> > my $txt;
>
> > $txt .= $_ while <>;
>
> >
>
> > my $parsed = Email::MIME->new($txt);
>
> > my $decoded = $parsed->body;
>
> > my $non_decoded = $parsed->body_raw;
>
> >
>
> > print "DECODED: $decoded\n";
>
> > print "NON: $non_decoded\n";
>
> >
>
> >
>
> > DECODED: This is a multipart message in MIME format.
>
> >
>
> >
>
> > NON: This is a multipart message in MIME format.
>
> >
>
> > ------=_NextPart_000_1500_01CE053E.2ADE0E30
>
> > Content-Type: text/plain;
>
> > charset="us-ascii"
>
> > Content-Transfer-Encoding: 7bit
>
> <snipped>
>
>
>
> It is working perfectly. Look up the structure of multipart MIME
>
> messages and read the documentation.
>
>
>
> Hint: you'll find some help in the third line of the code snippet in the
>
> Synopsis section of the perldoc for Email::MIME. There's another broad
>
> hint in the section describing the "body" method.
>
>
>
> --
>
>
>
> Henry Law Manchester, England
Well, what I found out was this:
If I send the email, like from Outlook, and specifically choose Plain Text, the script works fine. But, if the email is in HTML, which is the default, I just cannot get plain text from it.
So, I give, Gonna try and loop through the content and find the info I need. Thanks for all the pointers though, it did help quite a bit.
------------------------------
Date: Fri, 08 Feb 2013 18:52:30 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <T8mdnTQC8Jfy1IjMnZ2dnUVZ8l2dnZ2d@giganews.com>
On 08/02/13 18:37, artmerar@gmail.com wrote:
> Well, what I found out was this:
>
> If I send the email, like from Outlook, and specifically choose Plain Text, the script works fine. But, if the email is in HTML, which is the default, I just cannot get plain text from it.
>
> So, I give, Gonna try and loop through the content and find the info I need. Thanks for all the pointers though, it did help quite a bit.
>
I'm going to have one more go at helping you to help yourself.
A MIME message, of the kind that you've tried to print out, contains
multiple parts. Each one of them will be instantiated by the
Email::MIME "new" method as a _separate_ Email::MIME object; the parts
which are contained inside one of them are returned by the "parts"
method. In other words, the MIME parts are arranged in a tree.
When you constrain Outlook to send in plain text there IS no MIME
content (that's what plain text means), so there are no subsidiary
parts, and your program (the one I wrote for you?) prints out the body.
But if there are subsidiary parts then it won't; it will only print
the body of the top-level object.
So you need to use the parts() method of your "first" message to
retrieve the individual sub-parts (they are returned as an array of
Email::MIME objects). Once you have the sub-parts you can find the one
that has the body you want (hint: look at the content disposition), and
then use the "body" method to return it. Watch out: the sub-parts may
have sub-sub-parts and so on; different news clients do it in different
ways (and often sub-optimally). And as Ben has sagely observed, that in
itself makes what you're trying to do quite hard.
Key learning: trees; objects; arrays of objects; iteration. And Reading
The Fine Manual. You should have found all this out already.
I'm the only person in this group that's still trying to help you. Now
please do some research, and write some code (and post it here) or
that's it.
Oh, and can't you fix your newsreader to stop it putting in extra blank
lines in your quotes?
--
Henry Law Manchester, England
------------------------------
Date: Fri, 8 Feb 2013 20:37:20 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <094gu9-t19.ln1@anubis.morrow.me.uk>
Quoth Henry Law <news@lawshouse.org>:
> On 08/02/13 18:37, artmerar@gmail.com wrote:
> > Well, what I found out was this:
> >
> > If I send the email, like from Outlook, and specifically choose Plain
> Text, the script works fine. But, if the email is in HTML, which is the
> default, I just cannot get plain text from it.
> >
> > So, I give, Gonna try and loop through the content and find the info
> I need. Thanks for all the pointers though, it did help quite a bit.
> >
>
> I'm going to have one more go at helping you to help yourself.
>
> A MIME message, of the kind that you've tried to print out, contains
> multiple parts. Each one of them will be instantiated by the
> Email::MIME "new" method as a _separate_ Email::MIME object; the parts
> which are contained inside one of them are returned by the "parts"
> method. In other words, the MIME parts are arranged in a tree.
>
> When you constrain Outlook to send in plain text there IS no MIME
> content (that's what plain text means), so there are no subsidiary
> parts, and your program (the one I wrote for you?) prints out the body.
> But if there are subsidiary parts then it won't; it will only print
> the body of the top-level object.
A plain text message will usually have MIME headers, and may well be
Content-Transfer-Encoded. Strictly a message in a character set other
than US-ASCII must use MIME, at least to the extent of declaring
'Content-Type: text/plain; charset=...' and 'Content-Transfer-Encoding:
8bit'. A 'plain text' message created by a conventional MUA may also be
multipart, if it has attachments or a signature.
> So you need to use the parts() method of your "first" message to
> retrieve the individual sub-parts (they are returned as an array of
> Email::MIME objects). Once you have the sub-parts you can find the one
> that has the body you want (hint: look at the content disposition),
Content-Disposition was not part of the original MIME spec, so body
parts might not have that header. The spec for multipart/related
(usually used for attachments) explicitly says that the rules for that
type override Content-Disposition handling, where they conflict. The
only way to find 'the body' of a message is by a careful parsing of the
various multipart types involved, checking Content-Type and -Disposition
where necessary.
> and then use the "body" method to return it. Watch out: the sub-parts
> may have sub-sub-parts and so on; different news clients do it in
> different ways (and often sub-optimally).
I believe the OP is also trying to convert HTML messages to plain text,
for which he will need to see perldoc -q "remove html".
Ben
------------------------------
Date: Thu, 7 Feb 2013 11:15:41 -0800 (PST)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: help with regexp
Message-Id: <e9c85819-32c8-4ec2-8c60-7e9fefabe7c0@p17g2000vbn.googlegroups.com>
Thanks Ben (and Rainer),
I didn't have any chance to touch it myself today...
On Feb 7, 2:37=A0pm, Ben Morrow <b...@morrow.me.uk> wrote:
> I am assuming the spec here requires matching brackets inside a %[]Nl?
> Can non-matching brackets be escaped?
I cannot see how non-maching brackets could make any sense there.
So, this would likely be an error, and I'd have to report it.
Now, maybe not in this scope, although...
I'd rather not force escaping inner brackets.
But that's my choice.
> If you don't allow escaping of unbalanced brackets, the simple answer is
> to use Regexp::Common::balanced. If you do, you will need to use 5.10,
> and write out the recursion yourself:
...
> The trick is the (?-1) group, which says 'start again at the top of the
> nearest enclosing () group'.
I'll have to play with both of these suggestions!
Thanks!
Marc
------------------------------
Date: Thu, 7 Feb 2013 13:35:35 -0800 (PST)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: help with regexp
Message-Id: <f325686e-1956-4f0e-ac0c-d736bf3a44eb@z9g2000vbx.googlegroups.com>
On Feb 7, 7:15=A0pm, Marc Girod <marc.gi...@gmail.com> wrote:
> I'll have to play with both of these suggestions!
I am very impressed.
Regexp::Common qw /balanced/ gives me a starting point (I have to use
{-keep}, and work out how to discriminate the 'wrong' brackets (e.g. %
[...]NSa) from the right ones, and to strip the backets;
but yours works fully as such (er... I had to switch from m[...] to
e.g. m{...}-- my Perl (5.14.2 on Cygwin) got confused and told:
'Invalid [] range "?-1" in regex'.)
I wasn't aware of this recursive option.
Only ashamed that I didn't even try...
Thanks!
Marc
------------------------------
Date: Thu, 7 Feb 2013 22:37:29 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: help with regexp
Message-Id: <9umdu9-cbn2.ln1@anubis.morrow.me.uk>
Quoth Marc Girod <marc.girod@gmail.com>:
> On Feb 7, 2:37 pm, Ben Morrow <b...@morrow.me.uk> wrote:
>
> > I am assuming the spec here requires matching brackets inside a %[]Nl?
> > Can non-matching brackets be escaped?
>
> I cannot see how non-maching brackets could make any sense there.
> So, this would likely be an error, and I'd have to report it.
> Now, maybe not in this scope, although...
>
> I'd rather not force escaping inner brackets.
> But that's my choice.
Hmm, I'm not sure I understand... Which of these are valid?
%[a[b]c]Nl # simple brackets
%[a[b[c]d]e]Nl # nested brackets
%[a\[b]Nl # an escaped bracket
%[a[[c]d]Nl # a Perl character class containing [c
%[a[]c]d]Nl # a Perl character class containing ]c
%[a[^]c]d]Nl # a Perl character class not containing ]c
The code I posted will match the first three but not the last three.
This is also the same logic as used by perl when finding the end of a
m[...] pattern, even though Perl character classes don't do nesting like
that.
Ben
------------------------------
Date: Fri, 8 Feb 2013 09:56:02 -0800 (PST)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: help with regexp
Message-Id: <7e3681ca-bae9-4a00-9088-e10976866321@y9g2000vbb.googlegroups.com>
On Feb 7, 10:37=A0pm, Ben Morrow <b...@morrow.me.uk> wrote:
> =A0 =A0 %[a[b]c]Nl =A0 =A0 =A0 =A0 =A0# simple brackets
Yes
> =A0 =A0 %[a[b[c]d]e]Nl =A0 =A0 =A0# nested brackets
> =A0 =A0 %[a\[b]Nl =A0 =A0 =A0 =A0 =A0 # an escaped bracket
> =A0 =A0 %[a[[c]d]Nl =A0 =A0 =A0 =A0 # a Perl character class containing [=
c
> =A0 =A0 %[a[]c]d]Nl =A0 =A0 =A0 =A0 # a Perl character class containing ]=
c
> =A0 =A0 %[a[^]c]d]Nl =A0 =A0 =A0 =A0# a Perl character class not containi=
ng ]c
Honestly, I believe only the first is relevant...
I.e. I'll take the contents and use it as a regexp to filter 'label
types'.
So, one level of character class may be useful, but brackets are not
themselves legal characters for 'label types', so all the rest is
moot, isn't it?
Thanks again anyway!
Marc
------------------------------
Date: Fri, 8 Feb 2013 19:46:38 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: help with regexp
Message-Id: <u91gu9-gf8.ln1@anubis.morrow.me.uk>
Quoth Marc Girod <marc.girod@gmail.com>:
> On Feb 7, 10:37 pm, Ben Morrow <b...@morrow.me.uk> wrote:
>
> > %[a[b]c]Nl # simple brackets
>
> Yes
>
> > %[a[b[c]d]e]Nl # nested brackets
> > %[a\[b]Nl # an escaped bracket
> > %[a[[c]d]Nl # a Perl character class containing [c
> > %[a[]c]d]Nl # a Perl character class containing ]c
> > %[a[^]c]d]Nl # a Perl character class not containing ]c
>
> Honestly, I believe only the first is relevant...
> I.e. I'll take the contents and use it as a regexp to filter 'label
> types'.
> So, one level of character class may be useful, but brackets are not
> themselves legal characters for 'label types', so all the rest is
> moot, isn't it?
Oh, well, that's much easier then:
m{ %\[( (?: [^][]+ | \[ [a-z]+ \] )* )\]N?l }gx
(assuming your 'label types' all match [a-z]+)
Ben
------------------------------
Date: Sat, 9 Feb 2013 04:01:38 -0800 (PST)
From: SSS Develop <sssdevelop@gmail.com>
Subject: Parsing Process Log files - looking for Perl Modules
Message-Id: <91274ed0-ac87-4e43-ace3-5299e6e4a9ec@googlegroups.com>
I am looking for Perl Modules which can help me parse the log files.
I have monitoring framework which kind of scrapes Web Applications(sites). Visits web sites, fills the login form, clicks login button, verifies the welcome page content.
This generates the log files - logs details of each step.. something like: Monitoring site started, got the login form, filled the login form, clicked on the form, got the response, authentication failed etc..etc
I would like to parse the log files for [1] check the consistency of each block (I am calling block for one monitoring instance log). [2] What times failures (authentication failures etc) etc etc.
Please help by suggesting Text Parsing modules/or other Open source tools.
thank you,
------------------------------
Date: Sat, 09 Feb 2013 12:45:20 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: Parsing Process Log files - looking for Perl Modules
Message-Id: <M6idnYlt3Md82YvMnZ2dnUVZ8o6dnZ2d@giganews.com>
On 09/02/13 12:01, SSS Develop wrote:
> I am looking for Perl Modules which can help me parse the log files.
> This generates the log files - logs details of each step.. something like: Monitoring site started, got the login form, filled the login form, clicked on the form, got the response, authentication failed etc..etc
>
>
> I would like to parse the log files for [1] check the consistency of each block (I am calling block for one monitoring instance log). [2] What times failures (authentication failures etc) etc etc.
Rather a general question. Have you Googled "perl log parsing"? You'll
get lots of hits, including reference to an O'Reilly book called "Perl
for System Administration" which has lots about using Perl to parse log
files. There's also a reference to a "Log Parser (PERL)" (sic).
Have you searched CPAN? A cursory search throws up lots of log analysis
modules, admittedly targeted at specific log formats; maybe you could
modify one of those?
It would be easier for the group to help you if you did a bit more
research, wrote some simple code, and posted it with some slightly more
specific questions, together with some sample log data.
--
Henry Law Manchester, England
------------------------------
Date: Thu, 07 Feb 2013 23:13:40 -0700
From: Cal Dershowitz <cal@example.invalid>
Subject: Re: taking a look at some examples of web automation scripts
Message-Id: <5L2dnfTNlNcOConMnZ2dnUVZ_sSdnZ2d@supernews.com>
On 02/02/2013 12:16 AM, Cal Dershowitz wrote:
> I'd like to take a look at examples of web automation that anyone might
> have. I found this one today and was able to adapt it (slightly) to
> actually make it work. I think of how long it takes me to do this with
> GUI events, and this is so much better.
>
> $ ./cpan1.pl HTML::Form
> $ cat cpan1.pl
> #!/usr/bin/perl
>
> # turn on perl's safety features
> use strict;
> use warnings;
>
> # work out the name of the module we're looking for
> my $module_name = $ARGV[0]
> or die "Must specify module name on command line";
>
> # create a new browser
> use WWW::Mechanize;
> my $browser = WWW::Mechanize->new();
>
> # tell it to get the main page
> $browser->get("http://search.cpan.org/");
>
> # okay, fill in the box with the name of the
> # module we want to look up
> $browser->form_number(1);
> $browser->field( "query", $module_name );
> $browser->click();
>
> # click on the link that matches the module name
> $browser->follow_link( text => $module_name );
>
> my $url = $browser->uri;
>
> # launch a browser...
> system( 'firefox', $url );
>
> exit(0);
> $
>
> That this fires up firefox at the end makes it a great tool. I'm
> struggling now with the referencing in the object model, but I'm wearing
> it down with repetition.
>
> I'd love to see any examples others may have.
No responses. I think I need to change my toolchain.
--
Cal
------------------------------
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 3877
***************************************
