[25400] in Perl-Users-Digest
Perl-Users Digest, Issue: 7645 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 14 00:10:26 2005
Date: Thu, 13 Jan 2005 21:10:18 -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 Thu, 13 Jan 2005 Volume: 10 Number: 7645
Today's topics:
Re: Perl CGI does not generate file. <gazza@192.168.1.1>
Re: Perl CGI does not generate file. <gazza@192.168.1.1>
Re: Perl CGI does not generate file. <sbryce@scottbryce.com>
Re: Perl CGI does not generate file. <noreply@gunnar.cc>
Re: Perl CGI does not generate file. <sbryce@scottbryce.com>
Re: Print question <1usa@llenroc.ude.invalid>
Re: Random Functionality <sbryce@scottbryce.com>
Re: Regular expression lookahead question xhoster@gmail.com
Re: Regular expression lookahead question <abigail@abigail.nl>
Re: Regular expression lookahead question <matthew.garrish@sympatico.ca>
Re: Regular expression lookahead question <matthew.garrish@sympatico.ca>
Re: Regular expression lookahead question <matthew.garrish@sympatico.ca>
Re: Regular expression lookahead question <matthew.garrish@sympatico.ca>
Re: Some question?! <djames@thehub.com.au>
Re: Unix-format text from STDOUT under Windows (AcitveP <bart.lateur@pandora.be>
Re: Unix-format text from STDOUT under Windows (AcitveP <jimmonty@gmail.com>
Re: Works great! <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 14 Jan 2005 01:37:57 GMT
From: Gazza <gazza@192.168.1.1>
Subject: Re: Perl CGI does not generate file.
Message-Id: <VnFFd.539$VE5.109@newsfe2-win.ntli.net>
Paul Lalli wrote:
> "Gazza" <gazza@192.168.1.1> wrote in message
> news:rJuFd.169$VE5.153@newsfe2-win.ntli.net...
>> I have written an HTML script
>
> This is a contradiction in terms
Oops, you're right! Sorry. :-)
>> The HTML script is here:
>>
>
http://homepage.ntlworld.com/gary.hayward/My_HTML_Scripts/perl_cgi_file_creator.html
>>
>> (cut and paste from source view) and the Perl CGI script is here:
>>
>>
>
http://homepage.ntlworld.com/gary.hayward/My_Perl_Scripts/perl_cgi_file_creator.txt
>>
>
> Why didn't you just copy and paste the code yourself? That would have
> been far more polite. Regardless:
All the scripts (those that really are: BASH, Perl, etc) on my web site for
downloading are in plain text so I thought I would have my HTML pages like
that, but then I thought, by leaving them with the '.html' extension,
people could see what they looked like straight away -- only a minor thing,
I know, but they are HTML on a web server. I used to include code in my
newsgroup postings but thought, with two longish files it might look a mess
and be irritating. I do go and am going to go to considerable lengths to
make stuff I make available for others easy to access and use on an ongoing
basis.
>
>> $input3=<STDIN>;
>> $input3=~s/\+/ /g;
>> @input4 = split(/&/, $input3);
>> foreach $time(0,1) {
>> $input4[$time]=~s/%([\dA-Fa-f]{2})/pack("C", hex($1))/eg;
>> $input4[$time]=~s/</</g;
>> }
>> $input4[0]=~s/nameoffiletocreate=//;
>> $input4[1]=~s/filetext=//;
>>
>> print <<endofhtml;
>
> <HTML snipped>
>
> You are attempting to parse CGI parameters yourself. This is a bad
> idea. You should be using a module that does this task for you. That
> module is CGI.pm. Please read up on it at
> perldoc CGI
Thanks and I'll bear that in mind :-) (although, as a 'newbie', I feel I am
going to have to be doing without calling modules for the time being so I
can learn the basics of the language by doing things the
'hard'/'long-winded' way).
>
> Using that module, the entirety of the above code would be reduced to:
> @input4 = (param('nameoffiletocreate'), param('filetext'));
>
>> endofhtml
>>
>> open WF,">$input4[0]";
>> print WF "$input4[1]";
>> close WF;
>
>> What have I done wrong?
>
> You have not checked the return value of open. You have no idea if this
> open succeeded. Perl will tell you that, and will also tell you *why*
> it failed - but you have to tell it to tell you:
>
> open WF "> $input4[0]" or die "Could not open $input4[0] for writing:
> $!";
>
The 'die' stuff was on my computer's version of the Perl script and I didn't
update the web-hosted one which I should have done.
> Now if that open fails, your script will terminate, and the error
> message will be printed to your error log. If you do not have access to
> the error log, add this line to the top of your script:
>
> use CGI::Carp qw/fatalsToBrowser/;
>
> That will cause the error to be displayed in your browser.
Thank you. That code was very helpful.
>
> Once you have done this, you will likely be told exactly why your
> program fails. As an offhand guess, I'd bet the CGI user doesn't have
> permissions to create a new file.
>
The error I got was that that the file couldn't be written as there was no
such file existing. I thought that may be due to the script not having the
right permission on directories it needed to go through to get to where it
had to write the file (the Opera browser I use simply reports, 'Could not
open file' when browsing to a directory I don't have permission to access;
it doesn't tell you everything). Trying a different directory, I got
permission denied messages despite all the directories in the file's path
being owned by and set up with the right permissions for the user running
the browser and invoking the Perl script. The only time I got it to work
was when I specified '/tmp/[file_name]' as the destination. The HTML page
(watered down) and Perl CGI script are part of a web-based web site
administrator's tool set that I've written for myself (in case anybody was
wondering, which you probably weren't :-)) to administrate one of my web
sites. One Perl script that I have uploaded to my web server does manage
to create files without any problems (it's used to log visitor's IP
addresses and other visitor stats in a file) so, hopefully, this admin.
Perl script will work there (although I need to look at how secure things
would be before I implement it there).
> Paul Lalli
Thanks for your help.
Yours,
Gary Hayward.
------------------------------
Date: Fri, 14 Jan 2005 01:57:13 GMT
From: Gazza <gazza@192.168.1.1>
Subject: Re: Perl CGI does not generate file.
Message-Id: <ZFFFd.549$3g5.412@newsfe5-win.ntli.net>
Tad McClellan wrote:
> Gazza <gazza@192.168.1.1> wrote:
>
>> CGI
>> script is supposed to then create the file with the text in it. It's
>> simple but, unfortunately, the file doesn't get created.
>
>> CGI script on a BASH command line like this:
>
>> (all one line, of course) works.
>
>
>> What have I done wrong?
>
>
> You did not check the Perl FAQ before posting to the Perl newsgroup.
>
> perldoc -q CGI
>
> 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?
>
>
Hi,
Point taken :-).
Yours,
Gary Hayward.
------------------------------
Date: Thu, 13 Jan 2005 19:07:06 -0700
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Perl CGI does not generate file.
Message-Id: <8fedncUJspujtHrcRVn-sw@comcast.com>
Paul Lalli wrote:
>>You are attempting to parse CGI parameters yourself. This is a bad
>>idea. You should be using a module that does this task for you. That
>>module is CGI.pm. Please read up on it at perldoc CGI
Gazza responded:
> Thanks and I'll bear that in mind :-) (although, as a 'newbie', I feel I am
> going to have to be doing without calling modules for the time being so I
> can learn the basics of the language by doing things the
> 'hard'/'long-winded' way).
You will probably get a lot of responses on this. If you want to learn
the basics of the language, you want to learn how to do things right.
Using CGI.pm is the RIGHT way to parse CGI parameters. You will learn
very little by writing your own code that does not work. If you are
going to use Perl to write CGI, using CGI.pm IS one of the basics.
Doing things the hard way is NOT a basic part of programming in Perl.
When there is a standard module that does the job for you, using that
module IS a basic part of programming in Perl.
------------------------------
Date: Fri, 14 Jan 2005 03:31:09 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Perl CGI does not generate file.
Message-Id: <34op8tF4ak0q7U1@individual.net>
Scott Bryce wrote:
> Gazza responded:
>> (although, as a 'newbie', I feel I am going to have to be doing
>> without calling modules for the time being so I can learn the
>> basics of the language by doing things the 'hard'/'long-winded'
>> way).
>
> Using CGI.pm is the RIGHT way to parse CGI parameters.
It's normally advisable to use it since it's convenient.
> You will learn very little by writing your own code ...
I'm amazed that you can be so sure of that. Even if I often use CGI.pm
today, I've previously used my own code successfully for years. Writing
that code helped me learn some Perl, and it also gave me valuable
insight in how CGI works.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Thu, 13 Jan 2005 20:32:07 -0700
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Perl CGI does not generate file.
Message-Id: <G46dnbi9Hoe2oHrcRVn-rQ@comcast.com>
Gunnar Hjalmarsson wrote:
> Scott Bryce wrote:
>> Using CGI.pm is the RIGHT way to parse CGI parameters.
>
>
> It's normally advisable to use it since it's convenient.
And more likely to be correct than parameter parsing code written by
someone who is new to the language. Unless, I suppose, he already knows
how to write bullet-proof CGI parameter passing routines in some other
language.
>> You will learn very little by writing your own code ...
>
>
> I'm amazed that you can be so sure of that. Even if I often use CGI.pm
> today, I've previously used my own code successfully for years. Writing
> that code helped me learn some Perl, and it also gave me valuable
> insight in how CGI works.
Of course, you are right.
When I first learned to write CGI in Perl, I had some wonderful examples
to go by courtesy of Matt Wright. One important lesson I learned early
on was to give up roll-your-own CGI parameter parsing and use CGI.pm.
One can certainly learn something about Perl and CGI by writing CGI
parameter parsing routines. But I think something that someone new to
writing CGI in Perl needs to learn is that CGI.pm is the preferred way
to do it, not just because it is convenient, but because it is more
likely to be right.
------------------------------
Date: 14 Jan 2005 03:24:23 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Print question
Message-Id: <Xns95DDE3EDA8BD7asu1cornelledu@132.236.56.8>
"edgrsprj" <edgrsprj@ix.netcom.com> wrote in
news:1imFd.5694$C52.3280@newsread2.news.atl.earthlink.net:
> "Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
> news:K82Fd.33124$TN6.1038398@news20.bellglobal.com...
>>
>> "edgrsprj" <edgrsprj@ix.netcom.com> wrote in message
>> news:F2ZEd.4034$KJ2.1086@newsread3.news.atl.earthlink.net...
>> >
>
>> Why are you asking us? I thought you wrote the documentation?
>>
>> http://www.freewebz.com/eq-forecasting/Perl.html
...
> That Web page was to a large degree intended to serve as an interim
> type of resource for people such as myself
I see, you don't know anything so you are qualified to write guides for
people who don't know anything. That makes perfect sense!
Sinan.
------------------------------
Date: Thu, 13 Jan 2005 16:34:56 -0700
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: Random Functionality
Message-Id: <DvydnVxklJQJmHrcRVn-uQ@comcast.com>
xhoster@gmail.com wrote:
> Are you having some kind of difficulty with the method you are currently
> using? If not, you don't need something better. If so, what is/are the
> problem(s) you are having?
I don't have a lot of experience working with references in Perl. The
code I posted was hacked together rather quickly last night. I was
reading about creating references to anonymous subroutines, and that led
me to write the code. It "works," but I was wondering if someone with
more Perl experience could suggest a better approach.
So this isn't a "I can't make this work" question, but a "can you review
my code?" question. Or, to borrow a word you used in your post, "Is this
approach dreck compared to what might be better approaches?"
Right now I'm leaning toward the approach suggested by Brian McCauley,
unless someone knows a good reason why I shouldn't be grabbing the list
of references from the symbol table.
So the latest rendition of the code looks like this:
use strict;
use warnings;
my @sub_list =
map { \&$_ }
grep { exists(&$_) }
map {"Handlers::$_"}
keys %::Handlers::;
print $sub_list[int rand @sub_list]->('stuff');
package Handlers;
sub One
{
return "Sub One was chosen.\n";
}
sub Two
{
return "Sub Two was chosen.\n";
}
sub Three
{
return "Sub Three was chosen.\n";
}
sub Four
{
my ($string) = @_;
return "You passed $string into sub Four.\n";
}
------------------------------
Date: 14 Jan 2005 00:06:03 GMT
From: xhoster@gmail.com
Subject: Re: Regular expression lookahead question
Message-Id: <20050113190603.775$I8@newsreader.com>
"zeebster" <gregaryh@juno.com> wrote:
> I am trying to parse an xml file for unprotected ampersands (&)
> I do not want to match ampersand characters that preceed a protected
> entity such as in the case of < or >
> After hours of copious searches I found something that looked like it
> would work using lookaheads:
> &(?!quot|lt|gt|amp)
Don't you want to force a ';' after the entities?
> However this does not seem to work. Can anyone give me a clue what I am
> doing wrong?
Yes, you aren't explaining what you mean when you say it does not seem to
work. You aren't posting working code which demonstrates the problem
you claim to have. You aren't following the posting guidelines.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: 14 Jan 2005 00:31:35 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Regular expression lookahead question
Message-Id: <slrncue4n7.e1.abigail@alexandra.abigail.nl>
zeebster (gregaryh@juno.com) wrote on MMMMCLIII September MCMXCIII in
<URL:news:1105657042.759998.176370@z14g2000cwz.googlegroups.com>:
{} I am trying to parse an xml file for unprotected ampersands (&)
{} I do not want to match ampersand characters that preceed a protected
{} entity such as in the case of < or >
{} After hours of copious searches I found something that looked like it
{} would work using lookaheads:
{} &(?!quot|lt|gt|amp)
{} However this does not seem to work. Can anyone give me a clue what I am
{} doing wrong?
You have a bug on line 17.
HTH. HAND.
Abigail
--
my $qr = qr/^.+?(;).+?\1|;Just another Perl Hacker;|;.+$/;
$qr =~ s/$qr//g;
print $qr, "\n";
------------------------------
Date: Thu, 13 Jan 2005 19:31:14 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regular expression lookahead question
Message-Id: <jpEFd.32549$b64.1007524@news20.bellglobal.com>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
news:njEFd.32545$b64.1006103@news20.bellglobal.com...
>
> <xhoster@gmail.com> wrote in message
> news:20050113190603.775$I8@newsreader.com...
>> "zeebster" <gregaryh@juno.com> wrote:
>>> I am trying to parse an xml file for unprotected ampersands (&)
>>> I do not want to match ampersand characters that preceed a protected
>>> entity such as in the case of < or >
>>> After hours of copious searches I found something that looked like it
>>> would work using lookaheads:
>>> &(?!quot|lt|gt|amp)
>>
>> Don't you want to force a ';' after the entities?
>>
>
> It's also not a valid way to alternate options, and you still need to
> check what is there:
>
> /&(?:(?!(quot|lt|gt|amp)).*);/
>
Actually, I sent that off without checking thoroughly. The above would
happily consider &foo; a valid entity.
Matt
------------------------------
Date: Thu, 13 Jan 2005 19:24:54 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regular expression lookahead question
Message-Id: <njEFd.32545$b64.1006103@news20.bellglobal.com>
<xhoster@gmail.com> wrote in message
news:20050113190603.775$I8@newsreader.com...
> "zeebster" <gregaryh@juno.com> wrote:
>> I am trying to parse an xml file for unprotected ampersands (&)
>> I do not want to match ampersand characters that preceed a protected
>> entity such as in the case of < or >
>> After hours of copious searches I found something that looked like it
>> would work using lookaheads:
>> &(?!quot|lt|gt|amp)
>
> Don't you want to force a ';' after the entities?
>
It's also not a valid way to alternate options, and you still need to check
what is there:
/&(?:(?!(quot|lt|gt|amp)).*);/
Matt
------------------------------
Date: Thu, 13 Jan 2005 20:03:46 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regular expression lookahead question
Message-Id: <PTEFd.32587$b64.1020778@news20.bellglobal.com>
"zeebster" <gregaryh@juno.com> wrote in message
news:1105657042.759998.176370@z14g2000cwz.googlegroups.com...
>I am trying to parse an xml file for unprotected ampersands (&)
> I do not want to match ampersand characters that preceed a protected
> entity such as in the case of < or >
> After hours of copious searches I found something that looked like it
> would work using lookaheads:
> &(?!quot|lt|gt|amp)
>
A negative lookahead is probably not the way to go:
my $str = 'Me & my &fudge. ';
my %entity = map { $_ => 1 } qw/amp lt gt quot/;
while ($str =~ /&([^\s;]+)([\s;])/g) {
print "No ending semi-colon: $1\n" if $2 =~ tr/ \r\n\t//;
print "Invalid entity: $1\n" unless $entity{$1};
}
Matt
------------------------------
Date: Thu, 13 Jan 2005 20:06:23 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Regular expression lookahead question
Message-Id: <fWEFd.32593$b64.1021373@news20.bellglobal.com>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
news:PTEFd.32587$b64.1020778@news20.bellglobal.com...
>
> "zeebster" <gregaryh@juno.com> wrote in message
> news:1105657042.759998.176370@z14g2000cwz.googlegroups.com...
>>I am trying to parse an xml file for unprotected ampersands (&)
>> I do not want to match ampersand characters that preceed a protected
>> entity such as in the case of < or >
>> After hours of copious searches I found something that looked like it
>> would work using lookaheads:
>> &(?!quot|lt|gt|amp)
>>
>
> A negative lookahead is probably not the way to go:
>
> my $str = 'Me & my &fudge. ';
>
> my %entity = map { $_ => 1 } qw/amp lt gt quot/;
>
> while ($str =~ /&([^\s;]+)([\s;])/g) {
>
> print "No ending semi-colon: $1\n" if $2 =~ tr/ \r\n\t//;
I've really got to go eat. The above could just be:
print "No ending semi-colon: $1\n" unless $2 eq ';';
Matt
------------------------------
Date: Fri, 14 Jan 2005 01:20:05 GMT
From: Damian James <djames@thehub.com.au>
Subject: Re: Some question?!
Message-Id: <slrncue7ec.8s2.djames@puli.local>
On Sat, 08 Jan 2005 01:38:38 GMT, Peter Wyzl said:
> "Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
> news:ZAGDd.68194$P%3.2359787@news20.bellglobal.com...
>:
>: "Jim Gibson" <jgibson@mail.arc.nasa.gov> wrote in message
>: news:070120051341269893%jgibson@mail.arc.nasa.gov...
>: >
>: >> 3.) Where to find free version of Cron for Windows?
>: >
>: > Don't know.
>: >
>:
>: Start -- Settings -- Control Panel -- Scheduled Tasks
>
> Or on WinNT and 2k,
> Start - Run - 'Cmd' - 'AT'
In NT4 and least, that is not available unless you install the NT4
resource kit. Not free.
Cheers,
Damian
--
@:=grep!(m!$/|#!..$|),split//,<DATA>;@;=0..$#:;while($:=@;){$;=rand
$:--,@;[$;,$:]=@;[$:,$;]while$:;push@|,shift@;if$;[0]==@|;select$,,
$,,$,,1/80;print qq x\bxx((@;+@|)*$|++),@:[@|,@;],!@;&&$/} __END__
Just another Perl Hacker,### http://home.pacific.net.au/~djames.hub
------------------------------
Date: Thu, 13 Jan 2005 23:07:04 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Unix-format text from STDOUT under Windows (AcitvePerl 5.8.x)?
Message-Id: <8lvdu0hlprs16d58skmvdjr2fgnrndfl9g@4ax.com>
Shawn Corey wrote:
>Jim Monty wrote:
>> Using ActivePerl 5.8.x for Windows, how do I make STDOUT output
>> Unix-format text instead of DOS-format text? In other words, I want to
>> force the output text to have LF-terminated lines, not CRLF-terminated
>> lines. The input text is DOS-format.
>You could try 'binmode'. I'm not running MS so I can't test it.
>
>perldoc -f binmode
That should work, yes. Note that "\n" on Windows is a LF, chr(10).
Reading from a text filehandle (no binmode) converts CRLF to "\n" on
input, and printinf to a text filehandle will convert "\n" into CRLF.
binmode prevents that conversion, leaving you with a "Unix text file".
--
Bart.
------------------------------
Date: 13 Jan 2005 17:55:48 -0800
From: "Jim Monty" <jimmonty@gmail.com>
Subject: Re: Unix-format text from STDOUT under Windows (AcitvePerl 5.8.x)?
Message-Id: <1105667748.877074.297630@z14g2000cwz.googlegroups.com>
Michael Carman wrote:
> Jim Monty wrote:
> > Using ActivePerl 5.8.x for Windows, how do I make STDOUT output
> > Unix-format text instead of DOS-format text?
>
> I too once looked into ways to have Perl generate text files in
> something other than the native platform format. IIRC, binmode()
worked
> for some situations but wasn't flexible enough for the general case.
I
> finally decided that it was better to either
>
> a) post-process the files, or
> b) use an FTP client to transfer them in ASCII mode
In fact, that's what I've been doing in this case: post-processing the
file.
C:\>perl ScriptThatUsesXMLWriter.pl Input.csv | tr -d "\r" >Output.xml
But now I'd like to be able to hand the Perl script to someone who will
have ActivePerl, but not necessarily tr (Cygwin or MKS Toolkit). Using
binmode() would work splendidly if I were controlling STDOUT, but I'm
not: XML::Writer is. (I explained this in a second follow-up post.)
Jim Monty
------------------------------
Date: Thu, 13 Jan 2005 22:12:34 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Works great!
Message-Id: <slrncuehli.2i7.tadmc@magna.augustmail.com>
Jim Gibson <jgibson@mail.arc.nasa.gov> wrote:
> The local declaration creates a
> temporary variable within the innermost enclosing block:
No it doesn't.
It creates a temporary *value* for a variable.
(If the variable does not exist, _then_ it will create it. If
the variable already exists, then it does not create it.)
What is local about local() is NOT the variable, but rather
the variable's value.
And the variable (along with its temporary value) are NOT local
but global.[1]
All local() variables are global variables.
Pretty friggin strange, but there you have it.
[1] put a subroutine call in the block, and it will see the local()
value, potentially many lines away, AKA action-at-a-distance.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
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 7645
***************************************
