[32527] in Perl-Users-Digest
Perl-Users Digest, Issue: 3791 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Oct 7 14:09:19 2012
Date: Sun, 7 Oct 2012 11:09:06 -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 Sun, 7 Oct 2012 Volume: 11 Number: 3791
Today's topics:
Re: Differential pattern match <ben@morrow.me.uk>
Re: Differential pattern match <rweikusat@mssgmbh.com>
Re: Differential pattern match <graham.stow@stowassocs.co.uk>
Re: Differential pattern match <graham.stow@stowassocs.co.uk>
Re: Differential pattern match <graham.stow@stowassocs.co.uk>
Re: Differential pattern match <ben@morrow.me.uk>
Re: Differential pattern match <rweikusat@mssgmbh.com>
Re: Differential pattern match <graham.stow@gmail.com>
I need a free script afrikaans@gmail.com
Re: I need a free script <news@lawshouse.org>
Re: I need a free script <lesley.binks@gmail.com>
Re: I need a free script <glex_no-spam@qwest-spam-no.invalid>
Re: I need a free script <lesley.binks@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 5 Oct 2012 12:36:20 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Differential pattern match
Message-Id: <kat2k9-3ou1.ln1@anubis.morrow.me.uk>
[Please don't top-post here.]
Quoth "Graham" <graham.stow@stowassocs.co.uk>:
> Both these regex produced the same output. It's the best so far, but
> unfirtunately it's not perfect.
>
> Here's some 'real life' attempts using the first of these to match some of
> the tabs on the page at
> http://www.hakwright.co.uk/music/tab/not-the-same-without-you.shtml
Can you show your code? How you apply the regex to the string can make a
difference.
<snip>
> However, applied to the line 'xxx200 1xx230 x7x785 xx0975'
> produced the output
> '2xx200 1xx230
> x7x785
> xx0975'
>
> Thus the first two chord tabs on this line weren't matched
I was misunderstanding the tab format again, I think: these have a
string marked as fret 0, which I assumed wasn't allowed. Change [1-9Xx]
to [0-9Xx] to fix that.
> Similarly, applied to the line 'xx0563 3x353x x3545x 1x221x
> 07x775'
> produced the output
>
> 'xx0
> 563 3x3
> 53x x35
> 45x 1x2
> 21x 07x775'
>
> Thus none of the five chords on this line were matched correctly, with the
> regex bridging the white space and matching part of one chord with part of
> another in some instances (the very problem I'm trying to avoid)
This was the non-\b version, right? That's exactly the problem the \bs
are supposed to solve. (This was also running into the 'fret 0'
problem.)
Since you're trying to match out of random text like this, you may want
to be less liberal and change the [ ]* back to [ ]{0,2}. You may also
want to add more \bs at both ends of the whole pattern, to avoid
misunderstandings like the one above.
Ben
------------------------------
Date: Fri, 05 Oct 2012 13:05:45 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Differential pattern match
Message-Id: <87boghm8di.fsf@sapphire.mobileactivedefense.com>
"Graham S" <graham.stow@gmail.com> writes:
> The six strings of a guitar, from lowest to highest pitch, are tuned EADGBE.
> Thus a tab of 333x22 would mean 3rd fet on the E, A and D strings, the G
> string muted (not played) and the 2nd fret on the B and E strings. This is
> the normal tablature for chords where all the notes are from up to but not
> exceeding the 9th fret. Beond the 9th fret, one or two spaces are left to
> make it clear which strings are being played and at what fret. Thus '999x
> 10x' would mean 9th fret on the E, A & D strings, the G and E strings muted,
> and 10th fret on the B string. However, some tab writers might equally show
> this as '999x 10 x' or '9 9 9 x 10 x '.
So what's '11x 11x'? Can this be decided without examining the
complete input? Examples of that:
11x 11x3
11x 11x 33
11x 11x
11x 11x 11x
------------------------------
Date: Fri, 5 Oct 2012 13:57:12 +0100
From: "Graham" <graham.stow@stowassocs.co.uk>
Subject: Re: Differential pattern match
Message-Id: <wKqdnZ7EAOWzRPPNnZ2dnUVZ8qGdnZ2d@bt.com>
"Rainer Weikusat" <rweikusat@mssgmbh.com> wrote in message
news:87boghm8di.fsf@sapphire.mobileactivedefense.com...
> "Graham S" <graham.stow@gmail.com> writes:
>> The six strings of a guitar, from lowest to highest pitch, are tuned
>> EADGBE.
>> Thus a tab of 333x22 would mean 3rd fet on the E, A and D strings, the G
>> string muted (not played) and the 2nd fret on the B and E strings. This
>> is
>> the normal tablature for chords where all the notes are from up to but
>> not
>> exceeding the 9th fret. Beond the 9th fret, one or two spaces are left to
>> make it clear which strings are being played and at what fret. Thus '999x
>> 10x' would mean 9th fret on the E, A & D strings, the G and E strings
>> muted,
>> and 10th fret on the B string. However, some tab writers might equally
>> show
>> this as '999x 10 x' or '9 9 9 x 10 x '.
>
> So what's '11x 11x'? Can this be decided without examining the
> complete input? Examples of that:
>
> 11x 11x3
> 11x 11x 33
> 11x 11x
> 11x 11x 11x
>
>
>
'11x 11x' can only be
1-lowE string
1-A string
x-D string
1-G string
1-Bstring
x-highE string
'11x 11x3', if it was anything, would be
1-lowE string
1-A string
x-D string
11-G string
x-B string
3-highE string
but unplayable due to the stretch between the 3rd and 11th frets (and
assuming the a capo was used to barre at the first fret)
'11x 11x 33' if it was anything would be
11-lowE string
x-A string
11-D string
x-G string
3-B string
3-highE string
but again unplayable due to the stretch between the 3rd and 11th frets
11x 11x 11x can only be
11-lowE string
x-A string
11-D string
x-G string
11-B string
x-highE string
My brain can figure that out pretty easily. What it can't do is figure out a
pattern match that accounts for all the variables.
Graham S
------------------------------
Date: Fri, 5 Oct 2012 14:28:49 +0100
From: "Graham" <graham.stow@stowassocs.co.uk>
Subject: Re: Differential pattern match
Message-Id: <jcedna2eDrcKffPNnZ2dnUVZ8sOdnZ2d@bt.com>
"Ben Morrow" <ben@morrow.me.uk> wrote in message
news:kat2k9-3ou1.ln1@anubis.morrow.me.uk...
> [Please don't top-post here.]
>
> Quoth "Graham" <graham.stow@stowassocs.co.uk>:
>> Both these regex produced the same output. It's the best so far, but
>> unfirtunately it's not perfect.
>>
>> Here's some 'real life' attempts using the first of these to match some
>> of
>> the tabs on the page at
>> http://www.hakwright.co.uk/music/tab/not-the-same-without-you.shtml
>
> Can you show your code? How you apply the regex to the string can make a
> difference.
>
> <snip>
>> However, applied to the line 'xxx200 1xx230 x7x785
>> xx0975'
>> produced the output
>> '2xx200 1xx230
>> x7x785
>> xx0975'
>>
>> Thus the first two chord tabs on this line weren't matched
>
> I was misunderstanding the tab format again, I think: these have a
> string marked as fret 0, which I assumed wasn't allowed. Change [1-9Xx]
> to [0-9Xx] to fix that.
>
>> Similarly, applied to the line 'xx0563 3x353x x3545x
>> 1x221x
>> 07x775'
>> produced the output
>>
>> 'xx0
>> 563 3x3
>> 53x x35
>> 45x 1x2
>> 21x 07x775'
>>
>> Thus none of the five chords on this line were matched correctly, with
>> the
>> regex bridging the white space and matching part of one chord with part
>> of
>> another in some instances (the very problem I'm trying to avoid)
>
> This was the non-\b version, right? That's exactly the problem the \bs
> are supposed to solve. (This was also running into the 'fret 0'
> problem.)
>
> Since you're trying to match out of random text like this, you may want
> to be less liberal and change the [ ]* back to [ ]{0,2}. You may also
> want to add more \bs at both ends of the whole pattern, to avoid
> misunderstandings like the one above.
>
> Ben
>
!! Success !!
/ ((?: (?: \b [12][0-9] \b | [0-9Xx] ) [ ]{0,2} ){6}) /x did the business
and produces exactly the output I want !! (basically your code with an
additional pair of parentheses on the extreme left and right to capture the
output
Tested it on a number of tabs with 100% success !!
Apart from the following line - which I obviously wouldn't expect to match
8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AX
8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AXDon't
know what's going on there with the As and the B's - maybe it a typo, or
maybe it means something I'm not aware of (I'm no guitarist either!)
Cheers Ben :) !!
Graham
------------------------------
Date: Fri, 5 Oct 2012 15:13:54 +0100
From: "Graham" <graham.stow@stowassocs.co.uk>
Subject: Re: Differential pattern match
Message-Id: <RN-dndRSo6S0dvPNnZ2dnUVZ7oKdnZ2d@bt.com>
"Graham" <graham.stow@stowassocs.co.uk> wrote in message
news:jcedna2eDrcKffPNnZ2dnUVZ8sOdnZ2d@bt.com...
>
> "Ben Morrow" <ben@morrow.me.uk> wrote in message
> news:kat2k9-3ou1.ln1@anubis.morrow.me.uk...
>> [Please don't top-post here.]
>>
>> Quoth "Graham" <graham.stow@stowassocs.co.uk>:
>>> Both these regex produced the same output. It's the best so far, but
>>> unfirtunately it's not perfect.
>>>
>>> Here's some 'real life' attempts using the first of these to match some
>>> of
>>> the tabs on the page at
>>> http://www.hakwright.co.uk/music/tab/not-the-same-without-you.shtml
>>
>> Can you show your code? How you apply the regex to the string can make a
>> difference.
>>
>> <snip>
>>> However, applied to the line 'xxx200 1xx230 x7x785 xx0975'
>>> produced the output
>>> '2xx200 1xx230
>>> x7x785
>>> xx0975'
>>>
>>> Thus the first two chord tabs on this line weren't matched
>>
>> I was misunderstanding the tab format again, I think: these have a
>> string marked as fret 0, which I assumed wasn't allowed. Change [1-9Xx]
>> to [0-9Xx] to fix that.
>>
>>> Similarly, applied to the line 'xx0563 3x353x x3545x 1x221x
>>> 07x775'
>>> produced the output
>>>
>>> 'xx0
>>> 563 3x3
>>> 53x x35
>>> 45x 1x2
>>> 21x 07x775'
>>>
>>> Thus none of the five chords on this line were matched correctly, with
>>> the
>>> regex bridging the white space and matching part of one chord with part
>>> of
>>> another in some instances (the very problem I'm trying to avoid)
>>
>> This was the non-\b version, right? That's exactly the problem the \bs
>> are supposed to solve. (This was also running into the 'fret 0'
>> problem.)
>>
>> Since you're trying to match out of random text like this, you may want
>> to be less liberal and change the [ ]* back to [ ]{0,2}. You may also
>> want to add more \bs at both ends of the whole pattern, to avoid
>> misunderstandings like the one above.
>>
>> Ben
>>
>
> !! Success !!
>
> / ((?: (?: \b [12][0-9] \b | [0-9Xx] ) [ ]{0,2} ){6}) /x did the
> business and produces exactly the output I want !! (basically your code
> with an additional pair of parentheses on the extreme left and right to
> capture the output
>
> Tested it on a number of tabs with 100% success !!
>
> Apart from the following line - which I obviously wouldn't expect to match
> 8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AX
> 8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AXDon't
> know what's going on there with the As and the B's - maybe it a typo, or
> maybe it means something I'm not aware of (I'm no guitarist either!)
>
> Cheers Ben :) !!
>
> Graham
>
Hmm - I spoke a little to soon! It's fine with a few of the 'commercial'
tabs I've fed it, but when I try and break it, unfortunately I can with the
likes of....
It doesn't like this 'xx10 10 10x' very muchor this 'x10 10 10 9x'
eitherwhich match as It doesn't like this 'xx10 10 10x' very muchor this
'x10 10 10 9x' eitherGraham
------------------------------
Date: Fri, 5 Oct 2012 20:00:17 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Differential pattern match
Message-Id: <1bn3k9-d322.ln1@anubis.morrow.me.uk>
Quoth "Graham" <graham.stow@stowassocs.co.uk>:
>
> > / ((?: (?: \b [12][0-9] \b | [0-9Xx] ) [ ]{0,2} ){6}) /x did the
> > business and produces exactly the output I want !! (basically your code
> > with an additional pair of parentheses on the extreme left and right to
> > capture the output
> >
> > Tested it on a number of tabs with 100% success !!
> >
> > Apart from the following line - which I obviously wouldn't expect to match
> > 8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AX
> > 8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AXDon't
> > know what's going on there with the As and the B's - maybe it a typo, or
> > maybe it means something I'm not aware of (I'm no guitarist either!)
I presume you can see how to fix that, if you want to? (Just treat A and
B the same as X.)
> Hmm - I spoke a little to soon! It's fine with a few of the 'commercial'
> tabs I've fed it, but when I try and break it, unfortunately I can with the
> likes of....
>
> It doesn't like this 'xx10 10 10x' very muchor this 'x10 10 10 9x'
> eitherwhich match as It doesn't like this 'xx10 10 10x' very muchor this
> 'x10 10 10 9x' eitherGraham
Well, no. I didn't know those were allowed, either: they have a
single-character fret 'number' (which happens to be an X) right next to
a double-digit number, with no space. The only simple way I can see to
fix that is to replace the first \b with
(?: (?<= [Xx]) | \b )
and the second with
(?: (?= [Xx]) | \b )
Those constructions are called 'lookahead/behind', and like \b, ^ and $
they are zero-width assertions that match between characters. (?<=foo)
matches at a point in the string immediately preceded by 'foo', (?=foo)
at a point immediately followed. So the new pattern will allow Xs to
butt up against two-digit fret numbers, but not other digits or letters.
This is turning into quite a complicated pattern. Make sure you write it
with plenty of whitespace (and newlines and indentation, where that's
helpful), and if necessary include comments within the pattern to
explain what the various bits do.
Ben
------------------------------
Date: Fri, 05 Oct 2012 23:33:03 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Differential pattern match
Message-Id: <87haq81rds.fsf@sapphire.mobileactivedefense.com>
"Graham" <graham.stow@stowassocs.co.uk> writes:
[...]
> '11x 11x3', if it was anything, would be
> 1-lowE string
> 1-A string
> x-D string
> 11-G string
> x-B string
> 3-highE string
> but unplayable due to the stretch between the 3rd and 11th frets (and
> assuming the a capo was used to barre at the first fret)
>
> '11x 11x 33' if it was anything would be
> 11-lowE string
> x-A string
> 11-D string
> x-G string
> 3-B string
> 3-highE string
> but again unplayable due to the stretch between the 3rd and 11th frets
[...]
> My brain can figure that out pretty easily. What it can't do is figure out a
> pattern match that accounts for all the variables.
And I assume that 11x 11x33 would be the same as 11x 11x 33. If this
is true, the sequence 11x 11x3 can mean 1 1 x 11 x 3 or 11 x 11 x 3,
depending on what, if anything comes after the final 3: Either this
needs to be parsed back to front and not front to back or it needs to
do a real exhaustive search with backtracking, based on knowing the
meaning/ semantics of the input, not just the patterns occuring in it.
And I don't think this can be done with regular expressions (I could,
of course, be wrong).
------------------------------
Date: Sat, 6 Oct 2012 11:12:21 +0100
From: "Graham S" <graham.stow@gmail.com>
Subject: Re: Differential pattern match
Message-Id: <k4p068$3nu$1@news.enta.net>
"Ben Morrow" <ben@morrow.me.uk> wrote in message
news:1bn3k9-d322.ln1@anubis.morrow.me.uk...
>
> Quoth "Graham" <graham.stow@stowassocs.co.uk>:
>>
>> > / ((?: (?: \b [12][0-9] \b | [0-9Xx] ) [ ]{0,2} ){6}) /x did the
>> > business and produces exactly the output I want !! (basically your code
>> > with an additional pair of parentheses on the extreme left and right to
>> > capture the output
>> >
>> > Tested it on a number of tabs with 100% success !!
>> >
>> > Apart from the following line - which I obviously wouldn't expect to
>> > match
>> > 8X998X 7X778X 6X776X 5X556X AXBBAX 9X99AX
>> > 8X998X 7X778X 6X776X 5X556X AXBBAX
>> > 9X99AXDon't
>> > know what's going on there with the As and the B's - maybe it a typo,
>> > or
>> > maybe it means something I'm not aware of (I'm no guitarist either!)
>
> I presume you can see how to fix that, if you want to? (Just treat A and
> B the same as X.)
>
>> Hmm - I spoke a little to soon! It's fine with a few of the 'commercial'
>> tabs I've fed it, but when I try and break it, unfortunately I can with
>> the
>> likes of....
>>
>> It doesn't like this 'xx10 10 10x' very muchor this 'x10 10 10 9x'
>> eitherwhich match as It doesn't like this 'xx10 10 10x' very muchor this
>> 'x10 10 10 9x' eitherGraham
>
> Well, no. I didn't know those were allowed, either: they have a
> single-character fret 'number' (which happens to be an X) right next to
> a double-digit number, with no space. The only simple way I can see to
> fix that is to replace the first \b with
>
> (?: (?<= [Xx]) | \b )
>
> and the second with
>
> (?: (?= [Xx]) | \b )
>
> Those constructions are called 'lookahead/behind', and like \b, ^ and $
> they are zero-width assertions that match between characters. (?<=foo)
> matches at a point in the string immediately preceded by 'foo', (?=foo)
> at a point immediately followed. So the new pattern will allow Xs to
> butt up against two-digit fret numbers, but not other digits or letters.
>
> This is turning into quite a complicated pattern. Make sure you write it
> with plenty of whitespace (and newlines and indentation, where that's
> helpful), and if necessary include comments within the pattern to
> explain what the various bits do.
>
> Ben
>
Superb!! Works a treat!!
I'm pretty convinced this will match 99.9% of guitar tabs out there - most
of them are straightforward 6 character strings of X's and numerals played
below the 10th fret anyway, but this pattern match should catch the vast
majority of the more complex ones.
And many thanks for explaining some of the finer points of pattern matching
Graham
------------------------------
Date: Fri, 5 Oct 2012 06:13:57 -0700 (PDT)
From: afrikaans@gmail.com
Subject: I need a free script
Message-Id: <f3e49050-fdc4-4bf7-90ea-104b0dc2f8eb@googlegroups.com>
G'day everyone
Where can I, as a non-perl user, post a question of the type "Where can I find a free script that does X", without stepping on toes?
Thanks
Samuel (leuce)
------------------------------
Date: Fri, 05 Oct 2012 16:07:56 +0100
From: Henry Law <news@lawshouse.org>
Subject: Re: I need a free script
Message-Id: <g7WdnUYz_f1TavPNnZ2dnUVZ8iadnZ2d@giganews.com>
On 05/10/12 14:13, afrikaans@gmail.com wrote:
> G'day everyone
>
> Where can I, as a non-perl user, post a question of the type "Where can I find a free script that does X", without stepping on toes?
Here: http://www.google.com/search?q=perl+scripts+free
--
Henry Law Manchester, England
------------------------------
Date: Fri, 5 Oct 2012 08:37:22 -0700 (PDT)
From: Lesley Binks <lesley.binks@gmail.com>
Subject: Re: I need a free script
Message-Id: <3de3ac9f-1605-4aef-9383-47c766919282@googlegroups.com>
On Friday, 5 October 2012 16:07:59 UTC+1, Henry Law wrote:
> On 05/10/12 14:13, afr...ns@gmail.com wrote:
>=20
> > G'day everyone
>=20
> >
>=20
> > Where can I, as a non-perl user, post a question of the type "Where can=
I find a free script that does X", without stepping on toes?
>=20
>=20
>=20
> Here: http://www.google.com/search?q=3Dperl+scripts+free
>=20
which regretfully shows the Matt's Script archive at the top of the list :(=
(ouch! my toes! ;) ) Although Formail has been downloaded a lot, all of =
Matt's scripts have been heavily criticised in the past - mostly for lack o=
f both robustness and secure behaviour. =20
Most of the scripts haven't been updated since 1995 and are therefore hugel=
y out of date; FormMail was last updated 3 years ago.
I'm not sure what the OP means by a 'non-perl user' anyway. =20
There are free scripts out there but it is difficult to know what sources t=
o trust.
But if the OP would like to learn perl or at least familiarise him/herself =
with good practices then learn.perl.org is a good start.
Kind Regards
Lesley
------------------------------
Date: Fri, 05 Oct 2012 11:11:14 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: I need a free script
Message-Id: <506f06a2$0$52265$815e3792@news.qwest.net>
On 10/05/12 08:13, afrikaans@gmail.com wrote:
> G'day everyone
>
> Where can I, as a non-perl user, post a question of the type "Where can I find a free script that does X", without stepping on toes?
>
> Thanks
> Samuel (leuce)
How do you know you want to use Perl?
Maybe it could be a simple Korn Shell script, or maybe Javascript,
or you're on Windows and a Batch file will suffice.. Sure Perl can
do just about anything, however not knowing a little more about
what you want to do and what sort of limitations/constraints you
have, it's tough to suggest where to go.
Either provide what you want to do, at a high level, and maybe
folks here will provide you with a solution and/or point
you down the right path, or start using your favorite search
engine, giving it as much information as you can. Using 'free'
typically is a poor way to find programs that do a specific task,
use some technical terms to help the search engine narrow the
results.
------------------------------
Date: Sat, 6 Oct 2012 16:52:31 -0700 (PDT)
From: Lesley Binks <lesley.binks@gmail.com>
Subject: Re: I need a free script
Message-Id: <3cbd3952-a181-43c8-8945-1189722ee9a7@googlegroups.com>
On Friday, 5 October 2012 17:11:14 UTC+1, J. Gleixner wrote:
> On 10/05/12 08:13, af...ans@gmail.com wrote:
>
> > G'day everyone
>
> >
>
> > Where can I, as a non-perl user, post a question of the type "Where can I find a free script that does X", without stepping on toes?
>
> >
>
> > Thanks
>
> > Samuel (leuce)
>
>
>
>
>
> How do you know you want to use Perl?
>
>
>
> Maybe it could be a simple Korn Shell script, or maybe Javascript,
>
> or you're on Windows and a Batch file will suffice.. Sure Perl can
>
> do just about anything, however not knowing a little more about
>
> what you want to do and what sort of limitations/constraints you
>
> have, it's tough to suggest where to go.
>
>
>
> Either provide what you want to do, at a high level, and maybe
>
> folks here will provide you with a solution and/or point
>
> you down the right path, or start using your favorite search
>
> engine, giving it as much information as you can. Using 'free'
>
> typically is a poor way to find programs that do a specific task,
>
> use some technical terms to help the search engine narrow the
>
> results.
Well said :)
Anyhow - here's a link to the nms project
http://nms-cgi.sourceforge.net/
which contains code by an experienced Perl coder and educator. Again it hasn't been updated in anyway since about 2006.
Kind Regards
Lesley
------------------------------
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 3791
***************************************
