[29625] in Perl-Users-Digest
Perl-Users Digest, Issue: 869 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Sep 20 14:09:38 2007
Date: Thu, 20 Sep 2007 11:09:06 -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 Thu, 20 Sep 2007 Volume: 11 Number: 869
Today's topics:
Re: are you using Perl in your job? <cwilbur@chromatico.net>
Re: are you using Perl in your job? <cwilbur@chromatico.net>
Re: are you using Perl in your job? <tzz@lifelogs.com>
Re: List Variable becomes undefined inexplicably mattbreedlove@yahoo.com
Re: List Variable becomes undefined inexplicably <nobull67@gmail.com>
Re: List Variable becomes undefined inexplicably <dummy@example.com>
Re: List Variable becomes undefined inexplicably <jgibson@mail.arc.nasa.gov>
Re: List Variable becomes undefined inexplicably <kenslaterpa@hotmail.com>
Re: perl and unix command <josef.moellers@fujitsu-siemens.com>
Re: perl and unix command <lerameur@yahoo.com>
Re: perl and unix command <tzz@lifelogs.com>
Re: perl and unix command xhoster@gmail.com
Re: perl and unix command <spamtrap@dot-app.org>
Re: perl and unix command <dummy@example.com>
Re: Web interface to script? <glex_no-spam@qwest-spam-no.invalid>
Re: Writing a C++ Style Checker <tzz@lifelogs.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 20 Sep 2007 11:53:39 -0400
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: are you using Perl in your job?
Message-Id: <87bqbxtjss.fsf@mithril.chromatico.net>
>>>>> "bdf" == brian d foy <brian.d.foy@gmail.com> writes:
bdf> It's not hard to get a Perl job. It's just hard to get one
bdf> where you are probably. :)
What I've noticed is that jobs tend to fall into a few categories.
Startups founded by business-types who think they can contract out
development usually use something Microsofty, Java, or ColdFusion,
because that's what their highly-paid consultants told them to use.
Startups founded by technical types tend to use whatever language the
developers think gives them the most advantage in the problem domain.
This may not have any correlation with what is actually likely to give
them short- or long-term advantage, and usually is biased in favor of
languages and frameworks the developers already know.
Startups that have become profitable tend to stick with what's worked
for them, because the cost and risk of reimplementation is so high.
Startups that are failing tend to thrash around, and "rebuild the
whole thing from scratch in another technology" is a common move; if
it works, they become profitable, and if it doesn't, they continue
thrashing.
Older companies (and organizations such as universities) for whom
software development is a cost center rather than a primary reason for
existence tend towards whatever's been tested and proven, with a
healthy dose of glossy magazine lore, corporate FUD, and risk
avoidance ("nobody ever got fired for...."). You're likely to find
lots of Java and Microsoft in those companies; if there's any Perl or
open-source Unixlike technology going on at all, it's either because
the CIO doesn't know it's there or because the CIO trusts his
sysadmins even though they're using such a subversive anti-corporate
software stack.
Consultants tend to focus with one of Microsoft, Java/J2EE, or LAMP,
with diverse interpretations of 'L', 'M', and 'P' in that last
acronym. Consulting companies can either specialize in one of the
three or diversify.
So if you want a Perl job, you really have four basic approaches:
1 - Become a founding member of a startup where technical decisions
are made by technical people and not managers, or join such a startup.
2 - Work for a small profitable company that got that way using Perl.
3 - Consult.
4 - Work for a large organization that doesn't necessarily realize
it's using Perl.
Options 1 and 2 require networking; startups don't advertise, and
small companies don't advertise much. Location is also critical here.
Option 3 requires either marketing yourself or joining a reputable
consulting company. Smaller consulting companies have the same issues
as option 2; larger consulting companies have the same issues as option 4.
Option 4 is the most visible one you're likely to see on job sites,
but it's also the one that's likely to be the least satisfying. In
some cases, "Perl" gets thrown into a list of 20-odd languages and
technologies that they consider "nice to have"; other times, they
throw in "Perl" because they think they might want someone webbish
and,hey, Perl is webbish, even though everything else in the company
is Java or Cobol.
(I worked one job where "Perl" was prominently featured in the job
description, and was actually used quite a bit in the company, but the
actual job I was hired for involved PHP - my manager thought they were
the same thing. He displayed a similar level of cluefulness across
the board. And I worked another job at a startup where they were
pouring horrendous amounts of money into trying to get ColdFusion to
do the right thing. I went in thinking, hey, small company, obviously
broken software, they might be amenable to switching platforms; but
they had paid six figures for a bunch of consultants to build the
software, and they had invested another six figures into getting it to
work, and after that level of investment there was no way management
would admit that they had made a mistake, especially in such an
obvious way as changing development platforms.)
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: 20 Sep 2007 11:54:34 -0400
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: are you using Perl in your job?
Message-Id: <877imltjr9.fsf@mithril.chromatico.net>
>>>>> "PL" == Paul Lalli <mritty@gmail.com> writes:
PL> On Sep 19, 1:30 pm, Summercool <Summercooln...@gmail.com>
PL> wrote:
>> I heard there are many many Perl programmers. But the job
>> interviews I went to lately, they either use Java, PHP, Python,
>> or Ruby.
PL> Then go to better job interviews. http://jobs.perl.org
And be prepared to relocate: if you pay attention to jobs.perl.org for
any length of time, you'll notice that there's far more Perl activity
in some areas than in others.
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: Thu, 20 Sep 2007 11:41:04 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: are you using Perl in your job?
Message-Id: <m27iml70in.fsf@lifelogs.com>
On Wed, 19 Sep 2007 17:30:10 -0000 Summercool <Summercoolness@gmail.com> wrote:
S> I heard there are many many Perl programmers. But the job interviews
S> I went to lately, they either use Java, PHP, Python, or Ruby.
I'm not sure why you put a "but" in there, implying a connection. The
job interviews you've done lately don't have any significant correlation
to the worldwide number of Perl programmers.
S> So I wonder for all the people who know Perl quite well, are you
S> using Perl in your job?
Yes.
I also use Perl outside my job all the time. This is one of the things
that distinguish Perl programmers from programmers who know Perl.
Ted
------------------------------
Date: Thu, 20 Sep 2007 08:52:33 -0700
From: mattbreedlove@yahoo.com
Subject: Re: List Variable becomes undefined inexplicably
Message-Id: <1190303553.751484.24640@z24g2000prh.googlegroups.com>
The only reason the open command was commented was so that anyone
could run the test script to reproduce the problem. I tested the test
script with or without the commented "open" command so its not like
the array is getting undefined by the absence of input to the while
loop. It is certainly not the root cause.
I believe there is a place for strict and warnings. That place is not
necessarily in a quick test script to illustrate a completely
unrelated problem. Thanks
So the question remains, why is this happening? I appreciate the
suggestions to define a new variable in the instantiation of the
foreach/while loops, but the fact is that "should" not be required.
foreach (@SLAVE_HOSTS) {
chomp;
$REMOTE_HOST="$_";
open(CMD, "ping $REMOTE_HOST|");
while(<CMD>) {
chomp;
$LINE="$_";
}
}
print "@SLAVE_HOSTS\n";
PERL should be able to keep track of the frame of reference and values
for two discreet "$_" in nested iterative loops without blowing away a
parent array
This should be the same:
while(<CMD>) {
chomp;
$LINE="$_";
}
as this:
while ( $LINE = <CMD> ) {
chomp $LINE;
Such a "waste" of a precious line when it could be done with one line
less, but again the fact remains that this should work. Correct?
------------------------------
Date: Thu, 20 Sep 2007 16:54:59 -0000
From: Brian McCauley <nobull67@gmail.com>
Subject: Re: List Variable becomes undefined inexplicably
Message-Id: <1190307299.334889.211900@19g2000hsx.googlegroups.com>
On Sep 20, 4:52 pm, mattbreedl...@yahoo.com wrote:
> PERL should be able to keep track of the frame of reference and values
> for two discreet "$_" in nested iterative loops without blowing away a
> parent array
What you are actually saying is that the implicit assignment to $_ in
while(<FILEHANDLE>) should be implicit _localisation_ and assignment.
No argument from me there. If I had a time machine I'd go back and fix
it but there are probably moderately good reasons why it would be bad
to fix it now.
I always do a local(*_) before a while loop using implicit assignment
of $_ and I suggest that everyone should do so (or not use the
implicit assignment at all).
Do not be temped to do local($_) as nasty things will happen if the
"parent array" happens to be tied.
BTW: Please don't call Perl "PERL" as you'll just needlessly piss
people off.
------------------------------
Date: Thu, 20 Sep 2007 17:01:36 GMT
From: "John W. Krahn" <dummy@example.com>
Subject: Re: List Variable becomes undefined inexplicably
Message-Id: <QHxIi.76846$bO6.50671@edtnps89>
mattbreedlove@yahoo.com wrote:
>
> PERL should be able to keep track of the frame of reference and values
> for two discreet "$_" in nested iterative loops without blowing away a
> parent array
This "PERL" you speak of may be able to do that but here we use Perl which has
only one $_ variable.
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: Thu, 20 Sep 2007 10:10:46 -0700
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: List Variable becomes undefined inexplicably
Message-Id: <200920071010465139%jgibson@mail.arc.nasa.gov>
In article <1190303553.751484.24640@z24g2000prh.googlegroups.com>,
<mattbreedlove@yahoo.com> wrote:
> The only reason the open command was commented was so that anyone
> could run the test script to reproduce the problem. I tested the test
> script with or without the commented "open" command so its not like
> the array is getting undefined by the absence of input to the while
> loop. It is certainly not the root cause.
No, the open is not the root cause. The root cause is the input
operator <CMD> that you did _not_ comment out. In general, it is best
to post only relevant code, replacing such things as reading external
files with the equivalent assignment statements, for example, or using
the special <DATA> file handle so people can cut-and-paste your
program.
>
> I believe there is a place for strict and warnings. That place is not
> necessarily in a quick test script to illustrate a completely
> unrelated problem. Thanks
Fewer people will analyze your code if you don't have use strict. You
do want to get help, don't you? How can you be sure what is related and
what is not?
>
> So the question remains, why is this happening? I appreciate the
> suggestions to define a new variable in the instantiation of the
> foreach/while loops, but the fact is that "should" not be required.
>
> foreach (@SLAVE_HOSTS) {
> chomp;
> $REMOTE_HOST="$_";
>
> open(CMD, "ping $REMOTE_HOST|");
> while(<CMD>) {
> chomp;
> $LINE="$_";
> }
> }
> print "@SLAVE_HOSTS\n";
>
> PERL should be able to keep track of the frame of reference and values
> for two discreet "$_" in nested iterative loops without blowing away a
> parent array
Perl could, were it implemented that way, but it was not and does not.
You need to use a language the way it was implemented, not the way you
think it _should_ have been implemented. If you want a local version of
$_, use 'local $_;'.
>
> This should be the same:
> while(<CMD>) {
> chomp;
> $LINE="$_";
> }
>
> as this:
>
> while ( $LINE = <CMD> ) {
> chomp $LINE;
But the former has a side-effect, as you have discovered. It overwrites
the global $_ variable, which is aliased to a member of the
@SLAVE_HOSTS array. Since you do this for each element of @SLAVE_HOSTS,
and you are reading from an opening file handle, all of the members are
set to undef.
>
> Such a "waste" of a precious line when it could be done with one line
> less, but again the fact remains that this should work. Correct?
>
No, not correct. It should not work according to Perl's well-known
feature of using the global $_ variable as the default for many Perl
operations.
--
Jim Gibson
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
------------------------------
Date: Thu, 20 Sep 2007 10:32:06 -0700
From: kens <kenslaterpa@hotmail.com>
Subject: Re: List Variable becomes undefined inexplicably
Message-Id: <1190309526.785057.184380@n39g2000hsh.googlegroups.com>
On Sep 20, 11:52 am, mattbreedl...@yahoo.com wrote:
> The only reason the open command was commented was so that anyone
> could run the test script to reproduce the problem. I tested the test
> script with or without the commented "open" command so its not like
> the array is getting undefined by the absence of input to the while
> loop. It is certainly not the root cause.
>
> I believe there is a place for strict and warnings. That place is not
> necessarily in a quick test script to illustrate a completely
> unrelated problem. Thanks
I 'always' use strict and warnings. How do you know you don't have a
problem that is related until you try it?
>
> So the question remains, why is this happening?
Because of the way the foreach loop works - issue the command "perldoc
perlsyn" for more information.
>I appreciate the
> suggestions to define a new variable in the instantiation of the
> foreach/while loops, but the fact is that "should" not be required.
Playing the devil's advocate here. How would you refer to the $_
variable from the outer loop in the inner loop? Are you going to
force a label on the loops, so you can say OUTER_LOOP:$_ ?
>
> foreach (@SLAVE_HOSTS) {
> chomp;
> $REMOTE_HOST="$_";
>
> open(CMD, "ping $REMOTE_HOST|");
> while(<CMD>) {
> chomp;
> $LINE="$_";
> }}
>
> print "@SLAVE_HOSTS\n";
>
> PERL should be able to keep track of the frame of reference and values
> for two discreet "$_" in nested iterative loops without blowing away a
> parent array
>
> This should be the same:
> while(<CMD>) {
> chomp;
> $LINE="$_";
>
> }
>
> as this:
>
> while ( $LINE = <CMD> ) {
> chomp $LINE;
>
> Such a "waste" of a precious line when it could be done with one line
> less, but again the fact remains that this should work. Correct?
Not sure what you are referring to by 'this'. If you mean that $LINE
should contain the same value as $_ within the loop, I would say
yes.
Ken
------------------------------
Date: Thu, 20 Sep 2007 17:21:06 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: perl and unix command
Message-Id: <fcu35a$12h$1@nntp.fujitsu-siemens.com>
lerameur wrote:
> On Sep 20, 10:08 am, Tony Curtis <tony_curti...@yahoo.com> wrote:
>=20
>>lerameur wrote:
>>
>>>google?
>>>1,680,000 results, most of them refering to unix command in perl, in
>>>the one I looked, have not seen any with execution time analysis
>>>between commands.
>>>maybe you have googled one
>>
>>You didn't ask about "execution time analysis".
>>
>>Show us an example of what you're trying to do.
>=20
>=20
> I though I did in the first message.
> Example:
>=20
>>scan_log.pl
>>rm *.log
>=20
>=20
> here are the two unix command I want to put in a perl script, The scan
> log script can take 2 minutes to do the scan. I want to make sure the
> rm *.log command to starts after the scan_log. I am scared that once
> the scan_log.pl has been read, the script will go to the next line and
> run the rm *.log command before the scan_log.pl has finished scanning.
The system() function will not return until the command within has=20
terminated. Beware that if you write something like
system("scan_log.pl&");
then "the command within" is a shell, which in turn starts scan_log.pl=20
without waiting for it and thus will terminate before scan_log.pl has=20
finished.
I.e.
system("scan_log.pl");
system("rm *.log");
will be what you want.
--=20
These are my personal views and not those of Fujitsu Siemens Computers!
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://www.fujitsu-siemens.com/imprint.html
------------------------------
Date: Thu, 20 Sep 2007 08:28:18 -0700
From: lerameur <lerameur@yahoo.com>
Subject: Re: perl and unix command
Message-Id: <1190302098.797209.60380@50g2000hsm.googlegroups.com>
On Sep 20, 11:21 am, Josef Moellers <josef.moell...@fujitsu-
siemens.com> wrote:
> lerameur wrote:
> > On Sep 20, 10:08 am, Tony Curtis <tony_curti...@yahoo.com> wrote:
>
> >>lerameur wrote:
>
> >>>google?
> >>>1,680,000 results, most of them refering to unix command in perl, in
> >>>the one I looked, have not seen any with execution time analysis
> >>>between commands.
> >>>maybe you have googled one
>
> >>You didn't ask about "execution time analysis".
>
> >>Show us an example of what you're trying to do.
>
> > I though I did in the first message.
> > Example:
>
> >>scan_log.pl
> >>rm *.log
>
> > here are the two unix command I want to put in a perl script, The scan
> > log script can take 2 minutes to do the scan. I want to make sure the
> > rm *.log command to starts after the scan_log. I am scared that once
> > the scan_log.pl has been read, the script will go to the next line and
> > run the rm *.log command before the scan_log.pl has finished scanning.
>
> The system() function will not return until the command within has
> terminated. Beware that if you write something like
> system("scan_log.pl&");
> then "the command within" is a shell, which in turn starts scan_log.pl
> without waiting for it and thus will terminate before scan_log.pl has
> finished.
>
> I.e.
> system("scan_log.pl");
> system("rm *.log");
> will be what you want.
> --
> These are my personal views and not those of Fujitsu Siemens Computers!
> Josef M=F6llers (Pinguinpfleger bei FSC)
> If failure had no penalty success would not be a prize (T. Pratc=
hett)
> Company Details:http://www.fujitsu-siemens.com/imprint.html
ok thank you
k
------------------------------
Date: Thu, 20 Sep 2007 11:29:35 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: perl and unix command
Message-Id: <m2bqbx711s.fsf@lifelogs.com>
On Thu, 20 Sep 2007 06:11:58 -0700 lerameur <lerameur@yahoo.com> wrote:
l> I am writting a perl scipt in unix and I will invoking some unix
l> commands in my script. If the first command takes a few minutes to
l> process, how do I make sure the second command do not start until the
l> first command is finished ?
This is what will happen by default, unless the first command takes
special measures to detach itself and run in the background.
In Unix terms, the Perl process running the command is waiting for the
child process to exit every time it calls system(). There's more to the
picture (there are different ways to call system() for instance), but
this is the essential idea.
Ted
------------------------------
Date: 20 Sep 2007 16:39:10 GMT
From: xhoster@gmail.com
Subject: Re: perl and unix command
Message-Id: <20070920123912.404$we@newsreader.com>
lerameur <lerameur@yahoo.com> wrote:
> > > Hello,
> >
> > > I am writting a perl scipt in unix and I will invoking some unix
> > > commands in my script. If the first command takes a few minutes to
> > > process, how do I make sure the second command do not start until the
> > > first command is finished ?
> >
> > perldoc -f system
>
> ..
>
> />perldoc -f system
> ksh: perldoc: not found
Install Perl on your system.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Thu, 20 Sep 2007 13:09:14 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: perl and unix command
Message-Id: <m2fy19nu11.fsf@dot-app.org>
lerameur <lerameur@yahoo.com> writes:
>> > Hello,
>>
>> > I am writting a perl scipt in unix and I will invoking some unix
>> > commands in my script. If the first command takes a few minutes to
>> > process, how do I make sure the second command do not start until the
>> > first command is finished ?
>>
>> perldoc -f system
>
> ..
>
> />perldoc -f system
> ksh: perldoc: not found
Try "man system" - Perl docs are often installed as man pages also.
Also, check to see if your OS has a "perl-docs" or similar port|rpm|deb
or other package. Some vendors like to split Perl into multiple packages,
with separate developer and docs packages.
You really should fix this problem of missing docs before going any further
with anything else. Your question is a fairly simple one; I say that not to
insult you, but just to illustrate your experience level. At your level,
trying to learn Perl without having the docs on hand is like trying to paint
a wall with both hands tied. Both hands, and your feet too.
sherm--
--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
------------------------------
Date: Thu, 20 Sep 2007 17:18:21 GMT
From: "John W. Krahn" <dummy@example.com>
Subject: Re: perl and unix command
Message-Id: <xXxIi.76847$bO6.63467@edtnps89>
Sherm Pendley wrote:
> lerameur <lerameur@yahoo.com> writes:
>
>>>> Hello,
>>>> I am writting a perl scipt in unix and I will invoking some unix
>>>> commands in my script. If the first command takes a few minutes to
>>>> process, how do I make sure the second command do not start until the
>>>> first command is finished ?
>>> perldoc -f system
>> ..
>>
>> />perldoc -f system
>> ksh: perldoc: not found
>
> Try "man system" - Perl docs are often installed as man pages also.
That will probably get you the system(3) man page instead of Perl's system
function (although they basicly do the same thing.)
"man perlfunc" will get you the listing for Perl's system function.
> Also, check to see if your OS has a "perl-docs" or similar port|rpm|deb
> or other package. Some vendors like to split Perl into multiple packages,
> with separate developer and docs packages.
Kubuntu does this. I had to manually install a lot of stuff.
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: Thu, 20 Sep 2007 10:53:39 -0500
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Web interface to script?
Message-Id: <46f29783$0$495$815e3792@news.qwest.net>
Mike Stroud wrote:
> I have a perl script sitting in svn repos
whatever that is..
>, associated with many web
> development projects at my work. The script scoops the repo revision
> # and dumps it into a .txt that developers then print out to their
> pages to ensure version compatiblity (for me in qa, i can see what
> version im looking at and tell quickly what is a new bug and what's
> been fixed, etc..) It was recently requested that I add a 'web based
> interface' to my script(s, we are currently working on 20+ projects)
> to basically have a 'button that runs the script before the developers
> update their local repo'.
> Im not a super perl hacker, and dont know cgi very well, is there any
> pointers you can give me on how to accomplish this (or even better, a
> script that updates on checkout)?
Ever hear of an Internet search engine or new invention called a book? :-)
There are a lot of CGI tutorials on the Internet, you may use
your favorite search engine to find them. There are also
many CGI related books, some are also available online.
Possibly, something as simple as the following might get you started:
use CGI qw( :standard );
my $out = `/some/path/to/mikes_perl_script.pl`;
print header,
start_html( 'Output of mikes_perl_script' ),
h2( 'Some output' ),
pre( $out ),
end_html;
Take a look through the documentation for CGI, for other helpful methods:
perldoc CGI
------------------------------
Date: Thu, 20 Sep 2007 11:47:28 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Writing a C++ Style Checker
Message-Id: <m23ax9707z.fsf@lifelogs.com>
On Thu, 20 Sep 2007 04:52:07 -0000 ids <ishan.desilva@gmail.com> wrote:
i> What BenB suggested is not sufficient. Applying pattern matchings on a
i> line by line basis is not going help. For example, it won't allow me
i> to recognize a function implementation.
i> In a BNF grammar we can define a function using something similar to
i> the following.
i> func_impl : type_spec IDENTIFIER '(' opt_param_list ')' block ;
i> block : '{' opt_statement_list '}' ;
i> // define the other non terminals here
If you feel comfortable with this kind of grammar definition, definitely
look at the existing Parse::RecDescent solutions and try to extend one
of them.
I would suggest that coding standards are much easier to enforce by peer
review, especially since peer review will catch many errors (bugs and
inefficiencies) that an automatic checker won't. So if that's your
goal, please consider what you'll accomplish versus what you are
actually trying to do.
Ted
------------------------------
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 V11 Issue 869
**************************************
