[29991] in Perl-Users-Digest
Perl-Users Digest, Issue: 1234 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Jan 26 00:09:41 2008
Date: Fri, 25 Jan 2008 21:09:05 -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 Fri, 25 Jan 2008 Volume: 11 Number: 1234
Today's topics:
Re: Get an arbitrary hash key, quickly. <ben@morrow.me.uk>
Re: Newbie Perl Question <tadmc@seesig.invalid>
regex dingbat dodge - single char as string to repeatab <jfcampbell@aol.com>
Re: regex dingbat dodge - single char as string to repe <jfcampbell@aol.com>
Re: regex dingbat dodge - single char as string to repe <ben@morrow.me.uk>
Re: regex dingbat dodge - single char as string to repe <someone@example.com>
regular expression negate a word (not character) <Summercoolness@gmail.com>
Re: regular expression negate a word (not character) <Summercoolness@gmail.com>
Re: regular expression negate a word (not character) <paulaireilly@gmail.com>
Re: regular expression negate a word (not character) <ben@morrow.me.uk>
Re: regular expression negate a word (not character) <ben@morrow.me.uk>
Re: regular expression negate a word (not character) <mark.e.tolonen@mailinator.com>
Re: Relying on $_ <ben@morrow.me.uk>
Re: Search/Replace text in XML file sln@netherlands.co
Version 5.8.8.8 html docs are shifted over (hidden) abo sln@netherlands.co
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 25 Jan 2008 22:35:33 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Get an arbitrary hash key, quickly.
Message-Id: <lq4q65-mkh.ln1@osiris.mauzo.dyndns.org>
Quoth "comp.llang.perl.moderated" <ced@blv-sam-01.ca.boeing.com>:
> On Jan 24, 9:25 am, xhos...@gmail.com wrote:
>
> Even with tie slowness, a Tie::IxHash solution would at least be more
> straightforward since insertion order is maintained... I think.
I have to admit I've never seen the point of Tie::IxHash. It's just the
same as the parallel array/hash Xho'd already rejected, but slower...
Ben
------------------------------
Date: Sat, 26 Jan 2008 01:50:20 GMT
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: Newbie Perl Question
Message-Id: <slrnfpl467.iqf.tadmc@tadmc30.sbcglobal.net>
Bryce <zerospam@example.com> wrote:
> Gunnar - "use CGI::Carp 'fatalsToBrowser';" proved infinitely useful
There are lots of infinitely useful tips in the Perl FAQ.
If you are doing programming for the CGI, then you should
read all of the FAQs that mention it:
perldoc -q CGI
How can I make my CGI script more efficient?
Where can I learn about CGI or Web programming in Perl?
What is the correct form of response from a CGI script?
My CGI script runs from the command line but not the
browser. (500 Server Error)
How can I get better error messages from a CGI program?
How do I make sure users can't enter values into a form
that cause my CGI script to do bad things?
How do I decode a CGI form?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 25 Jan 2008 11:16:00 -0800 (PST)
From: John <jfcampbell@aol.com>
Subject: regex dingbat dodge - single char as string to repeatable single char.
Message-Id: <613d8d7a-783f-4ee3-a502-e4ed1a422f29@z17g2000hsg.googlegroups.com>
I have text that might have had a star character in the proprietary
orginating system. The character is used in ratings boxes: A three-
star movie, a four-star restaurant, etc.
By the time it's exported and available to me, it's represented by a
string: "<star>".
I want to suround consecutive stars with font coding and replace each
instance of the string with a single character that, in conjuction
with the font change, will eventually print as a star.
To set up this substitution, I change the strings back to a unique
character, one that I reckon would never occur in nature.
When I try to surround any repetitions of this invented character, I
instead match everything.
===
#!/usr/bin/perl -w
use strict;
my $text = "Cuisine: Urban deli<ep>";
$text .= "Overall: <star><star><star><star><1/2> (very good to
excellent)<ep>";
$text .= "Food: <star><star><star><star><1/2><ep>";
$text =~ s/\<star\>/_STAR_/ig; # uscores easier in regex than angle
brackets.
$text =~ s/_STAR_/\xbc/g; # change pseudocharacter to single
character
$text =~ s/(\xbc*)/_STARFONT_$1_ENDSTAR/g; #bracket groups in more
pseudocode
print $text;
====
If I limit the search to five consecutive stars, the match works as I
intended:
===
#!/usr/bin/perl -w
use strict;
my $text = "Cuisine: Urban deli<ep>";
$text .= "Overall: <star><star><star><star><1/2> (very good to
excellent)<ep>";
$text .= "Food: <star><star><star><star><1/2><ep>";
$text =~ s/\<star\>/_STAR_/ig; # uscores easier in regex than angle
brackets.
$text =~ s/_STAR_/\xbc/g; # change pseudocharacter to single
character
$text =~ s/(\xbc{1,5})/_STARFONT_$1_ENDSTAR/g; #bracket groups of
stars in more pseudocode
print $text;
===
So what am I missing when it comes to the first search?
Certainly, I am missing some superior technique for matching repeated
instances of such a string, so I am open to suggestions there.
John Campbell
Haddonfield, NJ 08033
------------------------------
Date: Fri, 25 Jan 2008 12:08:17 -0800 (PST)
From: John <jfcampbell@aol.com>
Subject: Re: regex dingbat dodge - single char as string to repeatable single char.
Message-Id: <fa808f15-741c-409b-8354-69cad65d13b8@d21g2000prf.googlegroups.com>
On Jan 25, 2:39=A0pm, "John W. Krahn" <some...@example.com> wrote:
> John wrote:
>=A0The '*' modifier matches *zero* or
> more times and there are *zero* '\xbc' characters everywhere in the
> string. =A0The second one has to match at least *one* character. =A0Change=
> '\xbc*' to '\xbc+'.
That does the trick. It ought to come in handy.
Just realized that this snippet prints what in some systems is an
unprintable character.
I just see questions marks. Hope I didn't cause any problems with that.
------------------------------
Date: Fri, 25 Jan 2008 22:46:46 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: regex dingbat dodge - single char as string to repeatable single char.
Message-Id: <mf5q65-mkh.ln1@osiris.mauzo.dyndns.org>
Quoth John <jfcampbell@aol.com>:
> I have text that might have had a star character in the proprietary
> orginating system. The character is used in ratings boxes: A three-
> star movie, a four-star restaurant, etc.
>
> By the time it's exported and available to me, it's represented by a
> string: "<star>".
>
> I want to suround consecutive stars with font coding and replace each
> instance of the string with a single character that, in conjuction
> with the font change, will eventually print as a star.
>
> To set up this substitution, I change the strings back to a unique
> character, one that I reckon would never occur in nature.
>
> When I try to surround any repetitions of this invented character, I
> instead match everything.
>
> #!/usr/bin/perl -w
You want
use warnings;
rather than -w, nowadays.
> use strict;
>
> my $text = "Cuisine: Urban deli<ep>";
> $text .= "Overall: <star><star><star><star><1/2> (very good to
> excellent)<ep>";
> $text .= "Food: <star><star><star><star><1/2><ep>";
>
> $text =~ s/\<star\>/_STAR_/ig; # uscores easier in regex
> than angle
No they're not. Angles don't need escaping inside regexen.
> brackets.
> $text =~ s/_STAR_/\xbc/g; # change pseudocharacter to single
> character
> $text =~ s/(\xbc*)/_STARFONT_$1_ENDSTAR/g; #bracket groups in more
> pseudocode
I don't know what the point of that is, unless you have some intervening
code that processes char-by-char.
s/( (?: <star> )+ )/_STARFONT_$1_ENDSTAR/gx;
will work perfectly well. Notice the difference between () and (?: )
(capturing vs. grouping) and my use of /x to make the regex more
comprehensible. Needing + instead of * has already been covered :).
Ben
------------------------------
Date: Fri, 25 Jan 2008 19:39:58 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: regex dingbat dodge - single char as string to repeatable single char.
Message-Id: <iWqmj.14512$vp3.8258@edtnps90>
John wrote:
> I have text that might have had a star character in the proprietary
> orginating system. The character is used in ratings boxes: A three-
> star movie, a four-star restaurant, etc.
>
> By the time it's exported and available to me, it's represented by a
> string: "<star>".
>
> I want to suround consecutive stars with font coding and replace each
> instance of the string with a single character that, in conjuction
> with the font change, will eventually print as a star.
>
> To set up this substitution, I change the strings back to a unique
> character, one that I reckon would never occur in nature.
>
> When I try to surround any repetitions of this invented character, I
> instead match everything.
>
> ===
>
> #!/usr/bin/perl -w
> use strict;
>
> my $text = "Cuisine: Urban deli<ep>";
> $text .= "Overall: <star><star><star><star><1/2> (very good to
> excellent)<ep>";
> $text .= "Food: <star><star><star><star><1/2><ep>";
>
> $text =~ s/\<star\>/_STAR_/ig; # uscores easier in regex than angle
> brackets.
> $text =~ s/_STAR_/\xbc/g; # change pseudocharacter to single
> character
> $text =~ s/(\xbc*)/_STARFONT_$1_ENDSTAR/g; #bracket groups in more
> pseudocode
>
> print $text;
>
> ====
>
> If I limit the search to five consecutive stars, the match works as I
> intended:
>
> ===
>
> #!/usr/bin/perl -w
> use strict;
>
> my $text = "Cuisine: Urban deli<ep>";
> $text .= "Overall: <star><star><star><star><1/2> (very good to
> excellent)<ep>";
> $text .= "Food: <star><star><star><star><1/2><ep>";
>
> $text =~ s/\<star\>/_STAR_/ig; # uscores easier in regex than angle
> brackets.
> $text =~ s/_STAR_/\xbc/g; # change pseudocharacter to single
> character
> $text =~ s/(\xbc{1,5})/_STARFONT_$1_ENDSTAR/g; #bracket groups of
> stars in more pseudocode
>
> print $text;
>
> ===
>
> So what am I missing when it comes to the first search?
>
> Certainly, I am missing some superior technique for matching repeated
> instances of such a string, so I am open to suggestions there.
In the first regular expression you are matching '\xbc*' and in the
second you are matching '\xbc{1,5}'. The '*' modifier matches *zero* or
more times and there are *zero* '\xbc' characters everywhere in the
string. The second one has to match at least *one* character. Change
'\xbc*' to '\xbc+'.
John
--
Perl isn't a toolbox, but a small machine shop where you
can special-order certain sorts of tools at low cost and
in short order. -- Larry Wall
------------------------------
Date: Fri, 25 Jan 2008 17:16:31 -0800 (PST)
From: Summercool <Summercoolness@gmail.com>
Subject: regular expression negate a word (not character)
Message-Id: <27249159-9ff3-4887-acb7-99cf0d2582a8@n20g2000hsh.googlegroups.com>
somebody who is a regular expression guru... how do you negate a word
and grep for all words that is
tire
but not
snow tire
or
snowtire
so for example, it will grep for
winter tire
tire
retire
tired
but will not grep for
snow tire
snow tire
some snowtires
need to do it in one regular expression
------------------------------
Date: Fri, 25 Jan 2008 18:15:36 -0800 (PST)
From: Summercool <Summercoolness@gmail.com>
Subject: Re: regular expression negate a word (not character)
Message-Id: <dcc47564-126d-47eb-9675-6456c5de23e3@d21g2000prg.googlegroups.com>
On Jan 25, 5:16 pm, Summercool <Summercooln...@gmail.com> wrote:
> somebody who is a regular expression guru... how do you negate a word
> and grep for all words that is
>
> tire
>
> but not
>
> snow tire
>
> or
>
> snowtire
i could think of something like
/[^s][^n][^o][^w]\s*tire/i
but what if it is not snow but some 20 character-word, then do we need
to do it 20 times to negate it? any shorter way?
------------------------------
Date: Fri, 25 Jan 2008 18:42:19 -0800 (PST)
From: paulaireilly <paulaireilly@gmail.com>
Subject: Re: regular expression negate a word (not character)
Message-Id: <0fda4784-27be-4783-872a-b03ff4e5cfe8@d70g2000hsb.googlegroups.com>
On Jan 25, 8:16 pm, Summercool <Summercooln...@gmail.com> wrote:
> somebody who is a regular expression guru... how do you negate a word
> and grep for all words that is
>
> tire
>
> but not
...
> snow tire
> snow tire
> some snowtires
>
> need to do it in one regular expression
You might be looking for a <b>negative lookahead assertion</b>. Look
that up in a handy
source. The syntax is approximately
(?!foo) --> will match at any place "betwee" chars not immediately
preceded by a"foo".
Now, you have to add in the "bar" afterwards. But remember that
(?!foo) takes up zero width. And be careful about /.*/ matching
anything including zero
chars.
I would say more but this looks sorta like a homework assignment to
me. So this is a "hint" post. I or someone else could do a "solution"
post later, but just having the phrase
"negative lookahead assertion" to look up on the Web or in a book
index will probably
answer all your questions.
Note that what you *really* want is a "negative lookbehind assertion",
to put right in front of the "tire" in your example (or my "bar"), but
I think those won't be working until Perl 6.
------------------------------
Date: Sat, 26 Jan 2008 03:27:31 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: regular expression negate a word (not character)
Message-Id: <3ulq65-c4j.ln1@osiris.mauzo.dyndns.org>
Quoth paulaireilly <paulaireilly@gmail.com>:
>
> You might be looking for a <b>negative lookahead assertion</b>. Look
<snip>
>
> Note that what you *really* want is a "negative lookbehind assertion",
> to put right in front of the "tire" in your example (or my "bar"), but
> I think those won't be working until Perl 6.
No, they work perfectly well in Perl 5, at least for fixed-length
strings. Syntax is (?<= ) and (?<! ). In 5.10 you can get
variable-length positive (but not negative) lookbehind at the start of
the match using \K.
Ben
------------------------------
Date: Sat, 26 Jan 2008 03:37:53 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: regular expression negate a word (not character)
Message-Id: <hhmq65-c4j.ln1@osiris.mauzo.dyndns.org>
[newsgroups line fixed, f'ups set to clpm]
Quoth Summercool <Summercoolness@gmail.com>:
> On Jan 25, 5:16 pm, Summercool <Summercooln...@gmail.com> wrote:
> > somebody who is a regular expression guru... how do you negate a word
> > and grep for all words that is
> >
> > tire
> >
> > but not
> >
> > snow tire
> >
> > or
> >
> > snowtire
>
> i could think of something like
>
> /[^s][^n][^o][^w]\s*tire/i
>
> but what if it is not snow but some 20 character-word, then do we need
> to do it 20 times to negate it? any shorter way?
This is no good, since 'snoo tire' fails to match even though you want
it to. You need something more like
/ (?: [^s]... | [^n].. | [^o]. | [^w] | ^ ) \s* tire /ix
but that gets *really* tedious for long strings, unless you generate it.
Ben
------------------------------
Date: Fri, 25 Jan 2008 20:40:23 -0800
From: "Mark Tolonen" <mark.e.tolonen@mailinator.com>
Subject: Re: regular expression negate a word (not character)
Message-Id: <teKdnXLQwsYpJAfanZ2dnUVZ_jOdnZ2d@comcast.com>
"Summercool" <Summercoolness@gmail.com> wrote in message
news:27249159-9ff3-4887-acb7-99cf0d2582a8@n20g2000hsh.googlegroups.com...
>
> somebody who is a regular expression guru... how do you negate a word
> and grep for all words that is
>
> tire
>
> but not
>
> snow tire
>
> or
>
> snowtire
>
> so for example, it will grep for
>
> winter tire
> tire
> retire
> tired
>
> but will not grep for
>
> snow tire
> snow tire
> some snowtires
>
> need to do it in one regular expression
>
What you want is a negative lookbehind assertion:
>>> re.search(r'(?<!snow)tire','snowtire') # no match
>>> re.search(r'(?<!snow)tire','baldtire')
<_sre.SRE_Match object at 0x00FCD608>
Unfortunately you want variable whitespace:
>>> re.search(r'(?<!snow\s*)tire','snow tire')
Traceback (most recent call last):
File "<interactive input>", line 1, in <module>
File "C:\dev\python\lib\re.py", line 134, in search
return _compile(pattern, flags).search(string)
File "C:\dev\python\lib\re.py", line 233, in _compile
raise error, v # invalid expression
error: look-behind requires fixed-width pattern
>>>
Python doesn't support lookbehind assertions that can vary in size. This
doesn't work either:
>>> re.search(r'(?<!snow)\s*tire','snow tire')
<_sre.SRE_Match object at 0x00F93480>
Here's some code (not heavily tested) that implements a variable lookbehind
assertion, and a function to mark matches in a string to demonstrate it:
### BEGIN CODE ###
import re
def finditerexcept(pattern,notpattern,string):
for matchobj in
re.finditer('(?:%s)|(?:%s)'%(notpattern,pattern),string):
if not re.match(notpattern,matchobj.group()):
yield matchobj
def markexcept(pattern,notpattern,string):
substrings = []
current = 0
for matchobj in finditerexcept(pattern,notpattern,string):
substrings.append(string[current:matchobj.start()])
substrings.append('[' + matchobj.group() + ']')
current = matchobj.end() #
substrings.append(string[current:])
return ''.join(substrings)
### END CODE ###
>>> sample='''winter tire
... tire
... retire
... tired
... snow tire
... snow tire
... some snowtires
... '''
>>> print markexcept('tire','snow\s*tire',sample)
winter [tire]
[tire]
re[tire]
[tire]d
snow tire
snow tire
some snowtires
--Mark
------------------------------
Date: Fri, 25 Jan 2008 22:40:36 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Relying on $_
Message-Id: <445q65-mkh.ln1@osiris.mauzo.dyndns.org>
Quoth Ted Zlatanov <tzz@lifelogs.com>:
> On Thu, 24 Jan 2008 12:15:57 -0500 Bernie Cosell
> <bernie@fantasyfarm.com> wrote:
>
> BC> As a matter of style and expectation, I'm wondering about relying on $_.
> BC> Often, just for convenience I'll do a no-var foreach. For example:
>
> BC> Is this a bug [even if a minor one] in the package? If not, what are the
> BC> rules for when you should and shouldn't expect $_ to get messed up?
>
> I'd say if there's more than two lines of code in the loop code, don't
> use $_. It is very handy for map/grep/postfix-foreach loops but can
> make life hell otherwise.
This is probably an appropriate time to point out 5.10 has a lexical $_:
~% perl5.10.0 -E'
sub foo { say shift; $_ = 1; }
my $_; foo $_ for 2, 3, 4;
'
2
3
4
Ben
------------------------------
Date: Fri, 25 Jan 2008 19:31:12 -0800
From: sln@netherlands.co
Subject: Re: Search/Replace text in XML file
Message-Id: <bs8lp3l5d9tgs3i0ogpo0eupr7vreo3nrf@4ax.com>
On Wed, 9 Jan 2008 11:21:41 -0800 (PST), Lax <lax_reddy@hotmail.com> wrote:
>Hello all,
>I'm trying to search and replace the value of a tag in an xml file.
>I'm not in a position to use the usual XML parsers as the version of
>Perl I'm required to use
>doesnt contain any of the XML libraries. I can use Text::Balanced, but
>I want to deal with the xml file on a
>line-by-line basis, as the value of my tag could strecth over multiple-
>lines.
>
>Perl Version:
>This is perl, v5.8.7 built for sun4-solaris
>
>Sample xml file:
>-------------------------
>
><project xmlns="xml:header">
>
> <version>1.0.0</version>
>
> <SomeTag>
> <version>invalid version</version>
> </SomeTag>
>
>
> <SomeAnotherTagNested1>
> <SomeAnotherTagNested2>
> <SomeAnotherTagNested3>
> <version>invalid version</version>
> </SomeAnotherTagNested3>
> </SomeAnotherTagNested2>
> </SomeAnotherTagNested1>
>
> <version>stand-alone, but not valid either</version>
>
></project>
>
>-------------------------
>
>I only want the version tag when they're not enclosed in any other
>tags.
>I want to replace the 1.0.0 (an example value) with 2.0.0 on an stand-
>alone "version"'s first occurence.
>I came up with the following:
>
>--------------------
>
>#!/usr/local/bin/perl
>
>use strict ;
>use File::Copy ;
>
>die "Usage: replace.pl <xml file>!\n" unless ( $#ARGV == 0 ) ;
>my $file = shift ;
>
>open(IN,"$file") or die "Cant open file: $!\n" ;
>chomp(my @arr = <IN> ) ;
>close(IN) ;
>
>open(OUT,"> bak") or die "Cant open file: $!\n" ;
>
># Two flags,
># $tag_flag -- to check if we're inside a tag
># $version_flag -- to check if we've replaced version tag already.
>
>my $tag_flag = "off" ;
>my $version_flag = "off" ;
>
>foreach my $line ( @arr )
>{
> # Dont consider the open and close of top-level <project> tag.
> if ( $line =~ /^\s*\<(\/)?project/ )
> {
> print OUT "$line\n" ;
> next ;
> }
>
> # Found <version>, replace version string if tag_flag is on and
>version_flag is off.
> elsif ( ($line =~ /^\s*\<version\>/) && ( $tag_flag eq "off" ) &&
>( $version_flag eq "off" ) )
> {
> # print "Flag: $flag\n" ;
> print OUT "<version>2.0.0</version>\n" ;
> $tag_flag = "on" ;
> $version_flag = "on" ;
> }
>
> # Inside an open tag "<", tag_flag on.
> elsif ( ( $line =~ /^\s*\<.*\>/ ) && ( $line !~ /^\s*\<\/.*
>\>/ ) )
> {
> print OUT "$line\n" ;
> $tag_flag = "on" ;
> }
>
> # Inside a close tag "</", tag_flag on.
> elsif ( $line =~ /^\s*\<\/.*\>/ )
> {
> print OUT "$line\n" ;
> $tag_flag = "off" ;
> } else {
> print OUT "$line\n" ;
> }
>}
>close(OUT) ;
>
># Move bak file to original
>
>------------------------------------------
>
>The above script works, and a "diff bak <xml-file>" gives me the
>expected result when the stand-alone <version> is all on one line, I
>cant get this working when its extended over multiple-lines.
>
>Could anyone give me some pointers, please?
>
>Thanks,
>Lax
I'm working on a modification of a module I wrote to do this type of thing (started last week).
But what you have stated on top is that you want to first "find" a version element that is "not"
inside of another element. This is hard to do bro.
You don't want to setup a search of tags with conditionals (in the general sense.) Its not like
regexpresions for xml. In the limited sense, as a basis, a search is setup as a singular for that "tag".
Should it encounter another identical "tag", does the search start over even if you have found "sub-tags"
in a tree, thereby invalidating this search, resetting it. Anchored/Unanchored (outer/inner if you will).
In parsing XML its easy to push/pop tags to determine validity. So its easy to say, find tag1->tag2->...
Inner/outer may be selectable. What about attribute names as conditionals? tag1->tag2->attr.
What about other items? What about content? Should content be a condition?
What should happen when all the conditions are met? What should be replaced, the tag, the attribute name/value,
the content? What if the content is spread over other items before closure?
To integrate a search & replace engine into a stream parser is a dificult task indeed. I am going to start slow,
tags and attributes first and move up from there.
------------------------------
Date: Fri, 25 Jan 2008 18:40:35 -0800
From: sln@netherlands.co
Subject: Version 5.8.8.8 html docs are shifted over (hidden) about 4 or 5 pixels to the left off the frame. WTF?
Message-Id: <t77lp3l5muv7t6e4ra1p5msn1o8edn623v@4ax.com>
Does anybody els have this problem? Its so anoying I wan't to go back to 5.8.6.
------------------------------
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:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#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 1234
***************************************
