[25203] in Perl-Users-Digest
Perl-Users Digest, Issue: 7449 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 26 06:06:15 2004
Date: Fri, 26 Nov 2004 03:05: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 Fri, 26 Nov 2004 Volume: 10 Number: 7449
Today's topics:
Re: CGI.PM not setting HTTP header <toreau@gmail.com>
Re: CGI.PM not setting HTTP header <nospam@thanksanyway.org>
Re: CGI.PM not setting HTTP header <amead@comcast.net>
Re: character encoding in CGI.pm <jwkenne@attglobal.net>
Re: character encoding in CGI.pm <flavell@ph.gla.ac.uk>
Re: Dat files help "Att James" hope@hope.com
FAQ 7.10: How do I create a class? <comdog@panix.com>
FAQ 7.13: What is variable suicide and how can I preven <comdog@panix.com>
Re: for Richard Gration <bik.mido@tiscalinet.it>
help for exec with command lines with spaces (PilotMI80)
Re: Help: separate difference length of spaces between <bik.mido@tiscalinet.it>
Re: List::Util::shuffle - where did the algorithm come <postmaster@castleamber.com>
Re: List::Util::shuffle - where did the algorithm come (Anno Siegel)
Re: looking for a better regexp <someone@example.com>
Re: Perl 6 <bik.mido@tiscalinet.it>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 26 Nov 2004 04:42:08 +0100
From: Tore Aursand <toreau@gmail.com>
Subject: Re: CGI.PM not setting HTTP header
Message-Id: <pan.2004.11.26.03.42.08.267687@gmail.com>
On Thu, 25 Nov 2004 09:47:48 -0800, Mark wrote:
>> Is the server written in Perl?
> It's an Apache server.
...and Apache, last time I checked, is not written in Perl. Your problem,
as you describe it, is that the _web server_ (Apache) is not sending the
correct header(s) to the client.
Thus, this isn't a Perl problem at all. At least you haven't showed us
the _Perl relevant_ information to make it a Perl problem.
I'm not emphasizing this just to be rude or something, but sometimes (ie.
always) it's smarter to post a question in the most relevant newsgroups.
--
Tore Aursand <toreau@gmail.com>
"What we do is never understood, but only praised and blamed."
(Friedrich Nietzsche)
------------------------------
Date: Thu, 25 Nov 2004 21:39:41 -0800
From: "Mark" <nospam@thanksanyway.org>
Subject: Re: CGI.PM not setting HTTP header
Message-Id: <35mdnRtvT7ULXDvcRVn-hw@speakeasy.net>
"Alan J. Flavell" <flavell@ph.gla.ac.uk> wrote
> As it turned out, you've solved your problem by using CGI.pm better.
> It's still not (quite) a Perl language problem, and might have been
> more at home on a usenet group that's primarily about the CGI, but
> you've rubbed-up several of the respected contributors here in the
> wrong way, and I wouldn't really recommend that: they may prove
> infinitely helpful to you in future, if you give them the idea that
> you're keen to learn.
I certainly do not believe that I said or did anything even remotely
offensive.
------------------------------
Date: Fri, 26 Nov 2004 01:15:42 -0600
From: Alan Mead <amead@comcast.net>
Subject: Re: CGI.PM not setting HTTP header
Message-Id: <pan.2004.11.26.07.15.42.153984@comcast.net>
On Thu, 25 Nov 2004 08:41:34 -0800, Mark wrote:
> So. . .it appears that the web server will output an HTTP header
> for each instance of a CGI object that I create? Is there any way
No, I think the server adds something but it doesn't print the
headers. It's up to you to print an appropriate header (usually
"print header" after importing the CGI shortcuts) once for each
HTML page that you create.
You might wonder why? Well, headers are also the way you transmit cookies
and do things like redirect. So you want to control them in your program
rather than have the server do it... or automatically by CGI.pm.
-Alan
------------------------------
Date: Thu, 25 Nov 2004 23:03:19 -0500
From: "John W. Kennedy" <jwkenne@attglobal.net>
Subject: Re: character encoding in CGI.pm
Message-Id: <41a6ab08$1@nap.mtholyoke.edu>
Ben Morrow wrote:
> Correct me if I'm wrong, but surely XHTML cannot be served under a
> text/html content type anyway? It isn't valid HTML (take this document,
> for example,
If you want Internet Explorer to display it, you /must/ serve it as
text/html. Internet Explorer refuses outright to render a document that
it knows to be XHTML. Fortunately, most browsers will produce acceptable
results for XHTML 1.0 served as HTML. XHTML 2.0 served as HTML, on the
other hand, will go straight into the toilet.
In short, XHTML is dead, murdered by Bill Gates' arrogance.
Ain't monopolies great?
--
John W. Kennedy
"Only an idiot fights a war on two fronts. Only the heir to the throne
of the kingdom of idiots would fight a war on twelve fronts"
-- J. Michael Straczynski. "Babylon 5", "Ceremonies of Light and Dark"
------------------------------
Date: Fri, 26 Nov 2004 10:49:43 +0000
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: character encoding in CGI.pm
Message-Id: <Pine.LNX.4.61.0411261015330.24563@ppepc56.ph.gla.ac.uk>
Oh dear. Off topic, but I can't resist at least a reply... with
apologies up-front
On Thu, 25 Nov 2004, John W. Kennedy wrote:
> Ben Morrow wrote:
> > Correct me if I'm wrong, but surely XHTML cannot be served under a
> > text/html content type anyway? It isn't valid HTML (take this
> > document, for example,
>
> If you want Internet Explorer to display it, you /must/ serve it as
> text/html.
IE, as normally used, does not support XHTML, and it would be better
not to send it any. Faking XHTML as HTML brings no benefits at all at
the web interface, and adds a few disbenefits. It's sometimes claimed
that XML-based tools at the authoring side are a valuable benefit, and
therefore the result will be XHTML - but that is a half-truth:
XML-based tools can also emit HTML/4.01 as their end-product.
> Internet Explorer refuses outright to render a document that it
> knows to be XHTML.
Right from the start of the WWW, browsers which can't render a
particular MIME content-type have been configured to fire up a
suitable "helper application" to view that content type.
More recently there's been a tendency to define "plug-ins", which
render certain content types but display them in the window of the
browser.
Either of these mechanisms should be available in IE (after
sacrificing a suitable animal to XP SP2, I suppose). Years back I
configured Windows/IE to use a "helper application" for opening XHTML
MIME-types, and I defined the helper application to be Mozilla. It
worked fine. OK, I'm not promoting it in that form as a practical
solution for end-users, just offering an in-principle refutation that
if the browser-like object doesn't support it then it can't be used.
The original idea of XML was to make a clean break with "tag soup".
> Fortunately, most browsers will produce acceptable results for XHTML
> 1.0 served as HTML.
Unfortunately, that's led to the unwashed masses of web deezyners
simply converting their HTML-flavoured tag soup into XHTML-flavoured
tag soup, and tossing the potential benefits of the clean break out of
the window (no pun intended).
> XHTML 2.0 served as HTML, on the other hand, will go
> straight into the toilet.
So the bottom line is:
- XHTML/1.0 Appendix C is functionally identical to HTML/4.01, and
almost - but not quite - as compatible with tag-soup slurpers. So
what's the point of deploying XHTML/1.0 to browsers which were never
designed to process it? If the original isn't HTML, XHTML/1.0 can be
converted by rote into HTML/4.01, and the result is slightly more
compatible with the browsers out there.
No other version of XHTML offers that easement. By definition, if you
serve it out as text/html it cannot be XHTML(tm), other than this
pointless, self-contradictory and counter-productive backwater:
XHTML/1.0-Appendix-C. What it would be is XHTML-flavoured tag soup,
which is no kind of improvement from what we already had.
I say choose one of:
* stay with HTML/4.01 - there's no point in XHTML/1.0; or
* make a clean break and move to Real XHTML(tm), with some kind of
Accept-type negotiation for client agents which don't grok it.
> In short, XHTML is dead, murdered by Bill Gates' arrogance.
XHTML is alive and well in a subset of client agents, with useful
extras like SVG. Content-type negotiation (Accept: header) has been
working for years; IE contrives (like so much else) to get it only
vaguely right, but with a bit of sleight of hand at the server it can
be made to work with IE's default settings, and the more-aware can
adjust the Accept: header (or have it adjusted for them) to get better
results.
IMHO and YMMV.
------------------------------
Date: Fri, 26 Nov 2004 08:22:13 GMT
From: hope@hope.com
Subject: Re: Dat files help "Att James"
Message-Id: <mtodq01a3tm68j4l9j8s433g6upqgi1kjc@4ax.com>
On Thu, 25 Nov 2004 19:02:29 -0600, Tad McClellan <tadmc@augustmail.com> wrote:
>hope@hope.com <hope@hope.com> wrote:
>> On Thu, 25 Nov 2004 13:46:28 -0600, Tad McClellan <tadmc@augustmail.com> wrote:
>>>hope@hope.com <hope@hope.com> wrote:
>>>> On Wed, 24 Nov 2004 14:26:58 -0800, Jim Gibson <jgibson@mail.arc.nasa.gov> wrote:
>>>>>In article <h2r9q0lpmkd35tc7g1qkhbtova6gcm4lbg@4ax.com>,
>>>>><hope@hope.com> wrote:
>>>
>>>
>>>>>> use CGI:: Carp dw(fatelsToBrowser)
> ^
> ^
>>>>>Spelling counts.
>
>>>> I see the mistakes now it should be
>>>>>> use CGI ::Carp qw<fatelsToBrowser>;
> ^
> ^
>>>There is *still* a typo there you know...
>>
>> Ok so you mean should be "(" instead of ">"
>
>
>Sheesh man, wake up!
>
>He said *spelling* counts.
>
>Punctuation is not spelling.
>
>You have misspelled something there, even after being told that
>you have misspelled something there.
Ok take your point, Have you looked at something time and time again and cannot spot the mistake ? well that is what happened to me
How stupid of me
Now I see it
use CGI::Carp qw(fatalsToBrowser);
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa not eeeeeeeeeeeeeeeee
Hows that :))
>>>>>These are warnings, not fatal errors, but they may be significant.
>Spelled correctly. That should be helpful to you.
>
>>>> open my $out, '+>/home/me/outfile' or die $!;
>>>
>>>
>>>Why do you open it for input AND output when you are only
>>>using it for output?
>>
>> I do not know why
>
>You should not run code that you don't understand...
Well that is why I'm in here trying to understand it and get some help with it, as well as reading
>
>> In my very first post to this group on this subject A very kind person named James wrote this script for me
>
>
>... because *bad* guys also post code on the web, hoping to lure
>people into running it for them.
>
>Don't be their patsy.
>
>(I am not talking about James here, of course.)
Hmmmmm so what you are saying that people in here can give you very bad code to harm you
>
>
>>>> read $fh, my $data, -s $fh;
>>>> my @fields = split /\n/, $data;
>
>
>That is a mighty strange way of reading in the data...
>
> chomp( my @fields = <$fh> ); # does the same thing, no temp variable
Hmmmm so in other words like you said up above bad code
>
>
>>>>>From the above, I might guess that $dir is undefined.
>>>
>>>And it still is.
>>
>> Ok I see that now, BUT I have done some searches on how to define and all I came up with was
>>
>> my $dir = '/xxx/xxx';
>
>Yes, exactly so.
>
>
>> So the director where my dat files are in WinXp pro are
>> c:\1\35
> ^^
> ^^
>> So I put
>> my $dir = '/1/35';
>> But that did not work
>
>
>How come you didn't put the "c:" part in there?
>
> my $dir = 'c:/1/35';
Oh my god this just gets worse as it goes along
I went and did a search for paths in perl for windows and apache
at this site
http://perlmonks.thepen.com/110030.html
In Perl you can generally just use a / as your path separator (except on Mac OS 9, thanks Hanamaki). Why? Because Perl will automagically convert the / to the correct path
separator for the system it is running on! This means that coding Windows paths like this
$path = "\\foo\\bar\\baz";
is not required. You can just use this:
$path = "/foo/bar/baz";
so that is why I left out the c:
------------------------------
Date: Fri, 26 Nov 2004 05:03:00 +0000 (UTC)
From: PerlFAQ Server <comdog@panix.com>
Subject: FAQ 7.10: How do I create a class?
Message-Id: <co6de4$sj2$1@reader1.panix.com>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
7.10: How do I create a class?
See perltoot for an introduction to classes and objects, as well as
perlobj and perlbot.
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
------------------------------
Date: Fri, 26 Nov 2004 11:03:02 +0000 (UTC)
From: PerlFAQ Server <comdog@panix.com>
Subject: FAQ 7.13: What is variable suicide and how can I prevent it?
Message-Id: <co72h6$4vv$1@reader1.panix.com>
This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.
--------------------------------------------------------------------
7.13: What is variable suicide and how can I prevent it?
Variable suicide is when you (temporarily or permanently) lose the value
of a variable. It is caused by scoping through my() and local()
interacting with either closures or aliased foreach() iterator variables
and subroutine arguments. It used to be easy to inadvertently lose a
variable's value this way, but now it's much harder. Take this code:
my $f = "foo";
sub T {
while ($i++ < 3) { my $f = $f; $f .= "bar"; print $f, "\n" }
}
T;
print "Finally $f\n";
The $f that has "bar" added to it three times should be a new $f ("my
$f" should create a new local variable each time through the loop). It
isn't, however. This was a bug, now fixed in the latest releases (tested
against 5.004_05, 5.005_03, and 5.005_56).
--------------------------------------------------------------------
Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short. They represent an important
part of the Usenet tradition. They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.
If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile. If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.
Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release. It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.
The perlfaq manual page contains the following copyright notice.
AUTHOR AND COPYRIGHT
Copyright (c) 1997-2002 Tom Christiansen and Nathan
Torkington, and other contributors as noted. All rights
reserved.
This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.
------------------------------
Date: Fri, 26 Nov 2004 09:14:17 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: for Richard Gration
Message-Id: <r4ecq0pe96gl50bq2akb5k13h5ledtcote@4ax.com>
On Wed, 24 Nov 2004 16:30:35 -0500, "daniel kaplan"
<nospam@nospam.com> wrote:
>i can only assure you that i never your reply NEVER hit my newserver, as
>neither did my OP...guess i should toss out OE, it's far from perfect....but
>that's for a different rant...
Sorry for answering while still failing to be Richard Gration...
AFAICT! ;-)
However notwithstanding the fact that I fully afree on your cmt about
OE, the problem you had probably has nothing to do with it. That is
how USENET is supposed to work. I'm afraid you'll have to live with
it...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 26 Nov 2004 00:41:49 -0800
From: pilotmi80@hotmail.com (PilotMI80)
Subject: help for exec with command lines with spaces
Message-Id: <9b14a223.0411260041.13c43b58@posting.google.com>
Hi,
I try to issue the command :
c:\program files\flashget\flashget.exe http:\\url.with.no.white.space
d:\a directory
(same can be tested with any prog that need a directory (potentially
containing whitespaces) as a parameter )
the url parameter does not contain whitespace so it is not a matter
so far, I tried many combinations (to escape baskslashes and quotes)
with the back tick (seems to work better for me although i don't need
the output), and with exec but to no avail :
here are a few :
1.
exec "c:\\program files\\flashget\\flashget.exe url d:\\a directory";
output> 'c:\program' not found (expected)
2.
exec "\"c:\\program files\\flashget\\flashget.exe\" url";
works ok but
exec "\"c:\\program files\\flashget\\flashget.exe\" \"url\"";
outputs 'c:\program' not found
3.
my @exe = ("\"c:\\program files\\flashget\\flashget.exe\" url \"d:\a
directory\"");
exec {$exe[0] } @exe; #as read in the manual
outputs nothing but does nothing because the command issue is wrong
(I assume the program is not the whole line so...)
4.
my @exe = ("\"c:\\program files\\flashget\\flashget.exe\"");
exec {$exe[0]} @exe, url; # or "url" or 'url' or " url" or ' url' ...
compiles but does nothing
I run out of ideas and am still stuck, by now, i do something like
this :
`"\"c:\\program files\\flashget\\flashget.exe\" url d:\\a_directory\"
which works but is quite limited.
any suggestion ?
thanks
------------------------------
Date: Fri, 26 Nov 2004 09:14:18 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Help: separate difference length of spaces between words
Message-Id: <27ccq0dthif284vnfk3q1ka5teclosp29l@4ax.com>
On Thu, 25 Nov 2004 03:34:08 GMT, Jim Keenan
<jkeen_via_google@yahoo.com> wrote:
># rough code: untested
>my (@data);
Why not
my @data;
instead? i.e. do (unnecessary) parens really add to readability?
>while (<FH>) {
> my @temp = split(/\s+/, $_);
Why explicitly using something that will be used anyways? Why not
writing
my @temp = split /\s+/;
instead? While we're there, why not using
my @temp = split;
instead? It's not *exactly* the same, but it is what the OP wants,
anyways...
> push(@data, [@temp[0..1]);
Why C<0..1> when it is just the same as C<0,1>?
All in all, why not
push @data, (split)[0,1] while <FH>;
(i.e. no need for intermediate variables)?
No offense intended,
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 26 Nov 2004 02:36:39 GMT
From: John Bokma <postmaster@castleamber.com>
Subject: Re: List::Util::shuffle - where did the algorithm come from?
Message-Id: <Xns95ACD1A9192E7castleamber@130.133.1.4>
Richard Gration wrote:
> On Thu, 25 Nov 2004 19:03:04 +0000, Richard Gration wrote:
>
> Ah, sorry, got sidetracked. The reason I was looking at this sub is to
> see if I could adapt it to not shuffle certain elements of the list
> based on arbitrary criteria. "Not easily" was my answer. Can anyone
> suggest how I could do this?
put elements that should be shuffled in a list, shuffle it and combine the
two.
--
John Small Perl scripts: http://johnbokma.com/perl/
Perl programmer available: http://castleamber.com/
Happy Customers: http://castleamber.com/testimonials.html
------------------------------
Date: 26 Nov 2004 09:59:22 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: List::Util::shuffle - where did the algorithm come from?
Message-Id: <co6upq$fri$1@mamenchi.zrz.TU-Berlin.DE>
Richard Gration <richard@zync.co.uk> wrote in comp.lang.perl.misc:
> On Thu, 25 Nov 2004 19:03:04 +0000, Richard Gration wrote:
>
> Ah, sorry, got sidetracked. The reason I was looking at this sub is to see
> if I could adapt it to not shuffle certain elements of the list based on
> arbitrary criteria. "Not easily" was my answer. Can anyone suggest how I
> could do this?
Use an array slice.
Suppose you want to shuffle a list of strings @l but keep all elements
in place that begin with "a".
my @mobile = grep $l[ $_] !~ /^a/, 0 .. $#l;
@l[ @mobile] = shuffle( @l[ @mobile]);
Anno
------------------------------
Date: Fri, 26 Nov 2004 07:01:09 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: looking for a better regexp
Message-Id: <VwApd.191108$df2.9494@edtnps89>
mike wrote:
>
> i have to strip a line of empty spaces/tabs before and after a comma
> eg word1, word2 ,word3,word4<tab>,word5
> i have to make it become word1,word2,word3,word4,word5
>
> so far i have tried
> $line =~ s/^\s+//; #get rid of spaces in the beginining of the line
> $line =~ s/^\t+//; #get rid of tabs in the beginning of the line
> $line =~ s/\s+,/,/g ; #get rid of spaces before a comma
> $line =~ s/,\s+/,/g; #get rid of spaces after a comma
> $line =~ s/\t+,/,/g; #get rid of tables before comma
> $line =~ s/,\t+/,/g; #get rid of tabs after comma
>
> i may have the line also containing eg
> word1, word2 <2 tabs> ,word3,word4<1 tab><space><space>,word5
> or other combinations of spaces/tabs .
>
> Is there a better way to do the regexp? I just need the output to be
> word1,word2,word3,word4,word5
You could do it like this:
$line = join ',', map { s/^\s+//; s/\s+$//; $_ } split /,/, $line;
John
--
use Perl;
program
fulfillment
------------------------------
Date: Fri, 26 Nov 2004 09:14:19 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Perl 6
Message-Id: <9cccq09rsv20s3vgc4chv6oi72kkps0md9@4ax.com>
On Thu, 25 Nov 2004 07:17:45 +0100, Tore Aursand <toreau@gmail.com>
wrote:
>I found this image quite entertaining;
>
> <http://otierney.net/images/perl6.gif>
Well I don't agree with whomever made that image, but I must admit
it's well done...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
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 V10 Issue 7449
***************************************
