[28441] in Perl-Users-Digest
Perl-Users Digest, Issue: 9805 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 5 00:05:43 2006
Date: Wed, 4 Oct 2006 21:05:07 -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 Wed, 4 Oct 2006 Volume: 10 Number: 9805
Today's topics:
$test <> ${test} <curtis@gr8.ch>
Re: $test <> ${test} anno4000@radom.zrz.tu-berlin.de
Re: $test <> ${test} <tadmc@augustmail.com>
Re: FAQ 5.2 (Was: inserting lines) <tadmc@augustmail.com>
Re: FAQ 5.2 (Was: inserting lines) <tadmc@augustmail.com>
Re: FAQ 5.2 (Was: inserting lines) jgraber@ti.com
Re: FAQ 5.2 <uri@stemsystems.com>
Re: One-Liner Help with -e + ksh heredoc anno4000@radom.zrz.tu-berlin.de
Re: One-Liner Help with -e + ksh heredoc <tadmc@augustmail.com>
Re: Please help me pass an array from VBA to Perl and p <mark.clementsREMOVETHIS@wanadoo.fr>
Problem with string comparison <mkazmierski@gmail.com>
Re: Problem with string comparison <wahab@chemie.uni-halle.de>
Re: Problem with string comparison <someone@example.com>
Re: Problem with string comparison <mgarrish@gmail.com>
Re: Problem with string comparison <tadmc@augustmail.com>
Re: Problem with string comparison <wahab@chemie.uni-halle.de>
question on File::Tail <iang@optonline.net>
Re: Validating Date-Time Ranges in a Schedule Database <1usa@llenroc.ude.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 5 Oct 2006 00:07:55 +0200
From: "Curtis M. West" <curtis@gr8.ch>
Subject: $test <> ${test}
Message-Id: <88f22$452430bb$50dbbc05$2957@news.hispeed.ch>
hello NG
can anyone tell me, what the difference between $test and ${test} is?
my $test = "abc";
print $test;
my $test = "abc";
print ${test};
both of the above examples do exactly the same?!
tnx & greet, curtis
------------------------------
Date: 4 Oct 2006 22:28:47 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: $test <> ${test}
Message-Id: <4oiqsvFeotsnU2@news.dfncis.de>
Curtis M. West <curtis@gr8.ch> wrote in comp.lang.perl.misc:
> hello NG
>
> can anyone tell me, what the difference between $test and ${test} is?
>
> my $test = "abc";
> print $test;
>
> my $test = "abc";
> print ${test};
>
> both of the above examples do exactly the same?!
That's because the meaning of $test and ${test} is exactly the same.
The difference is only relevant when a variable is interpolated in a
string, as in "this is the value: $test". If what follows the
variable name could also be part of the variable name, the {}
can be used to separate the name from surrounding text:
"here$testthere" would try to interpolate the variable $testthere.
"here${test}there" interpolates $test.
Anno
------------------------------
Date: Wed, 4 Oct 2006 17:45:04 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: $test <> ${test}
Message-Id: <slrnei8ebg.548.tadmc@magna.augustmail.com>
Curtis M. West <curtis@gr8.ch> wrote:
> Subject: $test <> ${test}
[
I doubt you want the diamond operator there.
I expect you meant either
$test ne ${test}
or
$test != ${test}
:-)
]
> can anyone tell me, what the difference between $test and ${test} is?
There are no semantic differences.
I think the syntactic difference is rather obvious. :-)
> my $test = "abc";
> print $test;
>
> my $test = "abc";
> print ${test};
>
> both of the above examples do exactly the same?!
Yes.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Wed, 4 Oct 2006 17:26:08 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: FAQ 5.2 (Was: inserting lines)
Message-Id: <slrnei8d80.4s1.tadmc@magna.augustmail.com>
brian d foy <brian.d.foy@gmail.com> wrote:
> In article <slrnei5ta3.uhj.tadmc@magna.augustmail.com>, Tad McClellan
><tadmc@augustmail.com> wrote:
>
>
>> You should probably review the answer that was there before 5.8.0
>> (which I liked better than what we have now).
>
>
>> Here is the POD from 5.6.1 for easy reference (=head2 line wrapped by me):
>>
>> ------------------------------------------------------
>> =head2 How do I change one line in a file/delete a line in a file/
>> insert a line in the middle of a file/append to the beginning of a
>> file?
>
> The old answer doesn't answer any of the questions.
I am embarrassed that I read the whole thing without noticing that. :-)
And in-place editing seems not a good choice for answering this
question either come to think of it.
I think the FAQ would benefit from just adding some examples:
Setup the tied array (see the Tie::File documentation):
use Tie::File;
tie @array, 'Tie::File', 'filename' or die $!;
Then to change the 5th line:
$array[4] =~ s/bar/baz/; # arrays start at zero, lines start at one
Or to delete the 5th line:
splice @array, 4, 1;
Or to insert a new 5th line:
splice @array, 4, 0, "this is a new line\n";
Of to append a new line at the beginning of the file:
unshift @array, "new line 1\n";
Or some such.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Wed, 4 Oct 2006 17:39:33 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: FAQ 5.2 (Was: inserting lines)
Message-Id: <slrnei8e15.548.tadmc@magna.augustmail.com>
brian d foy <brian.d.foy@gmail.com> wrote:
> In article <031020061558043174%jgibson@mail.arc.nasa.gov>, Jim Gibson
><jgibson@mail.arc.nasa.gov> wrote:
>
>> I recently complained about the lack of alternate approaches to the FAQ
>> "How do I change one line in a file/delete a line in a file/insert a
>> line in the middle of a file/append to the beginning of a file?"
> Anyway, here's the new answer.
[snip new answer]
That was really good.
Better than the old FAQ, better than the new FAQ, and better than
Jim's and my suggested changes.
You're pretty good at this.
I vote for you to replace that slacker that has been maintaining
the FAQ up to this point!
heh.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 04 Oct 2006 19:57:12 -0500
From: jgraber@ti.com
Subject: Re: FAQ 5.2 (Was: inserting lines)
Message-Id: <yvnhcyjy3yv.fsf@famous02.dal.design.ti.com>
brian d foy <brian.d.foy@gmail.com> writes:
> In article <031020061558043174%jgibson@mail.arc.nasa.gov>, Jim Gibson
> <jgibson@mail.arc.nasa.gov> wrote:
> The basic idea of inserting, changing, or deleting a line from a text
> file involves reading and printing the file to the point you want to
> make the change, making the change, then reading and printing the rest
> of the file. Perl doesn't provide random access to lines (especially
> since the record input separator, C<$/>, is mutable), although modules
> such as C<Tie::File> can fake it.
But Perl does provide random access to characters (bytes?)
a collection of them make up a line.
I've posted before on such methods as using RW random access
and overwriting the existing file in place.
1. overwriting "\ntext" with " " is similar to deleting a "line"
from top or middle of a file.
2. trunc is same as deleting a line from end of file
3. you can keep two filepointers to the same file,
and delete lines on the fly while overwriting the same file.
One example of this is gzip in place.
A trivial example is slurp, edit in memory, rewrite to same file.
4. A bigger buffer will let you insert/prepend lines while copying over the
same file as well.
But then I'm overly concerned with performance and diskspace
when processing many gzipped files whose aggregate size
is large compared to the available diskspace.
The above methods may not be advisable in the general case
nor appropriate for a FAQ entry, but I thought I'd mention them here.
Otherwise even the new answer still doesn't answer any of the questions,
since it mostly discusses making a modified copy of a file,
at least until "in-place" in mentioned.
Perhaps "... printing the file to the point ..."?
could be mis-construed to be hard-copy paper...
> A Perl program to do these tasks takes the basic form of opening a
> file, printing its lines, then closing the file:
>
> open my $in, '<', $file or die "Can't read old file: $!";
> open my $out, '>', "$file.new" or die "Can't write new file: $!";
I often use the following form of error message similar to recommended
by Perl Best Practices page 209, which works well for built up filenames
such as the example "$file.new"
Is it too clumsy to put in the FAQ in places like this?
my $fo; # shortened variable name for posting....
open my $in, '<', $fi or die "Can't read old file '$fi': $!";
open my $out, '>', $fo="$file.new" or die "Can't write new file '$fo': $!";
If you are recommending error checking on open,
why not also check for errors on close,
to make sure the disk did not fill up?
Similar issues are mentioned in recent thread
Subject: Revert inplace edit on HUP or full disk
--
Joel
------------------------------
Date: Wed, 04 Oct 2006 20:23:12 -0400
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: FAQ 5.2
Message-Id: <x7lknvfw5r.fsf@mail.sysarch.com>
>>>>> "TM" == Tad McClellan <tadmc@augustmail.com> writes:
TM> brian d foy <brian.d.foy@gmail.com> wrote:
>> In article <031020061558043174%jgibson@mail.arc.nasa.gov>, Jim Gibson
>> <jgibson@mail.arc.nasa.gov> wrote:
>>
>>> I recently complained about the lack of alternate approaches to the FAQ
>>> "How do I change one line in a file/delete a line in a file/insert a
>>> line in the middle of a file/append to the beginning of a file?"
>> Anyway, here's the new answer.
TM> [snip new answer]
TM> That was really good.
TM> Better than the old FAQ, better than the new FAQ, and better than
TM> Jim's and my suggested changes.
TM> You're pretty good at this.
TM> I vote for you to replace that slacker that has been maintaining
TM> the FAQ up to this point!
TM> heh.
just tell them both that another variant will be available soonish so
this would need an update again. i am adding edit_file (with some
variations) to file_slurp which can also solve this problem and with
less code than most of the given solutions.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: 4 Oct 2006 22:19:43 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: One-Liner Help with -e + ksh heredoc
Message-Id: <4oiqbvFeotsnU1@news.dfncis.de>
Tad McClellan <tadmc@augustmail.com> wrote in comp.lang.perl.misc:
> anno4000@radom.zrz.tu-berlin.de <anno4000@radom.zrz.tu-berlin.de> wrote:
> > s/war/peace/g; <smalder73@gmail.com> wrote in comp.lang.perl.misc:
> >> I'm in the midst of writing a ksh script. I've got a file of junk I
> >> need to manipulate with some hash magic in perl, but I'm trying to keep
> >> the perl code encapsulated in my ksh script. I'm trying to do
> >> something like this...
> >>
> >> perl -e 'magic' -i file
> >>
> >> But I want the magic to look more like...
> >>
> >> perl -e <<EOF
> >> magic
> >> EOF
> >> -i file
> >>
> >> This way the code is not cryptic. So far I can not seem to make this
> >> work... am I on crack for thinking I should be able to do something
> >> like this? Any suggestions?
> >
> > You are misunderstanding ksh here documents. They don't return
> > a string, they supply the given text via standard input.
>
>
> they supply the given text right "here" (where the here-doc appears),
> hence the name "here document".
Yes, that's where the text comes from. It goes to stdin of the command
it (i.e. the leading <<EOF) is part of.
Anno
------------------------------
Date: Wed, 4 Oct 2006 17:34:34 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: One-Liner Help with -e + ksh heredoc
Message-Id: <slrnei8dnq.548.tadmc@magna.augustmail.com>
anno4000@radom.zrz.tu-berlin.de <anno4000@radom.zrz.tu-berlin.de> wrote:
> Tad McClellan <tadmc@augustmail.com> wrote in comp.lang.perl.misc:
>> anno4000@radom.zrz.tu-berlin.de <anno4000@radom.zrz.tu-berlin.de> wrote:
>> > s/war/peace/g; <smalder73@gmail.com> wrote in comp.lang.perl.misc:
>> >> I'm in the midst of writing a ksh script. I've got a file of junk I
>> >> need to manipulate with some hash magic in perl, but I'm trying to keep
>> >> the perl code encapsulated in my ksh script. I'm trying to do
>> >> something like this...
>> >>
>> >> perl -e 'magic' -i file
>> >>
>> >> But I want the magic to look more like...
>> >>
>> >> perl -e <<EOF
>> >> magic
>> >> EOF
>> >> -i file
>> >>
>> >> This way the code is not cryptic. So far I can not seem to make this
>> >> work... am I on crack for thinking I should be able to do something
>> >> like this? Any suggestions?
>> >
>> > You are misunderstanding ksh here documents. They don't return
>> > a string, they supply the given text via standard input.
>>
>>
>> they supply the given text right "here" (where the here-doc appears),
>> hence the name "here document".
>
> Yes, that's where the text comes from. It goes to stdin of the command
> it (i.e. the leading <<EOF) is part of.
I can now see that _I_ am also misunderstanding ksh here documents.
Sorry.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 05 Oct 2006 00:50:57 +0200
From: Mark Clements <mark.clementsREMOVETHIS@wanadoo.fr>
Subject: Re: Please help me pass an array from VBA to Perl and populate it. Newbie at wits' end!
Message-Id: <45243aca$0$27389$ba4acef3@news.orange.fr>
Dr.Ruud wrote:
> Michele Dondi schreef:
>> david.f.jenkins:
>
>>> I can't execute an external program or shove files around, because of
>>> performance implications, mostly. I need a "sub" (but one written in
>>> Perl) that I can call from VBA.
>> (Un)fortunately I don't know enough VBA (namely, no VBA at all) to
>> address your question. My naive answer would be along the lines that
>> it's not possible, period. But indeed there may be some
>> framework/technology that allows this. Hope someone will know better.
>
> VBA can call members of libraries, at least .dll.
> So if there would be a perllib.dll or such, it would be possible.
>
Perl classes can be wrapped as COM components. See Windows Script
Components.
Mark
------------------------------
Date: 4 Oct 2006 16:26:17 -0700
From: "mark" <mkazmierski@gmail.com>
Subject: Problem with string comparison
Message-Id: <1160004377.744650.59130@i42g2000cwa.googlegroups.com>
Hello,
I have following program in linux:
open(DATA, "/etc/hostname");
$hostname = <DATA>;
print $hostname
if ($hostname eq "debian01") {
print "OK";
}
close(DATA);
Now, when I execute it I just got:
debian01
so it seems that $hostdata = "debian01" but there is no 'OK' string :/.
What is wrong?!? How can I make it working?!?
Regards, mark
------------------------------
Date: Thu, 05 Oct 2006 01:50:55 +0200
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: Problem with string comparison
Message-Id: <eg1hle$bf6$1@mlucom4.urz.uni-halle.de>
Thus spoke mark (on 2006-10-05 01:26):
> I have following program in linux:
> ...
> Now, when I execute it I just got:
> debian01
> so it seems that $hostdata = "debian01" but there is no 'OK' string :/.
> What is wrong?!? How can I make it working?!?
> open(DATA, "/etc/hostname");
> $hostname = <DATA>;
> print $hostname
> if ($hostname eq "debian01") {
> print "OK";
> }
> close(DATA);
there are some problems, most
will be found by Perl if you
start your program with:
use warnings;
use strict;
...
To read the content into a scalar,
you could 'slurp' the file, but
for beginners, its better to read
into an array and take the first
element as the first line:
open(my $data, '<', '/etc/hostname') or die "problem: $!";
my @lines = <$data>;
my $hostname = $lines[0];
close $data;
To compare strings, you don't need
always a string comparison operator:
if ( $hostname =~ /debian01/ ) {
print "OK";
}
means: if the string 'debian01' is found
somewhere on the first line pulled from
the array. Otherwise, it wouldn't work
because the "\n" is still in the string.
Regards
Mirco
------------------------------
Date: Thu, 05 Oct 2006 00:09:27 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Problem with string comparison
Message-Id: <X2YUg.51489$E67.39207@clgrps13>
mark wrote:
>
> I have following program in linux:
>
> open(DATA, "/etc/hostname");
> $hostname = <DATA>;
> print $hostname
> if ($hostname eq "debian01") {
> print "OK";
> }
> close(DATA);
>
> Now, when I execute it I just got:
> debian01
> so it seems that $hostdata = "debian01"
No, it is actually "debian01\n". You have to use chomp to remove the newline
first:
perldoc -f chomp
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: 4 Oct 2006 17:15:43 -0700
From: "Matt Garrish" <mgarrish@gmail.com>
Subject: Re: Problem with string comparison
Message-Id: <1160007343.779065.3340@m73g2000cwd.googlegroups.com>
Mirco Wahab wrote:
> Thus spoke mark (on 2006-10-05 01:26):
>
> > I have following program in linux:
> > ...
> > Now, when I execute it I just got:
> > debian01
> > so it seems that $hostdata = "debian01" but there is no 'OK' string :/.
> > What is wrong?!? How can I make it working?!?
>
> > open(DATA, "/etc/hostname");
> > $hostname = <DATA>;
> > print $hostname
> > if ($hostname eq "debian01") {
> > print "OK";
> > }
> > close(DATA);
>
> there are some problems, most
> will be found by Perl if you
> start your program with:
>
> use warnings;
> use strict;
> ...
>
> To read the content into a scalar,
> you could 'slurp' the file, but
> for beginners, its better to read
> into an array and take the first
> element as the first line:
>
> open(my $data, '<', '/etc/hostname') or die "problem: $!";
> my @lines = <$data>;
> my $hostname = $lines[0];
> close $data;
>
You're assuming that there's more in the file and that he's trying to
slurp (I don't see $/ being set to undef in his code). It's common
practice to read the first line into a scalar if, for example, the file
contains a count / timestamp / some other single value that's being
persisted. Using an array is just wasteful extra step, even for
beginners.
> To compare strings, you don't need
> always a string comparison operator:
>
> if ( $hostname =~ /debian01/ ) {
> print "OK";
> }
>
> means: if the string 'debian01' is found
> somewhere on the first line pulled from
> the array. Otherwise, it wouldn't work
> because the "\n" is still in the string.
>
Or you just chomp your line and use an equality check. You're
contradicting what you wrote above by giving this advice, though.
Regular expression checking requires much more careful consideration
than most beginners generally give them, so if you're assuming a
beginner audience it seems odd you'd provide this example instead of
just mentioning chomp (for example, what happens to the OP if the first
line actually contains "debian011a").
Matt
------------------------------
Date: Wed, 4 Oct 2006 19:35:11 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Problem with string comparison
Message-Id: <slrnei8kpv.5a9.tadmc@magna.augustmail.com>
mark <mkazmierski@gmail.com> wrote:
> I have following program in linux:
>
> open(DATA, "/etc/hostname");
You are missing a check of the return value to see if you
actually got what you asked for.
> $hostname = <DATA>;
You are missing a chomp().
> print $hostname
You are missing a semicolon.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 05 Oct 2006 02:32:37 +0200
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: Problem with string comparison
Message-Id: <eg1k3k$c96$1@mlucom4.urz.uni-halle.de>
Thus spoke Matt Garrish (on 2006-10-05 02:15):
> Mirco Wahab wrote:
>> Thus spoke mark (on 2006-10-05 01:26):
>> > I have following program in linux:
>> > ...
>> open(my $data, '<', '/etc/hostname') or die "problem: $!";
>> my @lines = <$data>;
>
> You're assuming that there's more in the file and that he's trying to
> slurp (I don't see $/ being set to undef in his code). It's common
> practice to read the first line into a scalar if, for example, the file
> contains a count / timestamp / some other single value that's being
> persisted. Using an array is just wasteful extra step, even for
> beginners.
You are correct, of course - but what I
sometimes found is the mistake of genera-
lizing later the reading of <> into a scalar
(as the OP did here - and what worked here).
To make things more explicit, I provided
the disputed example.
>> To compare strings, you don't need
>> always a string comparison operator:
>>
>> if ( $hostname =~ /debian01/ ) {
>> print "OK";
>> }
>>
>> means: if the string 'debian01' is found
>> somewhere on the first line pulled from
>> the array. Otherwise, it wouldn't work
>> because the "\n" is still in the string.
>
> Or you just chomp your line and use an equality check.
Actually, when I wrote the response,
I had the line
chomp($hostname = $lines[0]);
but dropped that in favor of
the /searchterm/ notation, which I
believed to be much more general here
and in the near future, especially if
you want /i and more ...
> You're contradicting what you wrote above by giving this advice, though.
> Regular expression checking requires much more careful consideration
> than most beginners generally give them, so if you're assuming a
> beginner audience it seems odd you'd provide this example instead of
> just mentioning chomp (for example, what happens to the OP if the first
> line actually contains "debian011a").
I tried to make a proper decision but may have failed
or somehow taken the wrong turn, ok. But starting
from the /searchterm/, it is imho straightforward
to jump softly into regular expressions by gradually
adding ...$/ and similar things.
Regards & Thanks
Mirco
------------------------------
Date: 4 Oct 2006 20:06:03 -0700
From: "golden" <iang@optonline.net>
Subject: question on File::Tail
Message-Id: <1160017563.684535.301360@h48g2000cwc.googlegroups.com>
Hello All,
I have program that tails a file using file::tail and also periodically
logs to a log file.
The name of the file that I tail changes frequently the format of which
is <file_yyyymmdd_pid.log>.
I would like to put a small "heartbeat message" to my log file. In
that file I wish to also include the current file name that is being
tailed.
I found that file::tail has an input method that simply displays the
logfile name. I have a function that determines the appropriate log
file. and use the "name_change" method to deal with that.
My question is can somebody help me determine how to write to my log
file periodically ( if the read is blocking waiting for data on the
file taile object.
Thanks in advance.
Ian
------------------------------
Date: Thu, 05 Oct 2006 01:53:55 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Validating Date-Time Ranges in a Schedule Database
Message-Id: <Xns9852DED193EECasu1cornelledu@127.0.0.1>
"John" <ClipperMiami@gmail.com> wrote in news:1159997978.837729.104600
@e3g2000cwe.googlegroups.com:
> Can anyone propose a change to the SQL that will detect the conflict in
> both cases without tripping false conflicts?
>
First off, it looks like you have difficulty diagnosing the most effective
way of solving your problem. This group is about Perl, you are more likely
to get SQL help here.
I will point out that if you had designed your tables differently, you
would have been able to solve this problem in a more straightforward way
in SQL.
My guess is, if you post your SQL and table design on
comp.databases.theory, you will get very illuminating answers.
If you want to solve your problem in Perl (although I would recommend
reconsidering the design of the database), you'll need to read the posting
guidelines, and post some Perl code so we know what to help you with.
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
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 9805
***************************************
