[18137] in Perl-Users-Digest
Perl-Users Digest, Issue: 305 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat Feb 17 03:05:31 2001
Date: Sat, 17 Feb 2001 00:05:09 -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: <982397109-v10-i305@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Sat, 17 Feb 2001 Volume: 10 Number: 305
Today's topics:
Re: Back Reference Problem I Think (Keith Calvert Ivey)
Re: Big Numerical Computations in Perl ve C++/Fortran (Ilya Zakharevich)
Re: Big Numerical Computations in Perl ve C++/Fortran (Abigail)
Re: Big Numerical Computations in Perl ve C++/Fortran <david@habanero.chem.usu.edu>
Re: Big Numerical Computations in Perl ve C++/Fortran <david@habanero.chem.usu.edu>
Drop-in replacement for XML::Parser ... comments? (Clinton A. Pierce)
Dynamically loading modules (Gwyn Judd)
Re: HTML generator <bwalton@rochester.rr.com>
PERL 5.005/Sybperl 2.13 question <labuss@magothy.com>
perl help (Another Way)
perl, SSI and IIS <jeff_fletcher@pacbell.net>
PerlScript documentation and reference ? (John Robson)
Re: Perlscript on Win2000 (how to run) <nowayandnohow@hotmail.com>
Re: regex experts (Charles DeRykus)
Review: Data Munging with Perl <david@kasey.umkc.edu>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 17 Feb 2001 02:30:32 GMT
From: kcivey@cpcug.org (Keith Calvert Ivey)
Subject: Re: Back Reference Problem I Think
Message-Id: <3a8edc0d.2686723@news.newsguy.com>
"Gabriel Richards" <grichards@endertechnology.com> wrote:
>Help very much appreciated.
I haven't bothered to analyze the whole program, but I've
pointed out a couple of problems.
[snip]
> my @threadlinks = ($threadcontent =~
>/href\=\"http\:\/\/srd\.yahoo\.com\/drst\/\d*\/\*(.*)[^<\/ul><p><\/ul>]/g);
I don't think that regex is what you want. Because of
greediness, that .* will eat up everything until the next
newline. And you're misunderstanding character classes: that
[^<\/ul><p><\/ul>] matches a character that is not '<', '/',
'u', 'l', '>', or 'p' (some of which are needlessly repeated).
In this case it will match the "\n" after .* gobbles up the rest
of the line. I'm not sure what you're trying to capture, but
you may want something like this:
my @threadlinks = ( $threadcontent =~
m{/href="http://srd\.yahoo\.com/drst/\d*/\*([^"]*)}g );
Note that I eliminated unnecessary backslashes to make things
less ugly. There's nothing special about =, ", or : in a regex,
and you don't have to use slashes as your regex delimiter.
Or maybe you want to add a ? after the .* and then follow it
with something more meaningful than the bogus character class.
[snip]
> $string =~ /\*(.*)">/;
> print "String: $string\n\n";
> $link = $1;
It's dangerous to use $1 if you're not sure your match
succeeded, because in the case of an unexpected failure you may
get the $1 from some previous unrelated match (the last one that
did succeed). That may or may not be related to your problem
here, but it will bite you eventually. You could do
($link) = $string =~ /\*(.*)">/;
or
$link = $string =~ /\*(.*)">/ ? $1 : '[no match]';
or
$string =~ /\*(.*)">/ or die 'Match failed';
$link = $1;
And again you may not want .* there. Maybe [^"]* or .*? would
be better.
--
Keith C. Ivey <kcivey@cpcug.org>
Washington, DC
------------------------------
Date: 17 Feb 2001 02:21:55 GMT
From: ilya@math.ohio-state.edu (Ilya Zakharevich)
Subject: Re: Big Numerical Computations in Perl ve C++/Fortran
Message-Id: <96kn83$l06$1@charm.magnus.acs.ohio-state.edu>
[A complimentary Cc of this posting was sent to david farrelly
<david@habanero.chem.usu.edu>],
who wrote in article <3A8DCC5D.16674EE5@habanero.chem.usu.edu>:
> task the FORTRAN version took 0.5 cpu seconds while the PERL version
> took 66
> seconds on a DEC alpha. I made no special attempts to optimize the PERL
> code and essentially just translated the FORTRAN into PERL. However,
> this is a
> huge difference in execution time. Is this normal?
I have seen different digits, typically in the 80..200 range. This
assumes that you translate a low-level C code to a low-level Perl
code.
Perl programs can fly - but only when they use high-level Perl
constructs. With low-level constructs the overhead of "opcode
dispatch" becomes enormous.
Ilya
------------------------------
Date: 17 Feb 2001 02:30:16 GMT
From: abigail@foad.org (Abigail)
Subject: Re: Big Numerical Computations in Perl ve C++/Fortran
Message-Id: <slrn98roho.p3c.abigail@tsathoggua.rlyeh.net>
Ilya Zakharevich (ilya@math.ohio-state.edu) wrote on MMDCCXXVII September
MCMXCIII in <URL:news:96kn83$l06$1@charm.magnus.acs.ohio-state.edu>:
`` [A complimentary Cc of this posting was sent to david farrelly
`` <david@habanero.chem.usu.edu>],
`` who wrote in article <3A8DCC5D.16674EE5@habanero.chem.usu.edu>:
`` > task the FORTRAN version took 0.5 cpu seconds while the PERL version
`` > took 66
`` > seconds on a DEC alpha. I made no special attempts to optimize the PERL
`` > code and essentially just translated the FORTRAN into PERL. However,
`` > this is a
`` > huge difference in execution time. Is this normal?
``
`` I have seen different digits, typically in the 80..200 range. This
`` assumes that you translate a low-level C code to a low-level Perl
`` code.
80 < 66 / 0.5 == 132 < 200.
Abigail
--
sub camel (^#87=i@J&&&#]u'^^s]#'#={123{#}7890t[0.9]9@+*`"'***}A&&&}n2o}00}t324i;
h[{e **###{r{+P={**{e^^^#'#i@{r'^=^{l+{#}H***i[0.9]&@a5`"':&^;&^,*&^$43##@@####;
c}^^^&&&k}&&&}#=e*****[]}'r####'`=437*{#};::'1[0.9]2@43`"'*#==[[.{{],,,1278@#@);
print+((($llama=prototype'camel')=~y|+{#}$=^*&[0-9]i@:;`"',.| |d)&&$llama."\n");
------------------------------
Date: Fri, 16 Feb 2001 19:16:03 -0700
From: david farrelly <david@habanero.chem.usu.edu>
Subject: Re: Big Numerical Computations in Perl ve C++/Fortran
Message-Id: <3A8DDEE3.66E8669B@habanero.chem.usu.edu>
Martien,
Thanks. Therein hangs my dilemma. I originally wanted to manipulate code as
data using Perl and then automatically execute using C or Fortran (1000s of
times for 1000s of different bits of code in a genetic programming app.) Since
I couldn't figure out how to do that I decided to do it all in Perl. I read
that, according to one of the authors of Mastering Algorithms in Perl, an
optimized Perl code is usally no slower that a factor of "e" as compared to C
or Fortran. (That I could live with but a factor of 120 I can't.) It sounds
like a factor of e is not the case with computationally intensive code that
has lots of nested loops. For what I want to do, with Inline::C, I'd have to
pass in part of the code as generated by the Perl part, and also translated
into C. That is beyond me!
Again, I appreciate your response.
David
Martien Verbruggen wrote:
> On Fri, 16 Feb 2001 17:57:01 -0700,
> david farrelly <david@habanero.chem.usu.edu> wrote:
>
> > task the FORTRAN version took 0.5 cpu seconds while the PERL version
> > took 66
> > seconds on a DEC alpha. I made no special attempts to optimize the PERL
> > code and essentially just translated the FORTRAN into PERL. However,
> > integration. On an identical
>
> You have just discovered that Perl is slow. It is also a memory hog.
> perl is not the language to program CPU-intensive algorithms in. For
> that you fall back on C or, in your case, Fortran.
>
> > this is a
> > huge difference in execution time. Is this normal? I'm relatively new to
> > PERL --- I want to solve a problem in quantum physics which requires
> > combining some PERL-ish stuff with some C++/FORTRAN-ish stuff. It could
> > be that I have goofed somewhere. Does anyone have experience with doing
> > large floating point computations in PERL?
>
> Have a look at Inline::C. This will let you put C code in a Perl
> program, without having to worry about all the code that needs to be
> written to link the two.
>
> > I used the Math::Random module's random number generator but the results
> > don't change much if I use rand (58 sec vs 66).
>
> I suspect that the slowness isn't in the random number generation, but
> in the loops that you have in your code.
>
> If you have really tight loops that need to be executed many, many
> times, Perl is not the place to do it. At least, not if you need
> performance.
>
> Martien
> --
> Martien Verbruggen |
> Interactive Media Division | I'm just very selective about what I
> Commercial Dynamics Pty. Ltd. | accept as reality - Calvin
> NSW, Australia |
------------------------------
Date: Fri, 16 Feb 2001 19:03:09 -0700
From: david farrelly <david@habanero.chem.usu.edu>
Subject: Re: Big Numerical Computations in Perl ve C++/Fortran
Message-Id: <3A8DDBDD.E4432326@habanero.chem.usu.edu>
Eli. Thanks. Yes, "Perl"....been a long day!
Eli the Bearded wrote:
> In comp.lang.perl.misc, david farrelly <david@habanero.chem.usu.edu> wrote:
> > I recently programmed up a Numerical Recipes algorithm in PERL. The
> > subroutine is called VEGAS and it does multidimensional Monte Carlo
> > integration. On an identical task the FORTRAN version took 0.5 cpu
> > seconds while the PERL version took 66 seconds on a DEC alpha.
>
> Perl (not PERL) is not the best language for complex math problems.
> That said, we can't really tell if your code can be speeded up unless
> we see it. You might want to use the perl profiler to see where all
> the processing time is going.
>
> perldoc Devel::DProf
>
> Inline::C might help you, if you can easily get the math complex bits
> done by C functions.
>
> Elijah
> ------
> but you probably would want Inline::FORTRAN, if it existed
------------------------------
Date: Sat, 17 Feb 2001 02:12:34 GMT
From: clintp@geeksalad.org (Clinton A. Pierce)
Subject: Drop-in replacement for XML::Parser ... comments?
Message-Id: <m6lj6.321$0u5.367606@news1.rdc1.mi.home.com>
I have a project where I need to parse a machine-generated XML file.
The data's very regular: there's no CDATA, Unicode, namespaces, external
entities or anything else. Just basic markup. And it's always going to
be well-formed. But, it's a very, very large document.
XML::Parser turns out to be fairly expensive to get going, and what I
wanted (essentially) was the output from XML::Simple (which uses
XML::Parser).
I need this process to startup and shutdown in an awful hurry. So,
what I came up with is this program. It's a drop-in replacement for
XML::Simple::build_tree that doesn't require expat. The benchmark hooks
at the bottom tell this story:
* element-for-element it runs at almost the same speed as
XML::Parser, about 5% slower over many iterations over the
same document.
* The startup costs are about 15-20% less than XML::Parser
So what I'm discovering is that for extremely large documents, that need
to be parsed only once, this routine seems to be faster.
What I'm looking for are:
* Comments on doing this in the first place.
(When in doubt, the answer will be "Hubris")
* Comments on the code.
* Suggestions on cranking a little more speed from this.
You're free to use if you like it, but I'm just looking for feedback
at this point.
#!/usr/bin/perl -w
use strict;
use XML::Simple;
use Benchmark;
# From here up is just so that the harness at the bottom will run
#
use integer;
my $ent_name='[\w:][-\w\d.:]*'; # From XML1.0 spec. sec 2.3
sub start {
my($element,$stack)=@_;
$element=~s@(^\s+|/\s*$)@@;
my $seed={};
# Fix attributes, assume quote marks of some kind.
# foo bar='com' narf='poit' hlag="foo bar"
$element=~/(${ent_name})/; # Remove keyword
my $key=$1;
while ($element=~m/($ent_name)\s*=\s*(["'])(.*?)\2\s*/og ) {
$seed->{$1}=fix($3);
}
# does this structure leak?
my $str=[ $seed, 0, '' ];
push(@{ $stack->[-1] }, $key, $str );
push(@$stack, $str);
}
sub char {
my($text,$stack)=@_;
# Cook out leading/trailing whitespace.
# [this is for my own purposes -- cap]
$text=~s/(^\s+|\s+$)//g;
return unless $text;
$$stack[-1]->[2].=fix($text);
}
{
# Fix up the predefined entities
my %ent=( lt => '<', gt => '>', amp => '&',
apos => q{'}, quot => q{"});
sub fix {
my($data)=@_;
$data=~s/\&(\w+);/$ent{$1}/eg;
return $data;
}
}
sub parsedata {
my($orig)=@_;
my $data=['root', [ {}, 0, '' ]];
my @stack=( $data->[1] );
my $lasttagend=0;
while($orig=~m@<([^>]+)>@og) {
my($elem,$text)=$1;
# Pitch comments, element type declarations, prologs, doctype
if ($elem=~/^[?!]/) {
$lasttagend=(pos $orig) + 1;
next;
}
char( substr($orig, $lasttagend-1,
((pos $orig)-(length($elem)+1))-$lasttagend), \@stack);
if (substr($elem, -1, 1) eq '/') { # Empty entity
start($elem,\@stack);
pop(@stack);
} elsif (substr($elem, 0, 1) eq '/') { # End of entity
pop(@stack);
} else {
start($elem,\@stack); # Start of entity
}
$lasttagend=(pos $orig) + 1;
}
return $data;
}
# Mash this in the namespace in place of XML::Simple::build_tree
# This'll supply the right things to X::S::collapse
# by mimicing XML::Parser('Tree')
sub mpb_t {
my($self,$file,$xml)=@_;
parsedata($xml);
}
# From here down is just for testing,
# benchmarking, etc...
my $orig;
open(F, "sample.xml") || die;
{
local $/;
$orig=<F>;
}
close(F);
my $mysub=\&mpb_t;
my $oldsub=\&XML::Simple::build_tree;
my $dummy;
*XML::Simple::build_tree=$mysub; # Use the new one
#*XML::Simple::build_tree=$oldsub; # Use the original one
$dummy=XMLin($orig);
use Data::Dumper;
print Dumper $dummy; # Looks right?
__END__
timethese(10, {
orig => sub {
*XML::Simple::build_tree=$oldsub;
$dummy=XMLin($orig, noattr => 1);
},
mine => sub {
*XML::Simple::build_tree=$mysub;
$dummy=XMLin($orig, noattr => 1);
},
});
--
Clinton A. Pierce Teach Yourself Perl in 24 Hours *and*
clintp@geeksalad.org Perl Developer's Dictionary -- May 2001
"If you rush a Miracle Man, for details, see http://geeksalad.org
you get rotten Miracles." --Miracle Max, The Princess Bride
------------------------------
Date: Sat, 17 Feb 2001 07:15:13 GMT
From: tjla@guvfybir.qlaqaf.bet (Gwyn Judd)
Subject: Dynamically loading modules
Message-Id: <slrn98s97v.a1b.tjla@thislove.dyndns.org>
Bear with me a little on this one. Imagine if you will that you have a
need to load perl code from a particular directory. No problem, you just
use 'use' right? But the problem is that you don't know the names of
these modules at the time your script was written. In my case this is
because these modules are like 'plug-ins' to my script and I just want
to be able to drop a new one into the directory and have it be loaded
and run correctly. So you'd do something like:
while (<some_dir/*>)
{
eval 'require $_';
die $@ is $@;
($package) = m/^.*\/(.*)\.pm/;
print "Package name is $package\n";
But this is not enough because these plug-ins declare certain variables
and functions that you would like to access. You know the names of these
variables, but since you don't know the name of the package at compile
time how do you access them? Well this is what I came up with:
# access some variables
my $var1 = eval "\$$package" . "::var1";
die $@ if $@;
my $var2 = eval "\$$package" . "::var2";
die $@ if $@;
# call a function
my $result = eval $package . "::some_function";
die $@ if $@;
}
Anyway this all works but I was wondering if I'm missing something
obvious here. Is there a way to access package variables/functions if
you don't know the name of the package at compile time?
--
Gwyn Judd (print `echo 'tjla@guvfybir.qlaqaf.bet' | rot13`)
The average Ph.D thesis is nothing but the transference of bones from
one graveyard to another.
-- J. Frank Dobie, "A Texan in England"
------------------------------
Date: Sat, 17 Feb 2001 03:21:16 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re: HTML generator
Message-Id: <3A8DEEAF.8716C4C2@rochester.rr.com>
Martijn Mulder wrote:
>
> You are right, no need to re-invent the wheel but I am working with a
> Windows version of Perl 5.001 and all functionallity is stashed away in a
> huge .DLL
> file and none of the .PM files of Perl is available. Also no access to
> online documentation,
Really? Try your browser: http://www.perldoc.com/
Also, you could download and install the latest from ActiveState. If
you have a reason for keeping 5.001 (hard to imagine what :-), you could
continue to run it, but use the nice docs provided with the ActiveState
install.
> allthough I keep (and cherish) my Camel and BigHorn
> books. I am looking for a small, homegrown implementation in tiny Perl to
> write out elementary stuff in every .HTML file, more or less re-enginering
> the wheel ;-).
>
> > perldoc CGI
> > --
> > Bob Walton
------------------------------
Date: Fri, 16 Feb 2001 22:09:08 -0500
From: "Larry Buss" <labuss@magothy.com>
Subject: PERL 5.005/Sybperl 2.13 question
Message-Id: <96kq0q$mkv$1@bob.news.rcn.net>
Hi Folks
I recently updated our PERL/Sybperl configuration from
5.003/2.0x to 5.005/2.13. After doing so one of our
developers complained that this update broke one of his CGI
scripts. According to the Apache errorlog output there were
a couple shared libraries and other assorted environment
variables not being found (He calls a binary from his PERL
CGI that requires a couple share libraries and other env
variables). I placed the directive, PassEnv, in the Apache
conf file and called out LD_LIBRARY_PATH and the his other
env variables. This got his program running again.
Did anything change in PERL 5.005 or Sybperl 2.13 that would
effect the way the environment is passed to CGIs? The
version of Apache we are running hasn't changed. I would
have thought that CGIs would inherit their environment from
the parent server process. Did I screw up all this guys
work?
Is there a better, more preferred method, of passing ENV
variables to a CGI rather than placing them in the Apache
httpd.conf file?
Thanks in advance for your help.
-LB
------------------------------
Date: 17 Feb 2001 06:09:32 GMT
From: anotherway83@aol.com (Another Way)
Subject: perl help
Message-Id: <20010217010932.03857.00002906@ng-mi1.aol.com>
hey
this might be the wrong newsgroup, sorry for that.
perl is the first computer programming language i've learnt and i've written a
calculator with it, the thing is, i need people to test it. all u will need is
the perl interpreter on your computer, also, the program only does basic
numerical things like addition, subtraction, division, multiplication and
exponentiation. as far as i know, it has worked well with expressions like
(2^8 + 6.7898 - 6 / 7 /8* 5^2.62^ 2 - 7.8 + 9) and given the correct result.
the reason i need it tested is that this is my first major computer program of
any kind and i am going to use this "calculator" in a bigger program that does
derivatives of polynomials, then im gonna post it as a cgi thing on my website
if possible, so please help me out.
thanks
peace
------------------------------
Date: Fri, 16 Feb 2001 20:58:41 -0800
From: "Jeff Fletcher" <jeff_fletcher@pacbell.net>
Subject: perl, SSI and IIS
Message-Id: <Txnj6.94375$Wq1.38987469@nnrp5-w.sbc.net>
Does anyone know about a bug involving IIS that makes it add extra header
information to a script that comes via a a server-side include <!--#exec
cgi="..."-->
Sending the scripts with non-parsed headers gets rid of some of the header
info that's printing into the browser, but not all of it. Because my scripts
work perfectly when called directly from their URLs, I'm thinking the
problem has to do with the SSI.
Any ideas?
------------------------------
Date: 17 Feb 2001 03:56:20 GMT
From: as646@FreeNet.Carleton.CA (John Robson)
Subject: PerlScript documentation and reference ?
Message-Id: <96ksp4$9vj$1@freenet9.carleton.ca>
I'm looking for a comprehensive online reference and documentation
on PerlScript.
The documentation that comes downloaded with ActivePerl (activestate.com) is
very basic and incomplete.
Does anyone know of good books, online manuals, web sites on PerlScript ?
------------------------------
Date: Sat, 17 Feb 2001 05:32:08 GMT
From: "nowayandnohow" <nowayandnohow@hotmail.com>
Subject: Re: Perlscript on Win2000 (how to run)
Message-Id: <s1oj6.796$lx.761693@typhoon2.ba-dsg.net>
start -> program files -> accesoris -> command prompt
Is that what you mean ?
"Perly_Boy" <aurko@saudia.com> wrote in message
news:3A8DDB3C.3A0F9B4E@saudia.com...
> Hi Folks,
>
> I had a question :
>
> I was trying to run Perl script in the server ( w/ Win 2k server ins.. )
>
> machine; I know how to run Perl script from the command line in a MS DOS
>
> (using the DOS prompt); however, I couldn't find any way of getting the
> DOS prompt in the server ( w/ Win 2k installed)..
>
> My question is -
> Is there anyway I can bring up a command line in such M/cs (w/ Win 2k)
> so that I can run the script.. or there has to be an altogether
> different approach?
>
> I shall appreciate very much a feedback from you in this regard (if
> possible)
>
> Thanks
>
> Perly Boy
>
------------------------------
Date: Sat, 17 Feb 2001 04:29:25 GMT
From: ced@bcstec.ca.boeing.com (Charles DeRykus)
Subject: Re: regex experts
Message-Id: <G8vwH1.nn@news.boeing.com>
In article <G8vEDG.B2y@news.boeing.com>,
Charles DeRykus <ced@bcstec.ca.boeing.com> wrote:
>In article <96ing4$m0j$1@mamenchi.zrz.TU-Berlin.DE>,
>...
>Maybe the parsing of /$^/ is idiosyncratic then because it
>doesn't appear to match anything except STDOUT_TOP.
>You need at least a set of parentheses:
>...
I'm wrong ...
--
Charles DeRykus
------------------------------
Date: Fri, 16 Feb 2001 12:15:56 -0600
From: "David L. Nicol" <david@kasey.umkc.edu>
To: Kansas City Perl Mongers <kansas-city-pm-list@hfb.pm.org>
Subject: Review: Data Munging with Perl
Message-Id: <3A8D6E5C.E1298090@kasey.umkc.edu>
Dave Cross's new book, published by Manning, which means it has
a figure from an old guide to native dress of the peoples of the
world on the cover instead of some kind of animal, tells everything
you need to know about using Perl for what it is most suited for:
manipulating data.
Starting with the source/filter/sink theory of data manipulation
and demonstrating every tip and technique with clear and efficient
examples, without severe digressions into mythological whimsy,
this book would make an excellent second text on the Perl language,
or a suitable first for someone who is good with programming languages.
Many of the techniques contained in it are of "trade secret" quality;
they are the sort of write-the-number-of-gallons-of-paint-it-took-to-paint-
the-room-on-the-back-of-the-light-switch-cover practices that until now
had to be learned or happened upon by every programmer, alone, or by example,
rather than in the context of a coherent theory.
The theoretical side, in which "munging" is defined and most software
activity is described in terms of it, is clear enough that the book might be
an interesting read for management, to answer the question "Just what is it
about Perl that makes those who use it regularly so confoundedly fanatical?"
If you've ever been mystified by a Perl wizard who found it easier to export
the records from the fancy GUI database into a comma delimited text file
and then sort and display the data with mysterious little programs rather than
use the GUI's native report generator, and want to find out why, or if you
would like to become such a person yourself, or if you already are such a
person but would like to get better at it, this book is for you.
http://www.amazon.com/exec/obidos/ASIN/1930110006/tipjartransactioA/
This e-mail copyright 2001 David Nicol and licensed for general distribution,
please forward as appropriate, in whole or in part.
--
David Nicol 816.235.1187 dnicol@cstp.umkc.edu
"All of a sudden it hit me: tk was short for Thorndike-Kibre Index"
------------------------------
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 305
**************************************
