[18232] in Perl-Users-Digest
Perl-Users Digest, Issue: 400 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Mar 2 18:10:37 2001
Date: Fri, 2 Mar 2001 15:10:21 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <983574620-v10-i400@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Fri, 2 Mar 2001 Volume: 10 Number: 400
Today's topics:
Global problem with array <iqbals8@cs.man.ac.uk>
Re: Global problem with array <maheshasolkar@yahoo.com>
Re: Help Matt with small programs <ren@tivoli.com>
Re: Help with sockets <dennis.kowalsk@daytonoh.ncr.com>
Re: Help with sockets <um@no.com>
Re: not sure to post it here (Ben Okopnik)
Re: Opening STDERR for input (Ilya Zakharevich)
Re: perl CGI output not shown in browser <simon@nospam.simonwebdesign.com>
Re: Perl CGI.pm RESET problem (BUCK NAKED1)
Re: Perl, Cookies, and Apache. <krahnj@acm.org>
Re: Perl, Cookies, and Apache. <jb@yperite.demon.co.uk>
Re: Perl, Cookies, and Apache. <jb@yperite.demon.co.uk>
Re: Perl, Cookies, and Apache. <jb@yperite.demon.co.uk>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 02 Mar 2001 20:51:08 +0000
From: Shazad Iqbal <iqbals8@cs.man.ac.uk>
Subject: Global problem with array
Message-Id: <3AA007BC.A6A7377E@cs.man.ac.uk>
Hi
I have just started using perl on a piece of work. What I want to do is
read the file and assign what I find to variables which are declared
global.
But when I use a variable outside the for loop, it doesnt recognise it.
The code is below could anyone see what I am doin wrong.
#!/opt/perl/bin/perl -w
use strict;
my $line;
my $Semester;
my $Day;
my $StartTime;
my $Type;
my $Week;
my $Course;
my $Group;
my $Room;
my @Semester;
my @Day;
my @StartTime;
my @Type;
my @Week;
my @Course;
my @Group;
my @Room;
my $index;
open USER, "table_pr"or die "Could not open file: $:";
# e.g. line
# 1 MONDAY 11.00 L Wa ab103_X Wind - AJWest PCCapon JSANDHAM
# Sem Day Time Typ Wk Crs Grp Rm - Rest
foreach $line (<USER>)
{
chomp $line;
if ( $line =~ m{^([12]) # sem
\s
(\S+) # day
\s+
([0-9]+\.[0-9]+) # Time
\s
(\S) # type
\s+
(\S+) # week
\s
([^_ ]+)(|_\S*) # course and group
\s+
(\S+) # room
\s+
(-.*)}x # ignore
)
{
@Semester=$1;
@Day=$2;
@StartTime=$3;
@Type=$4;
@Week=$5;
@Course=$6;
@Group=$7;
@Room=$8;
}
print "Courses @Course\t and it days @Day\t at the time @StartTime in
room @Room\n";
}
print "what module do u want information of?\n\n";
my $module_choice = <STDIN>;
chomp $module_choice;
print "The module you choice $module_choice\n";
for ($index=0; $index <= $#Course; $index++)
{
if ( $Course[$index] =~ /$module_choice/)
{
print " the module happens on $Day[$index], at $StartTime[$index].
The module is $Type[$index] in room $Room[$index]\n\n";
last;
}
else { print "You have not typed in an incorrect module\n";}
}
close USER;
Any help would be much appreciated.
SHazad iqbal
------------------------------
Date: Fri, 2 Mar 2001 13:40:24 -0800
From: "Mahesh A" <maheshasolkar@yahoo.com>
Subject: Re: Global problem with array
Message-Id: <ta04qa94bimab1@corp.supernews.com>
> #!/opt/perl/bin/perl -w
> use strict;
>
> my $line;
> my $Semester;
> my $Day;
> my $StartTime;
> my $Type;
> my $Week;
> my $Course;
> my $Group;
> my $Room;
> my @Semester;
> my @Day;
> my @StartTime;
> my @Type;
> my @Week;
> my @Course;
> my @Group;
> my @Room;
> my $index;
> open USER, "table_pr"or die "Could not open file: $:";
> # e.g. line
> # 1 MONDAY 11.00 L Wa ab103_X Wind - AJWest PCCapon JSANDHAM
> # Sem Day Time Typ Wk Crs Grp Rm - Rest
>
> foreach $line (<USER>)
> {
> chomp $line;
> if ( $line =~ m{^([12]) # sem
> \s
I had to make this \s+ to match the pattern, and gwt into the 'if'
> (\S+) # day
> \s+
> ([0-9]+\.[0-9]+) # Time
> \s
> (\S) # type
> \s+
> (\S+) # week
> \s
> ([^_ ]+)(|_\S*) # course and group
> \s+
> (\S+) # room
> \s+
> (-.*)}x # ignore
> )
> {
> @Semester=$1;
> @Day=$2;
> @StartTime=$3;
> @Type=$4;
> @Week=$5;
> @Course=$6;
> @Group=$7;
> @Room=$8;
I'd rather use...
push(@Semester,$1);
push(@Day,$2);
push(@StartTime,$3);
push(@Type,$4);
push(@Week,$5);
push(@Course,$6);
push(@Group,$7);
push(@Room,$8);
than t your assignments.
> }
> print "Courses @Course\t and it days @Day\t at the time @StartTime in
> room @Room\n";
> }
>
> print "what module do u want information of?\n\n";
> my $module_choice = <STDIN>;
> chomp $module_choice;
> print "The module you choice $module_choice\n";
>
> for ($index=0; $index <= $#Course; $index++)
> {
> if ( $Course[$index] =~ /$module_choice/)
> {
> print " the module happens on $Day[$index], at $StartTime[$index].
> The module is $Type[$index] in room $Room[$index]\n\n";
> last;
> }
> else { print "You have not typed in an incorrect module\n";}
I dont think this is a proper message here.
> }
> close USER;
>
>
> Any help would be much appreciated.
>
> SHazad iqbal
My modifications ...
#!/opt/perl/bin/perl -w
use strict;
my $line;
my $Semester;
my $Day;
my $StartTime;
my $Type;
my $Week;
my $Course;
my $Group;
my $Room;
my @Semester;
my @Day;
my @StartTime;
my @Type;
my @Week;
my @Course;
my @Group;
my @Room;
my $index;
$| = 1;
# open (DATA, "table_pr") || die "Could not open file: $:";
# e.g. line
# 1 MONDAY 11.00 L Wa ab103_X Wind - AJWest PCCapon JSANDHAM
# Sem Day Time Typ Wk Crs Grp Rm - Rest
while (<DATA>)
{
chomp;
if ( m{^([12]) # sem
\s+
(\S+) # day
\s+
([0-9]+\.[0-9]+) # Time
\s
(\S) # type
\s+
(\S+) # week
\s
([^_ ]+)(|_\S*) # course and group
# (\S+)_(\S*) # course and group
\s+
(\S+) # room
\s+
(-.*)
}x # ignore
)
{
push(@Semester,$1);
push(@Day,$2);
push(@StartTime,$3);
push(@Type,$4);
push(@Week,$5);
push(@Course,$6);
push(@Group,$7);
push(@Room,$8);
}
print "Courses $6\t and it days $2\t at the time $3 in room $8\n";
}
print "what module do u want information of?\n\n";
my $module_choice = <STDIN>;
chomp $module_choice;
print "The module you choice $module_choice\n";
my $match = 0;
for ($index=0; $index <= $#Course; $index++)
{
if ( $Course[$index] =~ /$module_choice/)
{
$match = 1;
print " the module happens on $Day[$index], at $StartTime[$index].
The module is $Type[$index] in room $Room[$index]\n\n";
last;
}
}
if (!$match) { print "You have not typed in an incorrect module\n";}
close DATA;
__DATA__
1 MONDAY 11.00 L Wa ab101_X Wind - AJWest PCCapon JSANDHAM
2 MONDAY 11.00 L Wa ab102_X Wind - AJWest PCCapon JSANDHAM
1 MONDAY 11.00 L Wa ab103_X Wind - AJWest PCCapon JSANDHAM
2 MONDAY 11.00 L Wa ab104_X Wind - AJWest PCCapon JSANDHAM
... Output ....
% perl arrays.pl
Courses ab101 and it days MONDAY at the time 11.00 in room Wind
Courses ab102 and it days MONDAY at the time 11.00 in room Wind
Courses ab103 and it days MONDAY at the time 11.00 in room Wind
Courses ab104 and it days MONDAY at the time 11.00 in room Wind
what module do u want information of?
ab104
The module you choice ab104
the module happens on MONDAY, at 11.00.
The module is L in room Wind
------------------------------
Date: 02 Mar 2001 14:55:50 -0600
From: Ren Maddox <ren@tivoli.com>
Subject: Re: Help Matt with small programs
Message-Id: <m3r90fevqh.fsf@dhcp9-175.support.tivoli.com>
On Thu, 1 Mar 2001, mshort@usol.com wrote:
> 1> $num=0;
> 2> while ($num>=0){
> 3> next if (int($num / 5) != ($num/5));
> 4> last if $num==100;
> 5> print "$num ";$num++;
> 6> }
It looks like you are still expecting "next" to cause $num to be
incremented. Anytime that first "if" is true, it will go to the next
iteration of the loop *without changing $num*.
There are lots of ways to fix it. Here is one:
$num=0;
while($num>=0) {
next if int($num / 5) != $num/5;
last if $num==100;
print "$num ";
} continue {
$num++;
}
Whenever "next" is called, it first executes the "continue" block and
then starts the next iteration of the loop. Also, if "next" isn't
called, the continue block is executed at the end of each iteration.
Of course, one you get to this, you have the exact format of a C-style
for loop:
for($num=0; $num>=0; $num++) {
next if int($num / 5) != $num/5;
last if $num==100;
print "$num ";
}
However, there are still a couple of oddities. First of all, your
loop conditional, "$num>=0", will always be true. Second, you are
exiting the loop when "$num==100", but only checking it if the you
don't happen to hit the "next" (which, naturally, you don't with these
values, but change the 5s to 6s and the loop never ends). The fix for
this is simply to use the correct loop conditional:
for($num=0; $num<100; $num++) {
next if int($num/5) != $num/5;
print "$num ";
}
Now, it might as well be:
for($num=0; $num<100; $num++) {
print "$num " if int($num/5) == $num/5;
}
Or, for in a more Perl-ish way:
int($_/5) == $_/5 and print "$_ " for 0..99; # requires 5.6
OR
print join " ", grep { int($_/5) == $_/5 } 0..99;
OR, just for fun :) :
print "@{[grep{int($_/5)==$_/5}0..99]}\n";
--
Ren Maddox
ren@tivoli.com
------------------------------
Date: Fri, 2 Mar 2001 15:25:07 -0500
From: "Dennis Kowalski" <dennis.kowalsk@daytonoh.ncr.com>
Subject: Re: Help with sockets
Message-Id: <3aa001a2$1@rpc1284.daytonoh.ncr.com>
Ben
Thanks for the reply.
But, I do not think your solution fits my problem.
I am trying to connect to a server on a remote host, send in a request for
data, then receive the output from the server program.
This dictates that my program does both sends and receives.
I have a C program that does it and it creates only 1 socket and does both
sends and receives on it.
I have checked the IPC web pages and they all show examples of a connect and
then a read, but I have not found an example of one that sends and receives.
Does anyone have a sample of a perl client program that does that?
Ben L. <um@no.com> wrote in message news:3a9b0092$1_2@news2.one.net...
> The problem is you are trying to send and receive through the same socket
in
> the same process. In the words of the Perl gods you should only attempt
> that if you are a real wizard, or if you are really into pain. What you
> need to do is modify your scirpt to fork an identical copy of itself ...
> with the parent reading the socket and the child writing to it (or
> vice-versa) ... that is the only way to accomplish the bi-directional
> communication you desire while remaining sane. There is some excellent
> sample code for this in the IPC (inter-process communication) tutorial:
>
> http://www.perl.com/pub/doc/manual/html/pod/perlipc.html
>
> Check out the interactive client example under the TCP with IO::Socket
> section. Enjoy!
>
> Ben
>
>
> Dennis Kowalski <dennis.kowalsk@daytonoh.ncr.com> wrote in message
> news:3a9a7571$1@rpc1284.daytonoh.ncr.com...
> > I am trying to write a script that connects to a server program, send
data
> > to it and get output back.
> >
> > I have a C program that does it, but now I am trying in Perl.
> >
> > I seem to connet to the server module OK.
> >
> > I build a message and send it.
> >
> > Then I receive off of the socket.
> >
> > The data I get, seems to be what I sent
> >
> > Can anybody look at the following code and tell me what is wrong?
> >
> > Doe anybode have some sample code that des what I am trying to do?
> >
> > SAMPLE CODE
> >
> > use IO::Socket;
> >
> > $port = '18059';
> > $ip = 'IP ADDRESS WAS HERE';
> > my $socket = new IO::Socket::INET (PeerAddr => $ip,
> > PeerPort => $port,
> > Proto => 'tcp')
> > or die "Can not connect to server.\n";
> > $socket->autoflush(1);
> >
> > # msg is built here
> >
> > # send the msg to the server
> > print $socket $output_rec;
> >
> > &read_socket;
> > exit;
> >
> > # routine to read the socket
> > sub read_socket
> > {
> > # read 2 byte vli, unpack it and subtract 2
> > $rcvrec = read ($socket,$vlib,2);
> > $vli = unpack("n",$vlib);
> > $vli2 = $vli -2;
> >
> > $buffin = 0;
> >
> > # read data portion from the socket
> >
> > $rcvrec = read ($socket,$buffin,$vli2);
> > if ($buffin)
> > {
> > print RCV $vlib;
> > print RCV $buffin;
> > }
> > 0;
> > }
> >
> >
> >
> >
>
>
------------------------------
Date: Fri, 2 Mar 2001 16:00:01 -0800
From: "Ben L." <um@no.com>
Subject: Re: Help with sockets
Message-Id: <3aa00c14$1_2@news2.one.net>
Yes, the IPC page DOES have an example, exactly the same one that I pointed
out. I understand what you are trying to do, and you can't do it the same
way in Perl that you do in C. In Perl, if you open a socket to a remote
host, and you write to the socket and then right after that you try to read
from the socket to get the remote host's response, it WILL NOT WORK. If you
fork() your process, and write in the parent and read in the child, you are
still using the same socket, and you can then send and receive with your
remote host without your script failing.
If you were to actually look at the example I mentioned, *INTERACTIVE*
client example using IO::Socket, you would see that the example SENDS and
RECEIVES using the SAME socket, like your C program does.
> I have checked the IPC web pages and they all show examples of a connect
and
> then a read, but I have not found an example of one that sends and
receives.
You didn't check very well; I gave you the exact URL and the exact
section that demonstrates what you want to do:
> > http://www.perl.com/pub/doc/manual/html/pod/perlipc.html
> >
> > Check out the interactive client example under the TCP with IO::Socket
> > section. Enjoy!
> >
------------------------------
Date: 2 Mar 2001 21:31:39 GMT
From: ben-fuzzybear@geocities.com (Ben Okopnik)
Subject: Re: not sure to post it here
Message-Id: <slrn9a04cp.u1j.ben-fuzzybear@Odin.Thor>
The ancient archives of Thu, 01 Mar 2001 15:42:23 -0500 showed
Lou Moran of comp.lang.perl.misc speaking thus:
>On 28 Feb 2001 23:16:04 +0000, nobull@mail.com wrote wonderful things
>about sparkplugs:
>
>>
>>[snip question in no way shape or form even remotely related to Perl ]
>>
>>You may just as well have asked about how to cook oysters. Oysters
>>contain pearls. "Pearl" sounds like "Perl". So questions about oyster
>>cooking are on-topic, surely?
>
>about the oysters though...
Dear Perl gurus: HELP! I keep getting an error that says "You're lunch,
sucker - empty shell invocation." What can I do? It's URGENT!
#!/usr/bin/perl -w
use strict;
use Shellfish::Parse qw( search );
$|++;
search ( \&shuck, shift );
for my $n ( 1..++$#total ) { print $n--, ".\t", $total[$n], "\n"; }
sub shuck {
foreach ( @oysterpile ) {
if ( oyster_mature ) {
pry_open or die "You're lunch, sucker - $!\n";
@found = vgrep /pearl/i, @oyster;
push @total, @found;
}
}
}
<grin> HTH, HAND.
Ben Okopnik
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
That which does not kill me is surely defective and should be returned to
the manufacturer for replacement. -- Anu Kapoor
------------------------------
Date: 2 Mar 2001 19:29:14 GMT
From: ilya@math.ohio-state.edu (Ilya Zakharevich)
Subject: Re: Opening STDERR for input
Message-Id: <97osaa$ie9$1@charm.magnus.acs.ohio-state.edu>
[A complimentary Cc of this posting was sent to Bernard Cosell
<bernie@fantasyfarm.com>],
who wrote in article <j4bv9t4g736m74qs4890f7k9gqeor4c282@4ax.com>:
> } > It is not passing data around inside the program -- it is a relatively
> } > standard Unix hack [that I've used before, just never before from
> } > Perl] for getting user input when you have a program that is running
> } > as a proper filter. you can't print out prompts and read responses
> } > using stdin/stdout else you'll mess up the pipeline, so it was always
> } > SOP to use stderr.
> }
> } This is what Term::ReadLine is for. At least you can use it (or just
> } the ::Stub part) to get the i/o handles to the TTY.
>
> Probably true, but that really feels like overkill. It was always
> traditional in Unix that STDERR/fd2 would stay pointed at the user's
> tty even as stdin and stdout were piped around from here to there.
I thought that we were discussing Perl, not Unix. Given that there is
not such thing as "THE Unix", it is even more pronounced.
If you look into Term/ReadLine.pm, you will see that the logic is not
*that* straightforward as you expect.
Ilya
------------------------------
Date: Fri, 2 Mar 2001 14:04:14 -0500
From: "Simon" <simon@nospam.simonwebdesign.com>
Subject: Re: perl CGI output not shown in browser
Message-Id: <t9vrncsivv97e1@corp.supernews.co.uk>
You have to have the following line before Perl can output to a browser.
print "Content-type: text/html\n\n";
Hope this helps
Simon
http://simonwebdesign.com
"Ivica Letunic" <Ivica.Letunic@EMBL-Heidelberg.de> wrote in message
news:uv8u25cik1e.fsf@nora.EMBL-Heidelberg.DE...
>
> I have a perl script that uses a simple queue system. If the queue is not
> empty, it enters a loop and waits for other jobs to finish, before
> continuing. Here is the relevant part of the script:
>
> $| = 1;
> print STDOUT "Your request has been queued (no. $num in the queue)\n";
> #loop until queue is free
> my $old_number=0;
> while ($my_number = $queue->busy())
> {
> if ($my_number < 0)
> {
> $www->error('queue_release','exit') if(not $queue->release());
> $www->error('check_queue','exit');
> }
> print STDOUT ". $my_number ." if ($old_number != $my_number);
> $old_number=$my_number;
> sleep 5;
> } else { #continue the script...
>
> My problem is that browsers do not show any output (or sometimes just the
> part that gets generated before the loop is shown) while the script is in
> the loop. So the 'print STDOUT ". $my_number...' is shown AFTER script
gets
> out of the loop.
>
> How do I make browsers print all output as soon as it is generated? I
> thought $| = 1 should be enough, but it isn't.
>
> Thank you for any suggestions.
>
> --
> Ivica Letunic <Ivica.Letunic@EMBL-Heidelberg.de>
> Biocomputing, EMBL
> http://www.embl-heidelberg.de/~letunic
------------------------------
Date: Fri, 2 Mar 2001 14:25:21 -0600 (CST)
From: dennis100@webtv.net (BUCK NAKED1)
Subject: Re: Perl CGI.pm RESET problem
Message-Id: <169-3AA001B1-13@storefull-241.iap.bryant.webtv.net>
Well, I got Godzilla's script to work without much problem (I like that
script, btw), but Joe, I never could get yours to work... came up with
two "1's" for output. That's OK, you've helped enough, and I've spent
waaay too much time on this already. Looks like I'm forced to use a
Javascript event handler. I guess I'm strange, but I'm not fond of JS,
and really hate mixing JS and Perl. I'm a bit surprised that Stein has
so much JS info in cgi.pm docs. Thanks again for everyone's help. I
sincerely appreciate it.
--Dennis
------------------------------
Date: Fri, 02 Mar 2001 21:54:24 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Perl, Cookies, and Apache.
Message-Id: <3AA017E9.91F0C9A6@acm.org>
Parrot wrote:
>
> Bart Lateur <bart.lateur@skynet.be> wrote in message
> news:peru9t09plgcefuts70esb11st8glb9b90@4ax.com...
> >
> > Allow me to disagree. It's only still readable if you're reading a whole
> > thread in one go. If it's been days since you've read the previous
> > message, you'll have to read the quoted part first, anyway, and then it
> > becomes annoying (spaghetti reading).
> >
>
> You don't need my permission to disagree - it's a free world :)
>
> However, I still disagree with the original statement. I've been messaging
> for years, and I've never had a problem reading 'jeopardy-style', nor have
> any of my friends online or on BBS's ever complained about decreased
> readability of posts depending on the quoting arrangements.
>
> Newsgroups are the only place I've come across where this has been an issue.
> I've been told that in the early days there were much fewer users on the
> newsgroups and that conditions were much stricter. I guess people got used
> to things in a certain way and have trouble adjusting when something
> different happens.
I'll be another one to disagree then. I've been posting for years on
programming forums in Compuserve and on Fidonet and the norm has always
been to post after the originally quoted text. This seems to only have
become an issue because certain MS software defaults to jeopardy style.
John
------------------------------
Date: Fri, 02 Mar 2001 22:03:07 +0000
From: jb <jb@yperite.demon.co.uk>
Subject: Re: Perl, Cookies, and Apache.
Message-Id: <3AA0189B.22B59C01@yperite.demon.co.uk>
> <nobull@mail.com> wrote in message news:u9n1b5o034.fsf@wcl-l.bham.ac.uk...
> > "Parrot" <parrot0123@yahoo.ca> writes jeopary-style. I do not know if
> > this is due to ignorance, lazyness, stupidity or a positive desire to
> > cause offence. Perhaps he'd like to enlighten us.
> >
Parrot wrote:
>
> As for your other comment here about me posting jeopardy-style : why the
> heck does the way I quote offend you? I find that top-posting is better in
> many cases, and I like to use it. What possible problem is there with that?
>
http://www.usenet.org.uk/ukpost.html
"Configuring your news reader to post to uk.*"
by Alex D. Baxter
Amongst other things, it covers why you shouldn't "top post" and also
why you shouldn't post in HTML. Although its title refers to uk.*, it is
equally applicable to all newsgroups.
"top posting" sucks!
------------------------------
Date: Fri, 02 Mar 2001 22:04:40 +0000
From: jb <jb@yperite.demon.co.uk>
Subject: Re: Perl, Cookies, and Apache.
Message-Id: <3AA018F8.C3711904@yperite.demon.co.uk>
> message boards. Frankly I find the idea that somebody can get royally pissed
> over the way you quote a message to be absurd.
It's not absurd. If you've read usenet for any time at all you'll learn
why.
> Frankly, people flaming me about it doesn't give me much incentive to
> conform - however, I realize that not everybody in this group is like that,
> so if they all find posts easier to read that way, then I'll do it.
No matter. You'll just be killfiled.
------------------------------
Date: Fri, 02 Mar 2001 22:09:12 +0000
From: jb <jb@yperite.demon.co.uk>
Subject: Re: Perl, Cookies, and Apache.
Message-Id: <3AA01A08.DBD58AF@yperite.demon.co.uk>
> Newsgroups are the only place I've come across where this has been an issue.
> I've been told that in the early days there were much fewer users on the
> newsgroups and that conditions were much stricter. I guess people got used
> to things in a certain way and have trouble adjusting when something
> different happens.
No need to adjust. Things weren't more strict then, people just knew how
to post in general. it is not difficult to understand that being able to
read news properly with nothing more than the spacebar (depending on the
newsreader) with replies properly interspersed with the quoted text is
the right way. There is no other way.
Jeopardy posting is the result of misconfigured software ("email"
programs like notes are notorious for this too) and a lack of
understanding about how this stuff is supposed to work.
------------------------------
Date: 16 Sep 99 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 16 Sep 99)
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: The mail to news gateway, and thus the ability to submit articles
| through this service to the newsgroup, has been removed. I do not have
| time to individually vet each article to make sure that someone isn't
| abusing the service, and I no longer have any desire to waste my time
| dealing with the campus admins when some fool complains to them about an
| article that has come through the gateway instead of complaining
| to the source.
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 400
**************************************
