[18176] in Perl-Users-Digest
Perl-Users Digest, Issue: 344 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 23 14:10:43 2001
Date: Fri, 23 Feb 2001 11:10:17 -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: <982955417-v10-i344@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Fri, 23 Feb 2001 Volume: 10 Number: 344
Today's topics:
Re: Perl in UNIX <khleung@cse.cuhk.edu.hk>
Re: Perl in UNIX <iltzu@sci.invalid>
Re: Perl in UNIX <mischief@velma.motion.net>
Re: Perl in UNIX nobull@mail.com
Re: Reading from __DATA__ <ianb@ot.com.au>
Re: Reading from __DATA__ <bart.lateur@skynet.be>
Re: Reading from __DATA__ (Tramm Hudson)
RFC: overloading. A mess? <dev@trahojen.REMOVETHIS.com>
Re: RFC: overloading. A mess? <iltzu@sci.invalid>
Re: RFC: overloading. A mess? <ddunham@redwood.taos.com>
Re: RFC: overloading. A mess? nobull@mail.com
RFD - comp.lang.perl.db, comp.lang.perl.network, comp.l <djberge@uswest.com>
server question <terry_s@northstate.net>
Re: Specifying the length of regular expression <ianb@ot.com.au>
Subroutine Name <sorinvc@utdallas.edu>
Re: Subroutine Name <tony_curtis32@yahoo.com>
Re: why do i get an unitialized value warning when read (teknokrat)
Re: why do i get an unitialized value warning when read nobull@mail.com
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 23 Feb 2001 14:29:42 GMT
From: Ivan Leung <khleung@cse.cuhk.edu.hk>
Subject: Re: Perl in UNIX
Message-Id: <975s4m$ia4$1@eng-ser1.erg.cuhk.edu.hk>
Ivan Leung <khleung@cse.cuhk.edu.hk> wrote:
> I want to ask can I set the permission of a perl script to be executed
> by others but not read by others?
I just thought about a method to do that.
1. change the perl script to a special and hard to guess file name.
"chmod 755" to the script.
2. write a C program. In this program, it will run the perl script.
3. "chmod 755" to the binary of the C program
Then others can run the binary of C instead of perl script.
Will it work?
--
Cheers,
Ivan
------------------------------
Date: 23 Feb 2001 16:54:06 GMT
From: Ilmari Karonen <iltzu@sci.invalid>
Subject: Re: Perl in UNIX
Message-Id: <982944901.256@itz.pp.sci.fi>
In article <975s4m$ia4$1@eng-ser1.erg.cuhk.edu.hk>, Ivan Leung wrote:
>Ivan Leung <khleung@cse.cuhk.edu.hk> wrote:
>
>> I want to ask can I set the permission of a perl script to be executed
>> by others but not read by others?
>
>1. change the perl script to a special and hard to guess file name.
> "chmod 755" to the script.
>2. write a C program. In this program, it will run the perl script.
>3. "chmod 755" to the binary of the C program
>
>Then others can run the binary of C instead of perl script.
>Will it work?
Not for any values of "work" I'd consider relevant, but that's only
because I consider your step 1 worthless as a security measure.
What you could do, however, is to include the Perl code as a string
*in* the C program, and hand it to perl as a long -e option. Then
chmod the program to 711.
--
Ilmari Karonen - http://www.sci.fi/~iltzu/
"Looks more like it's trying to issue an SNMP query asking the contents
of your left rear pocket." -- Greg Andrews in the monastery
Please ignore Godzilla and its pseudonyms - do not feed the troll.
------------------------------
Date: Fri, 23 Feb 2001 17:03:27 -0000
From: Chris Stith <mischief@velma.motion.net>
Subject: Re: Perl in UNIX
Message-Id: <t9d5uv3q1cm04@corp.supernews.com>
Ivan Leung <khleung@cse.cuhk.edu.hk> wrote:
> Ivan Leung <khleung@cse.cuhk.edu.hk> wrote:
>> I want to ask can I set the permission of a perl script to be executed
>> by others but not read by others?
> I just thought about a method to do that.
> 1. change the perl script to a special and hard to guess file name.
> "chmod 755" to the script.
> 2. write a C program. In this program, it will run the perl script.
> 3. "chmod 755" to the binary of the C program
> Then others can run the binary of C instead of perl script.
> Will it work?
Somewhat. The binary will still be readable. It would be better by far
if security is the concern in the first place to change the binary to
mode 711. You still would have security through obscurity, though. For
one thing, if the perl program's source is 755, they can see the file
names in a directory listing. That's an extremely weak point of your
solution.
Perhaps you could make a C program to change the mode of the file,
call perl to run it, then change the mode back as soon as perl is
running it. I causes a very short period when the file is readable,
but it shouldn't be that bad.
Chris
--
Christopher E. Stith
Disclaimer: Actual product may not resemble picture in ad in any way.
------------------------------
Date: 23 Feb 2001 17:52:02 +0000
From: nobull@mail.com
Subject: Re: Perl in UNIX
Message-Id: <u9elwpuw1p.fsf@wcl-l.bham.ac.uk>
"Godzilla!" <godzilla@stomp.stomp.tokyo> writes:
> You really should work at becoming more aware of your unconscious
> usage of personal idioms in language.
ROTFL!
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Sat, 24 Feb 2001 03:00:07 +1100
From: Ian Boreham <ianb@ot.com.au>
Subject: Re: Reading from __DATA__
Message-Id: <3A968907.2E09B79A@ot.com.au>
Abigail wrote:
> After the seek, do:
>
> 1 until <> eq "__DATA__\n";
Assuming, of course, that there are no lines that look like this before the
real DATA section, e.g.
...
print "This file reads the DATA section multiple times, by searching for:
__DATA__
in the file after doing a seek.
"
...
Regards,
Ian
------------------------------
Date: Fri, 23 Feb 2001 16:11:39 GMT
From: Bart Lateur <bart.lateur@skynet.be>
Subject: Re: Reading from __DATA__
Message-Id: <8u2d9to2c8h821i1e7peimod2cjfffh3pf@4ax.com>
Dmitry Epstein wrote:
>> After the seek, do:
>>
>> 1 until <> eq "__DATA__\n";
>>
>> Abigail
>
>OK, I am not a Perl expert, so let me ask a stupid question: doesn't <>
>read from STDOUT or a file from the parameter list? You obviously meant
>it to read from the source file.
Not STDOUT, STDIN. But you're right. The code should have read
seek DATA, 0, 0;
1 until <DATA> eq "__DATA__\n";
--
Bart.
------------------------------
Date: 23 Feb 2001 15:51:06 GMT
From: hudson@swcp.com (Tramm Hudson)
Subject: Re: Reading from __DATA__
Message-Id: <9760ta$96r$1@sloth.swcp.com>
[ Posted and cc'd to cited author ]
Abigail <abigail@foad.org> wrote:
[] Dmitry Epstein (mitiaNOSPAM@northwestern.edu.invalid) wrote on MMDCCXXXII
[] ][ How can I read read the entire __DATA__ block several times? Opening
[] ][ and closing DATA filehandle doesn't do the job. I tried seek:
[] ][
[] ][ seek(DATA, 0, 0)
[] ][
[] ][ but that rewinds to the top of the module, that is next time I read from
[] ][ DATA it starts reading from the first line of the file, rather than from
[] ][ the first line after __DATA__
[]
[] After the seek, do:
[]
[] 1 until <> eq "__DATA__\n";
I like the tell(3) and seek(3) solution -- it appears to be more robust.
Here are a few things that could cause your loop to fail by starting the
read in the wrong location.
=head1
__DATA__
=cut
my $data = "
__DATA__
";
s/
__DATA__
/
__DATA__
/x;
undef $/; # Oops
Remember -- only perl can parse Perl.
Tramm
--
o hudson@swcp.com hudson@turbolabs.com O___|
/|\ http://www.swcp.com/~hudson/ H 505.323.38.81 /\ \_
<< KC5RNF @ N5YYF.NM.AMPR.ORG W 505.986.60.75 \ \/\_\
0 U \_ |
------------------------------
Date: Fri, 23 Feb 2001 15:43:37 +0100
From: "Trahojen" <dev@trahojen.REMOVETHIS.com>
Subject: RFC: overloading. A mess?
Message-Id: <0Hul6.3845$hi2.11126@nntpserver.swip.net>
Hello all,
This is a question of almost pure curiosity, whilst trying to learn a few
obscure things...
I've read through the documentation of the overload pragma, and according to
the authors themselves "this document is confusing. There are grammos and
misleading language used in places. It would seem a total rewrite is
needed."
It's giving me head-aches.
I'm trying to
$set = new statement('like this');
$set = 'or after construction like this';
$set = 'now this';
and want to print 'now this' upon execution of
print $set;
I tried use overload '=' => \&get
It would seem to me as if the code never enters my overloaded function that
is set as:
sub get
{
my $self = shift;
return $message; # as declared locally, earlier in package statement
}
because when I call print $set; I get the scalar ref, as expected. $$set is
the package name "statement".
I'm not asking for a whole code snippet to solve my problem, I'm just asking
for a few pointers from those who are familiar with overloading and object
references in general. Is this impossible, what I'm asking?
Background:
I want to track down every time $set is read (like in print $set). I'd like
to achieve this by providing a print STDOUT "set is $value" in the
overloaded read procedure before passing it's value back to execution point.
By tracing $set's value at all times, I may be able to understand why things
tend to crash sometimes. It's for debugging only.
Any comments or suggestions are welcome.
- Samuel [dev@trahojen.REMOVETHIS.com]
------------------------------
Date: 23 Feb 2001 17:47:15 GMT
From: Ilmari Karonen <iltzu@sci.invalid>
Subject: Re: RFC: overloading. A mess?
Message-Id: <982947965.5389@itz.pp.sci.fi>
In article <0Hul6.3845$hi2.11126@nntpserver.swip.net>, Trahojen wrote:
>Background:
>I want to track down every time $set is read (like in print $set). I'd like
>to achieve this by providing a print STDOUT "set is $value" in the
>overloaded read procedure before passing it's value back to execution point.
>By tracing $set's value at all times, I may be able to understand why things
>tend to crash sometimes. It's for debugging only.
You don't want to use overload for that. You want to tie the scalar:
package Tracker;
use strict;
use Carp qw/carp/;
sub escape {
my $val = shift;
return "undef" unless defined $val;
return "$val" if ref $val;
$val =~ s/([\\\$\@\"])/\\$1/g;
$val =~ s/([\0-\x1f\x7f-\x9f])/sprintf "\\x%02x", ord $1/eg;
return qq("$val");
}
sub TIESCALAR {
my $pkg = shift;
my $name = @_ ? shift : "variable";
carp "Created $pkg scalar '$name'";
bless [$name, undef], $pkg;
}
sub FETCH {
carp "Fetched $_[0][0] = " . escape($_[0][1]);
return $_[0][1];
}
sub STORE {
carp "Stored $_[0][0] = " . escape($_[1]);
$_[0][1] = $_[1];
}
sub DESTROY {
carp "Destroying $_[0][0] = " . escape($_[0][1]);
}
Use it like this:
use Tracker;
tie my $foo, 'Tracker', '$foo';
--
Ilmari Karonen - http://www.sci.fi/~iltzu/
"OTOH, 'put to sleep' implies painless, and I can undertand als wanting
to avoid that." -- Ben Aveling in the monastery
Please ignore Godzilla and its pseudonyms - do not feed the troll.
------------------------------
Date: Fri, 23 Feb 2001 18:11:54 GMT
From: Darren Dunham <ddunham@redwood.taos.com>
Subject: Re: RFC: overloading. A mess?
Message-Id: <KJxl6.22$yz2.27577@news.pacbell.net>
Trahojen <dev@trahojen.removethis.com> wrote:
> Background:
> I want to track down every time $set is read (like in print $set). I'd like
> to achieve this by providing a print STDOUT "set is $value" in the
> overloaded read procedure before passing it's value back to execution point.
> By tracing $set's value at all times, I may be able to understand why things
> tend to crash sometimes. It's for debugging only.
I think you'll want to look at tie() rather than overload.
It's a whole chapter in Camel III, and it shows ways to use tie that
would be similar to what you mention above.
Overload lets you use operators for your brand new object methods. It's
not for changing what they do for normal scalars.
--
Darren Dunham ddunham@taos.com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< Please move on, ...nothing to see here, please disperse >
------------------------------
Date: 23 Feb 2001 18:21:17 +0000
From: nobull@mail.com
Subject: Re: RFC: overloading. A mess?
Message-Id: <u9wvah1crm.fsf@wcl-l.bham.ac.uk>
"Trahojen" <dev@trahojen.REMOVETHIS.com> writes:
> This is a question of almost pure curiosity, whilst trying to learn a few
> obscure things...
>
> I've read through the documentation of the overload pragma, and according to
> the authors themselves "this document is confusing. There are grammos and
> misleading language used in places. It would seem a total rewrite is
> needed."
Nontheless a lot of what it says is right.
> It's giving me head-aches.
>
> I'm trying to
>
> $set = new statement('like this');
> $set = 'or after construction like this';
> $set = 'now this';
>
> and want to print 'now this' upon execution of
>
> print $set;
This will happen.
You cannot overload the assignment operator in Perl so after the
second and third assignments $set is just a plain string.
> I tried use overload '=' => \&get
See perldoc overload/"Copy Constructor"
> Background:
> I want to track down every time $set is read (like in print $set). I'd like
> to achieve this by providing a print STDOUT "set is $value" in the
> overloaded read procedure before passing it's value back to
> execution point.
You are looking at the wrong concept. You want to be using tie not
overload.
> By tracing $set's value at all times, I may be able to understand why things
> tend to crash sometimes. It's for debugging only.
>
> Any comments or suggestions are welcome.
perl -MCPAN -e'install Tie::Watch'
perldoc Tie::Watch
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Fri, 23 Feb 2001 08:12:34 -0600
From: Daniel Berger <djberge@uswest.com>
Subject: RFD - comp.lang.perl.db, comp.lang.perl.network, comp.lang.perl.regex
Message-Id: <3A966FD2.14C4FBD@uswest.com>
Hi all,
news.groups postings suggested that I should canvas relevant newsgroups
to see if there was interest for some new newsgroups. Hopefully I am
not flogging a dead horse here, but I haven't seen this mentioned
before.
After reading comp.lang.perl.misc for a while now, I have noticed a
distinct
pattern of the types of questions that appear in this newsgroup with the
majority
falling into these four categories:
1)questions about database interfaces and database drivers (the DBI/DBD
modules,
DBM files, etc). I realize that there is a mailing list for this, but I
*much* prefer
a newsgroup to a mailing list. I suspect others do also (but could be
wrong).
2)questions about regular expressions.
3) questions regarding networking, including sockets in general,
client/server processes,
email, SMTP, NNTP, POP, usenet, ftp, the LWP module, and HTTP in general
4) everything else
Consequently, I wanted to see if there was *any* interest in separating
these topics
because they are so common in this newsgroup. The names I have chosen
in
the subject line are certainly open to discussion as well.
Here's a general rundown of what would be "on topic" for each group.
comp.lang.perl.db
Discussion of perl as it relates to interfacing with databases of any
sort. This would include
the DBI module and any DBD module, including installation (and any
problems
therein) and use of those modules. Discussion of DBM hashes would also
be on topic as
well as development of any new modules as they relate to databases (DDL
modules,
for example).
comp.lang.perl.regex
Regular expressions - period. Generally, "How do I match ..." and
"Here's how to match ..."
would be the subject line of mose messages. I imagine obfuscated regex
competitions would grow
out of this as well.
comp.lang.perl.network
CGI, LWP, and networking in general including, of course, sockets and
the IO::Socket module,
and any of the Net:: modules. This is the broadest of the three, and I
considered a narrower
newsgroup like comp.lang.perl.web strictly for CGI, Apache, etc, but
figured that there would
be too much overlap.
I would definitely like to hear people's (hopefully constructive)
opinions on this. Thanks
for your time.
Sincerely,
Daniel Berger
------------------------------
Date: Fri, 23 Feb 2001 13:26:16 -0500
From: "Terry" <terry_s@northstate.net>
Subject: server question
Message-Id: <13yl6.8353$pu5.130385@e420r-sjo2.usenetserver.com>
Hello Guys
I operate a web hosting service. I have been asked by a customer to install
perl on my server. I have downloaded perl 5.6, suposedly the latest version.
OK now what do I do with it. I am not a coder nor do I have time to become
one right now. But I do want my customers to be able to run perl CGI's on my
server. Any advice would be appreciated. My server is running Win 2000
professional,
with Omni httpd professional web server.
Thanks in advance
Terry
------------------------------
Date: Sat, 24 Feb 2001 01:28:00 +1100
From: Ian Boreham <ianb@ot.com.au>
Subject: Re: Specifying the length of regular expression
Message-Id: <3A96736F.1464617E@ot.com.au>
Greg Bacon wrote:
> In article <3A93ABD6.90E1851@ot.com.au>,
> : However, the right question was similar, and it was still
> : heavily biased towards a regex solution, since it had to be used in "split".
> : Yes, other solutions are possible, but in this case probably not better.
>
> If I said "Hey, I have to use split to tokenize HTML" or "Hey, I need to
> drive these 16d nails, but all I have is this stubby screwdriver",
> what's the best advice? Would you suggest that I leave my tool's design
> limits or that I use a more appropriate tool that will make my life
> easier in the long run?
In fact, the question omitted any mention of split. That the original poster wanted
to use the pattern in split only came out later. After looking at the real problem,
it
looks to me like a regex (split or m//g) solution is still probably the best under
the
circumstances.
> : > I would argue the a module like the one you've described is
> : > unnecessarily limited.
> :
> : As are about 99% of third-party products you'll ever be required to use.
>
> I like to use my head in manners other than as a brute force implement.
> If a tool is too limited for my intended use, then I either accept the
> limitation or find (or write!) a better tool.
Well, that's what I've been saying, only I was trying to make sure people didn't
forget the first choice in the rush.
The proportion of good (i.e. near-perfect) tools out there is very low. And I
certainly
don't have time to write every tool I need from scratch, no matter how much I'd
like
to or have tried in the past.
And I don't like the way this argument is heading towards making me defend
the idea that everyone should live with the imperfections in the tools they use,
because
I am personally prone to going too far the other way. I am simply maintaining that
sometimes you have to live with and work around imperfections in tools, whether
they
are your own or someone else's. You just have to decide when that's the case. And
if you have a mental toolkit that contains, among other things, a comprehensive
knowledge of regex techniques, workarounds in Perl come a heck of a lot easier.
> : I can just imagine you telling your boss "Well, I could just use the
> : interface as is, and spend a few minutes coming up with a regex [...]
>
> Your argument falls apart right there.
Actually, I think we'd rather moved on from the original question by this stage.
> The language in question, that
> might appear in a textbook on formal languages pattern, takes only a
> trivial amount of extra thought and modification.
Without Perl's lookahead, it wouldn't be so trivial, as EtB's version showed. I
doubt
it would be used in many books as a simple example. And I didn't see a whole lot of
people showing trivial modifications to make it work. There was a strong chorus
of "don't do it that way", which, incidentally, I agreed with in my post, but I was
simply showing the alternative for cases where it was not a simple matter to
rewrite the code.
> If there are only
> a couple of warts like this in the patterns that you want to match,
> then there's no reason to cook up a more flexible interface.
So you agree with me? Good.
> What
> happens when you have a lot of patterns that begin to require more and
> more effort? What if you want to match strings such that there is no
> Perl regular expression for them?
In that case you need an alternative solution, obviously. Apparently, I also agree
with you.
That's when you need to move to a different tool or write your own to replace it,
or rewrite
your own limited tool to do what you want, possibly wearing the consequences of
breaking
backwards compatibility, reducing reliability or whatever. The tool has to satisfy
the
requirements.
It's amazing how these sorts of "discussions" can start from what is a pretty
cautious
statement that later becomes represented as an extreme view.
Regards,
Ian
------------------------------
Date: Fri, 23 Feb 2001 11:06:32 -0600
From: Sorin Voicu-Comendant <sorinvc@utdallas.edu>
Subject: Subroutine Name
Message-Id: <Pine.GSO.4.21.0102231059450.28111-100000@apache.utdallas.edu>
Hi, all,
Under the ISO/IEC 9899:1999 C standard (C99) there is a way to get the
name of a function from within the function using _func_. Is there a
similar feature in Perl or a way to accomplish this?
Thank you,
Sorin.
***SOLI DEO GLORIA***
------------------------------
Date: 23 Feb 2001 11:36:56 -0600
From: Tony Curtis <tony_curtis32@yahoo.com>
Subject: Re: Subroutine Name
Message-Id: <874rxljo7b.fsf@limey.hpcc.uh.edu>
>> On Fri, 23 Feb 2001 11:06:32 -0600,
>> Sorin Voicu-Comendant <sorinvc@utdallas.edu> said:
> Hi, all, Under the ISO/IEC 9899:1999 C standard (C99)
> there is a way to get the name of a function from within
> the function using _func_. Is there a similar feature in
> Perl or a way to accomplish this?
I think yu're looking for caller,
perldoc -f caller
> ***SOLI DEO GLORIA***
Gloria is solid? :-)
--
The avalanche has already started.
It is too late for the pebbles to vote.
------------------------------
Date: Fri, 23 Feb 2001 17:25:44 GMT
From: teknokrat@mindless.com (teknokrat)
Subject: Re: why do i get an unitialized value warning when reading from a file?
Message-Id: <3a969c55.17361703@news.clara.net>
the code is a straightforward
while ( my $line=<FILE>) {
do something with $file
}
and i get errors warnings like
Use of uninitialized value at dbentry2.pl line 90, <CSV> chunk 12.
i am not chomping anything because for some reason when i chomp i
don't getthing in $line??
I was hoping someone here could shed some light on this.
thanks
On 22 Feb 2001 11:48:14 GMT, anno4000@lublin.zrz.tu-berlin.de (Anno
Siegel) wrote:
>According to David Efflandt <efflandt@xnet.com>:
>> On Wed, 21 Feb 2001, Igor Aptekar <igor_aptekar@programmer.net> wrote:
>> >I get this error in quite a few chunks eventhough i use chomp. Can someone
>> >explain what it mean and how to prevent it.
>>
>> I image that you chomp a blank line, ending up with nothing, and then
>> attempt to use nothing for something without testing it.
>
>chomp() won't undefine a defined string. Think about it.
>
>To the OP: Neither will chomp() define an undefined string. The
>"even though i use chomp" bit makes no sense.
>
>Anno
------------------------------
Date: 23 Feb 2001 18:06:44 +0000
From: nobull@mail.com
Subject: Re: why do i get an unitialized value warning when reading from a file?
Message-Id: <u9zofd1dfv.fsf@wcl-l.bham.ac.uk>
teknokrat@mindless.com (teknokrat) writes upside down:
> the code is a straightforward
> while ( my $line=<FILE>) {
> do something with $file
> }
Post _real_ code. Pseudo code written by someone who doesn't
understand what's going on just wastes our time.
Quote relevant parts on the message you are responing to _before_ your
responses.
If you can't act politely then perhaps you should leave.
> and i get errors warnings like
>
> Use of uninitialized value at dbentry2.pl line 90, <CSV> chunk 12.
There's nothing in you pseudo-code that defines $file. We cannot
begin guess what is wrong with you real code.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
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 344
**************************************
