[9151] in Perl-Users-Digest
Perl-Users Digest, Issue: 2769 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sat May 30 16:07:24 1998
Date: Sat, 30 May 98 13:00:24 -0700
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sat, 30 May 1998 Volume: 8 Number: 2769
Today's topics:
Re: An unwelcome and undeserved slap <hp@pobox.com>
Re: Autoloader question (Jonathan Stowe)
Re: Best tool? <merlyn@stonehenge.com>
Re: Best tool? (Chris Nandor)
Re: Don't Know how to decrypt using PERL (John Moreno)
Re: Don't Know how to decrypt using PERL <merlyn@stonehenge.com>
Re: Don't Know how to decrypt using PERL <lr@hpl.hp.com>
Re: Don't Know how to decrypt using PERL (Jonathan Stowe)
Re: Don't Know how to decrypt using PERL <tchrist@mox.perl.com>
Re: GPL documentation == unspeakable evil <hp@pobox.com>
Re: Have we got a good free Perl manual? scott@softbase.com
Re: Leap Year Script... <lr@hpl.hp.com>
Re: Leap Year Script... (Michael Armstrong)
Re: Perl Standard In/Out/Error on NT scott@softbase.com
Re: seek advice on simple first program (Andre L.)
Re: seek advice on simple first program <danboo@negia.net>
Re: seek advice on simple first program <lr@hpl.hp.com>
Re: Statistics for comp.lang.perl.misc <mike.schleif@aquila.com>
Re: uploading files (Sirrocco)
What does the FSF want? (was Re: GPL documentation == u <bruce@cenderis.demon.co.uk>
Digest Administrivia (Last modified: 8 Mar 97) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 30 May 1998 18:03:17 GMT
From: robert havoc pennington <hp@pobox.com>
Subject: Re: An unwelcome and undeserved slap
Message-Id: <wsnd8cvprfe.fsf@harper.uchicago.edu>
lvirden@cas.org writes:
>
> This is, to me, one of the central reasons for the FSF-related flame wars
> that have recurred for years.
>
> The Lewis-Carroll-like approach of treating words as meaning whatever
> one wants, often with meanings quite different to traditional usage
> (ala Orwellian new-speak), seems to be done intentionally to stir up
> controversy and argument.
>
*Any* social-change kind of organization will use words to get their
point across, often changing meanings along the way. Invented
buzzwords: "family values" (whoah, when did that start to mean
"conservative values"?); "gay" (oops, doesn't mean "happy" anymore).
Do you think the Bob Dole and the ACLU mean the same thing when
they say "freedom" and "liberty"?
Values and beliefs are embedded in the words that we use. Part of any
attempt to change values and beliefs is changing the way we use
language. If you can't change the language you can't change what
people think beyond certain parameters. It's a simple fact.
I would point out to you that the controversy comes from the values
being advocated, not the language change. Do you really think all the
people whining about "ruining a perfectly good word for 'happy'" a few
decades ago were upset about semantics rather than sex?
Havoc Pennington ==== http://pobox.com/~hp
------------------------------
Date: Sat, 30 May 1998 17:01:12 GMT
From: Gellyfish@btinternet.com (Jonathan Stowe)
Subject: Re: Autoloader question
Message-Id: <35703905.22003284@news.btinternet.com>
On 30 May 1998 16:14:33 GMT, Nathan V. Patwardhan wrote :
>Jonathan Stowe (Gellyfish@btinternet.com) wrote:
>
>: OK, I did this (my perl libraries are in /develop/lib/perl5 - yours
>: probably arent):
>
>Hmmmm. Why not use h2xs? It will do all of this stuff for you:
>
Hey, excellent I get to learn two new things in one thread. Except :
~/splittes> make
make.exe: *** [blib/lib/_exists] Error -1
[exited with 2]
~/splittes>
;-{
I've never quite sussed that one out. Never mind its a djgpp thing.
/J\
Jonathan Stowe
Some of your questions answered:
<URL:http://www.btinternet.com/~gellyfish/resources/wwwfaq.htm>
------------------------------
Date: Sat, 30 May 1998 17:19:02 GMT
From: Randal Schwartz <merlyn@stonehenge.com>
Subject: Re: Best tool?
Message-Id: <8cg1hr3ce8.fsf@gadget.cscaper.com>
>>>>> "Zenin" == Zenin <zenin@bawdycaste.org> writes:
Zenin> Nope, X Windows is.
What's "X Windows"? Is that like "Microsoft Windows"?
I've heard of "X", "X11", and "the X Window System". But never "X Windows".
I've seen "X" put up "windows", so I'd call those "X windows", but not
"X Windows".
:-)
(I've even hung up the phone on a recruiter once because he called me
to see if I could program "X Windows", and I said "no such thing" and
he didn't get it. Stoopid recruiter. :-)
print "Just another Perl hacker," # but not what the media calls "hacker!" :-)
## legal fund: $20,990.69 collected, $186,159.85 spent; just 93 more days
## before I go to *prison* for 90 days; email fund@stonehenge.com for details
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: Sat, 30 May 1998 18:54:40 GMT
From: pudge@pobox.com (Chris Nandor)
Subject: Re: Best tool?
Message-Id: <pudge-3005981449000001@dynamic416.ply.adelphia.net>
In article <8cg1hr3ce8.fsf@gadget.cscaper.com>, Randal Schwartz
<merlyn@stonehenge.com> wrote:
# I've heard of "X", "X11", and "the X Window System". But never "X Windows".
You HAVE heard of it.
--
Chris Nandor mailto:pudge@pobox.com http://pudge.net/
%PGPKey = ('B76E72AD', [1024, '0824090B CE73CA10 1FF77F13 8180B6B6'])
------------------------------
Date: Sat, 30 May 1998 17:12:49 GMT
From: phenix@interpath.com (John Moreno)
Subject: Re: Don't Know how to decrypt using PERL
Message-Id: <1d9ue1h.1634op11qi7iujN@roxboro0-054.dyn.interpath.net>
Larry Rosler <lr@hpl.hp.com> wrote:
> brian d foy wrote in message ...
> ...
> >
> >and of course you gave up and posted to comp.lang.perl.misc because
> >you expect to be spoonfed. the problem with your philosophy is
> >that no one ever learns how to do things, and you are the epitome
> >of that consequence.
> >
> >i'm sorry that you are stupid. here are the detailed instructions for
> >idiots:
> >
> >1. go to <URL:http://www.yahoo.com>
> >
> >2. in the text widget at the top, type "unix man pages", and select
> >the submit button. it's a fairly obvious thing to search on.
> >
> >3. the results page has 4 hits. one says
> >"Linux Manual Pages [John Martin]". select that or try the other
> three.
> >
> >4. one the search form for "Linux Manual Pages [John Martin]", type
> >"crypt" and select "Section 3 - C Library Routines" from the pulldown
> >menu. select the "Find" button.
> >
> >5. you now see the crypt(3) man page. slow modems aside, these five
> >steps took 15 seconds.
> >
> >get a clue.
>
>
> OK, let's summarize.
>
> I am a stoopid noobie Windows Perl user. I want to use the Perl crypt()
> function, I read the Perl documentation, and I ask in c.l.p.m. for more
> information about the purpose of the 'salt' argument. I am told `man 3
> crypt`.
I take exception to the "stoopid noobie" remark - there's nor reason to
suppose that you are stupid.
> At the DOS command line, I type 'man 3 crypt' and get 'No entry for
> "crypt" in section 3 of the manual'. (It knows about 'man' at all only
> because I have bought and installed MKS to make my system more
> Unix-like. Maybe I'm not all that stoopid.) I type 'man 3 printf' and
> get a similar response. In fact, there is nothing at all in section 3
> of the manual, because I do not have a C compiler! (Does that make me
> more stoopid? No, it makes me an idiot.) It's nice that 'man 1 date'
> works, though, because I have lots of Unix (Posix) commands, such as
> 'man'. I am a very unusual Windows Perl User. Now what?
>
> I go to Yahoo!, my favorite search engine, and search for 'man crypt'.
> I get one (1) response, having to do with _crypt_ography. Gosh, I
> should have used AltaVista, or Lycos, or Excite, or something, but I'm
> too stoopid.
Let's see, Brian wrote:
> see the man page for crypt(3) which (definatively) explains all of this.
So, Yahoo, "man page for crypt(3)" and click on the first match - yahoo!
that's it!
> A little bird whispers in my ear, "Here's a clue. Try 'unix man pages'.
> It's a fairly obvious thing to search on, because Perl uses the C
> library and C is Unix." The bird is not stoopid, just completely wrong.
> But I do it anyway, and get 4 links. Two of them are dead, and the
> third one returns a blank page with some explanatory shrugs. But the
> fourth link gets me the answer I've been looking for. "Slow modems
> aside, these five steps took 15 seconds." Bull-bleep!
What took me longest was finding the original statement and then
starting up IE.
> Which brings me back to the original point, which maybe by now all you
> Unix geniuses will begin to understand:
Not a unix geniuses (in fact I hardly qualify as a unix user, only doing
so via telnet every 4 or 5 months).
> Perl is not C. C is not Unix. Perl is not Unix. "Read the F***ing
> Unix Manual" is not a helpful response to questions on c.l.p.m. about
> Perl, especially to questions from Windows (or Mac?!) users.
No, but indicating a method of search is better than giving a answer -
it can be used for other questions, which is the real point.
> Perhaps further insults should go to /dev/null (oops, I mean NUL:). <--
> NO :-) HERE!!!
Well, if you want put a chicken in it and send it to alt.dev.null, it's
been pretty quite recently.
--
John Moreno
------------------------------
Date: Sat, 30 May 1998 17:14:26 GMT
From: Randal Schwartz <merlyn@stonehenge.com>
Subject: Re: Don't Know how to decrypt using PERL
Message-Id: <8ck9733clv.fsf@gadget.cscaper.com>
>>>>> "Chris" == Chris Nandor <pudge@pobox.com> writes:
Chris> perl -le 'print crypt($ARGV[0], substr($ARGV[0], 0, 2))' mypassword
Chris> myylAylKPNtmw
Waaaayy too much typing. I've never seen a crypt() that didn't
ignore everything after the first two chars given as a salt:
crypt($ARGV[0], $ARGV[0])
would have worked just fine.
print "Just another Perl hacker," # but not what the media calls "hacker!" :-)
## legal fund: $20,990.69 collected, $186,159.85 spent; just 93 more days
## before I go to *prison* for 90 days; email fund@stonehenge.com for details
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@teleport.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: Sat, 30 May 1998 11:00:31 -0700
From: "Larry Rosler" <lr@hpl.hp.com>
Subject: Re: Don't Know how to decrypt using PERL
Message-Id: <6kphge$oo4@hplntx.hpl.hp.com>
[posted and emailed]
John Moreno wrote in message
<1d9ue1h.1634op11qi7iujN@roxboro0-054.dyn.interpath.net>...
...
>Let's see, Brian wrote:
>> see the man page for crypt(3) which (definatively) explains all of
this.
>
>So, Yahoo, "man page for crypt(3)" and click on the first match -
yahoo!
>that's it!
There is wonderful juju here. Instead of "man page for crypt(3)" try
"man page for crypt (3)" or any variation thereof, with or without the
parentheses. One useless response!
The original c.l.p.m. response (remember way back when? :-) was `man 3
crypt`. Now just suppose one hadn't been born and bred with date(1) or
crypt(1) or crypt(3)?
This has been a very instructive morning (though not about Perl):
Mysteries of web searching like the one above, and the remarkable
discovery from another thread that <URL:http://www.perl.com/CPAN> ne
<URL:http://www.perl.com/CPAN/>. Keep 'em coming, folks!
--
Larry Rosler
Hewlett-Packard Laboratories
lr@hpl.hp.com
------------------------------
Date: Sat, 30 May 1998 18:21:17 GMT
From: Gellyfish@btinternet.com (Jonathan Stowe)
Subject: Re: Don't Know how to decrypt using PERL
Message-Id: <357043e0.24776173@news.btinternet.com>
On Sat, 30 May 1998 17:12:49 GMT, John Moreno wrote :
>Larry Rosler <lr@hpl.hp.com> wrote:
>
<snip>
< I think I've got these attributions right but this is getting
confusing>
>>
>> OK, let's summarize.
>>
>> I am a stoopid noobie Windows Perl user. I want to use the Perl crypt()
>> function, I read the Perl documentation, and I ask in c.l.p.m. for more
>> information about the purpose of the 'salt' argument. I am told `man 3
>> crypt`.
>
>I take exception to the "stoopid noobie" remark - there's nor reason to
>suppose that you are stupid.
>
Hey, if Larry wants to play the part as "stoopid newbie" then thats
alright: you've got to get with the motivation for the role. I mean
its not as if he's saying "I am a crustacean CP/M user" which might
stretch even the greatest talent. I mean do you think its mere
coincidence that Larry shares his name with one of the greatest
English actors (actually I think it probably is but it would spoil the
script.)
Actually if this thread is going to reach its full potential we might
have to pay a bit more for the talent anyhow. I've pencilled in
Quentin to direct and Tim Curry is going to play the role of me - We
havent decided on the other parts yet, but I'm sure its going to big.
/J\
Hey and this is before the beer.
Jonathan Stowe
Some of your questions answered:
<URL:http://www.btinternet.com/~gellyfish/resources/wwwfaq.htm>
------------------------------
Date: 30 May 1998 19:01:12 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: Don't Know how to decrypt using PERL
Message-Id: <6kpl1o$aef$1@csnews.cs.colorado.edu>
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc, "Larry Rosler" <lr@hpl.hp.com> writes:
:Now just suppose one hadn't been born and bred with date(1) or
:crypt(1) or crypt(3)?
This is getting really tiresome, Larry. Could you find
some other axe to grind?
--tom
--
"That which does not kill me makes me stranger." --Larry Wall
------------------------------
Date: Sat, 30 May 1998 18:12:17 GMT
From: robert havoc pennington <hp@pobox.com>
Subject: Re: GPL documentation == unspeakable evil
Message-Id: <wsnbtsfpr0e.fsf@harper.uchicago.edu>
lvirden@cas.org writes:
>
> Frankly, because of the distance between meanings of 'free' that people
> have, it seems unproductive to attempt to come to an agreement.
>
Nonsense. We can agree that the manuals are "free" under meaning A,
but not under meaning B. I think most people do agree on that. Seems
pretty obvious.
Also seems obvious that the real issue is which meaning of free should
be required for these manuals, not which meaning of free is "right."
Havoc Pennington ==== http://pobox.com/~hp
------------------------------
Date: 30 May 1998 15:12:54 GMT
From: scott@softbase.com
Subject: Re: Have we got a good free Perl manual?
Message-Id: <6kp7lm$pch$3@mainsrv.main.nc.us>
I *learned* Perl in 1994 from the manual page!
Scott
--
Look at Softbase Systems' client/server tools, www.softbase.com
Check out the Essential 97 package for Windows 95 www.skwc.com/essent
All my other cool web pages are available from that site too!
My demo tape, artwork, poetry, The Windows 95 Book FAQ, and more.
------------------------------
Date: Sat, 30 May 1998 10:38:00 -0700
From: "Larry Rosler" <lr@hpl.hp.com>
Subject: Re: Leap Year Script...
Message-Id: <6kpg63$obv@hplntx.hpl.hp.com>
[posted and emailed]
Michael Armstrong wrote in message <35703279.65947337@news.visi.com>...
>Wouldn't it be easier to just subtract the day at the localtime(time)
>statement and cut out most of the rest of the code. Leaving you with:
>
>#!/usr/perl
>
>($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time
>- 86400);
>$mon++; # adjusts the month to go from 1-12 instead of 0-11
># $year = $year + 1900; # uncomment this line to use 4 digit years.
>$time = localtime(time);
>
>print "Today is $time\n";
>print "yday = $yday\n";
>print "wday = $wday\n";
>print "isdat = $isdst\n";
>print "Time is $hour:$min:$sec\n";
>print "Date is $month-$mday-$year\n";
Hmmm. Then 20 months from now this will print "Date is 1-30-101"
(assuming you replace $month by $mon, as you intended).
I think you must use either $year + 1900 or $year % 100, as you wish.
--
Larry Rosler
Hewlett-Packard Laboratories
lr@hpl.hp.com
------------------------------
Date: Sat, 30 May 1998 18:52:05 GMT
From: michaela@phosphor.com (Michael Armstrong)
Subject: Re: Leap Year Script...
Message-Id: <357153e0.74495999@news.visi.com>
On Sat, 30 May 1998 10:38:00 -0700, "Larry Rosler" <lr@hpl.hp.com>
spake thusly:
[snip]
>Hmmm. Then 20 months from now this will print "Date is 1-30-101"
>(assuming you replace $month by $mon, as you intended).
Doh! (reminder to self: proofread twice, not just once.)
>I think you must use either $year + 1900 or $year % 100, as you wish.
You're right, I forgot that the year 2000 will come out of localtime()
as 100. Guess my brain isn't fully Y2K compliant yet. ;-)
Thanks for the corrections.
---
Michael Armstrong
michaela@phosphor.com http://www.phosphor.com/
Full service Web design and Internet consulting
------------------------------
Date: 30 May 1998 15:20:02 GMT
From: scott@softbase.com
Subject: Re: Perl Standard In/Out/Error on NT
Message-Id: <6kp832$pch$4@mainsrv.main.nc.us>
Jahan@PriceCut.com wrote:
> % program < input_data > output_data
> where my program is the executable that takes user input
> the input_data is data that is piped in the program
> and the output_data is the result of the program which will be captured in the
> outout_data file.
> I am trying to write a perl script to execute "program" for me and pipe the
> input_data to it and capture the output of the "program".
> How do I accomplish this using perl on windows NT?
>From what I gather, you are trying to actually write a shell that
binds the stdin/out/err of the program you are calling to
the one in your program like a shell would. I don't think that
can be done in NT Perl as it stands now. You would have to be
able to call the CreateProcess API and tell it to inherit the
files of the existing process.
The easy, copout way to do it is to just write the data to
files and call the NT shell.
I've never seen the source code to a command interpreter for
a Win32 platform, and don't know how they do many of the UNIX
things that can't be done in NT like file redirection. They
may do the copout themselves like DOS used to. If they do it
via the API, though, it would be so down and dirty I bet Perl
wouldn't support it because you can't directly call the API.
Scott
--
Look at Softbase Systems' client/server tools, www.softbase.com
Check out the Essential 97 package for Windows 95 www.skwc.com/essent
All my other cool web pages are available from that site too!
My demo tape, artwork, poetry, The Windows 95 Book FAQ, and more.
------------------------------
Date: Sat, 30 May 1998 13:46:50 -0500
From: alecler@cam.org (Andre L.)
Subject: Re: seek advice on simple first program
Message-Id: <alecler-3005981346500001@dialup-867.hip.cam.org>
(Posted and mailed, in the hope that the confusion will stop here.)
<sigh>
print @array;
does *not* append the output record separator to the elements of @array.
It appends $\ to the end of the printed output, that's all. You obviously
misread the Book.
Therefore, yes it is faster than doing
print "@array";
except you're comparing apples and oranges.
If you were to compare comparable things, they should be:
print "@array";
and
foreach (@array) { print }
and you'd see that the former is far more efficient.
A.L.
===========================
In article <6kp7k5$m6o@hplntx.hpl.hp.com>, "Larry Rosler" <lr@hpl.hp.com> wrote:
> [posted and emailed]
>
> Shaun Sides wrote in message ...
> >Original message by: Larry Rosler <lr@hpl.hp.com>
> >Date: Sat, 30 May 1998 01:07:02 -0700
> >Subject: Re: seek advice on simple first program
> >
> >
> >> That's neat, and suggests Yet Another Way to Do It, using $\, the
> output
> >> record separator:
> >>
> >> $\ = "\n";
> >> ...
> >> print F @content;
> >> ...
> >>
> >> I Benchmark this about 30% faster than using $". YMMV, of course.
> >
> >Why do you suppose the list separator is so much faster than the output
> >record separator? Geez, when they say there's more than one way, that
> >ain't no joke, eh? ;-)
> ...
>
> No joke. Real benefit. You can often choose between programmer
> efficiency or execution efficiency (which is why the Benchmark module is
> so useful when run-time performance matters), between clarity of
> expression and elegance (or obfuscation, if you insist), and on and on.
>
> In this case, it was no surprise to me that the output record separator
> is significantly faster than the list separator. (I think you meant
> your sentence the other way around.)
>
> Consider the semantics of the two statements 'print "@content\n";' and
> 'print @content;'.
>
> The first statement instructs perl to construct a (long) string
> comprising the elements of @content joined by the list separator,
> exactly as if it read 'print join($", @content) . "\n";' This
> concatenation takes significant time.
>
> The second statement instructs perl to print the elements of the list
> constructed from the elements of @content, printing the output record
> separator $\ after each list element. As discussed elsewhere (if I were
> at my office, I would start to look somewhere around page 540 in the
> Blue Camel), the 'print' statement efficiently prints the elements of
> its list argument one at a time, without concatenation. As I recall,
> the book says the speed tradeoff is architecture dependent and should be
> verified. So I did.
>
> --
> Larry Rosler
> Hewlett-Packard Laboratories
> lr@hpl.hp.com
------------------------------
Date: Sat, 30 May 1998 13:52:37 -0400
From: Dan Boorstein <danboo@negia.net>
Subject: Re: seek advice on simple first program
Message-Id: <35704765.4B99D853@negia.net>
Andre L. wrote:
>
> ... and Larry Rosler <lr@hpl.hp.com> wrote:
>
> > That's neat, and suggests Yet Another Way to Do It, using $\, the output
> > record separator:
> >
> > $\ = "\n";
> > ...
> > print F @content;
> > ...
> >
> > I Benchmark this about 30% faster than using $". YMMV, of course.
>
> Hi Larry,
>
> Inside a while loop, modifying $\ would be an obvious approach, of course,
> but it does not work if you print all the file at once with a single print
> statement. It only adds a newline at the end of the file. So I'm not
> surprised at the difference in speed you measured; the thing is, it
> doesn't do what it's supposed to. :-)
i think larry was looking for '$,' which is the output *field* separator.
sorry no benchmark comparisons.
--
Dan Boorstein home: danboo@negia.net work: danboo@y-dna.com
"THERE IS AS YET INSUFFICIENT DATA FOR A MEANINGFUL ANSWER."
- Cosmic AC
------------------------------
Date: Sat, 30 May 1998 12:38:47 -0700
From: "Larry Rosler" <lr@hpl.hp.com>
Subject: Re: seek advice on simple first program
Message-Id: <6kpn94$q9j@hplntx.hpl.hp.com>
(Posted and mailed, in the hope that the confusion will stop here.)
Andre L. wrote in message ...
>(Posted and mailed, in the hope that the confusion will stop here.)
...
>If you were to compare comparable things, they should be:
>
> print "@array";
>and
> foreach (@array) { print }
>
>and you'd see that the former is far more efficient.
>
>A.L.
You are absolutely right, and I am absolutely wrong. My apologies.
Here is a Benchmark, for those who are interested:
#!/usr/local/bin/perl -w
use Benchmark;
open OUT, '>/dev/null' or die $!;
@a = ( 'a' x 100 . "\n" ) x 10000;
timethese (10, {
'$LIST_SEPARATOR' => q{
local $" = "\n";
print OUT "@a\n";
},
'bogus' => q{
local $\ = "\n";
print OUT @a;
},
'$OUTPUT_RECORD_SEPARATOR' => q{
local $\ = "\n";
foreach (@a) { print OUT }
},
'control' => q{
local $\ = "\n";
foreach (@a) { }
},
} );
Benchmark: timing 100 iterations of $LIST_SEPARATOR,
$OUTPUT_RECORD_SEPARATOR, bogus, control...
$LIST_SEPARATOR: 9 secs ( 7.50 usr 0.08 sys = 7.58 cpu)
$OUTPUT_RECORD_SEPARATOR: 18 secs (16.36 usr 0.20 sys = 16.56 cpu)
bogus: 7 secs ( 5.60 usr 0.15 sys = 5.75 cpu)
control: 5 secs ( 3.72 usr 0.01 sys = 3.73 cpu)
--
Larry Rosler
Hewlett-Packard Laboratories
lr@hpl.hp.com
------------------------------
Date: Sat, 30 May 1998 19:53:06 GMT
From: "Michael D. Schleif" <mike.schleif@aquila.com>
Subject: Re: Statistics for comp.lang.perl.misc
Message-Id: <35706290.22192B14@aquila.com>
Am I missing something?
With hundreds of posts to this newsgroup per week, how can it be so
difficult to follow ONLY those threads that interest you?
Diatribe is diatribe. Period.
I prowl through dozens of newsgroups and thousands of articles every
week, week in and week out, year after year -- I have been doing this
longer than most. Of those thousands and thousands of articles per
week, only a few dozen really interest me, at the time. I read those.
I mark the others "read" and move on. Is this rocket science? Do I
need an advanced degree to do this? NOT.
I read what some of you are presenting as objections based on
suitability of Tom's article to this newsgroup. Your words are clear;
but, your intent is obfuscated. How can you respond to Tom's polemic
without first reading it, or much of it? Why would you bother, if said
topic is NOT interesting to you? Clearly, to me, an outsider who does
NOT know you, but by your signature, you and those singing your song
have other motivation here. You disagree with Tom, and you are posting
said disagreement to this same newsgroup -- of course, prompting others
to perpetuate this thread by responding to you . . .
If this thread is NOT interesting to you, mark this thread "Ignore" and
go on to the next. Very simple.
If your intent is NOT to paint this thread uninteresting, off-topic and
inappropriate, then say so. Then, people like me would not be tempted
to turn your diatribe back on your own posting. Read what you wrote and
tell me how your submission has any more right to be published here!
Remember, Perl is a language, like English or Spanish. As such, it has
rules, conventions and standards that impose structure on our use of it;
but, its primary reason for existing is communication.
Communication usually promotes clear transmission of intent and
content. Obfuscation is usually the result of trying NOT to
communicate, to hide something behind other things dissimilar.
I like to think that Forums, such as this newsgroup, promote
communication and NOT obfuscation. I go elsewhere when I want to become
confused . . .
jimbo@soundimages.co.uk wrote:
> Bullshit. Why should this newsgroup have to endure the copyright
> issues relating to ONE man? Tom's faq's do not perl documentation
> make. Indeed without pod faq is gibberish. Relating to YOU is what you
> meant, Mister Two X-Terms is what REAL users are made of. What a load
> of crap. Oh gee, Tom is a Guru-cum-God, his personal rights, liberties
> and freedoms are at stake, let's crosspost and whine and winge until
> we make our point! When will this happen for one of the regular
> readers of the group? ANSWER: NEVER.
>
> The hell with PERL questions. You know, Perl, the tool? I'm sure
> you've heard of it? You must have. You've made your I'm a command-line
> man so piss-off-the-rest-of-you speeches before on the subject. What's
> wrong with an IDE? What's right with one? I'm tuff as nails and your
> not.
--
Best Regards,
mds
mds resource
888.250.3987
"Dare to fix things before they break . . . "
"Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . . "
------------------------------
Date: Sat, 30 May 1998 18:20:11 GMT
From: martin.labrecque@usa.net (Sirrocco)
Subject: Re: uploading files
Message-Id: <35704dc2.20155025@news.videotron.net>
On Tue, 26 May 1998 14:38:11 -0700, Garrick Staples
<webmaster@directnet.com> wrote:
>I have an application to use the nifty html file upload feature.
>However implementaion has been a bear. I started this project by doing
>the form decoding myself, but that became problematic; I can't seem to
>find any documentation about the "multipart/form-data" enctype. So then
>I looked at the "CGI::BasePlus" module, but can't seem to get that to
>work.
> I guess my question is "Does anybody have any sample scripts that
>upload files?" I don't care if I use the CGI module or not, I just want
>the mulitpart/form-data decoded.
> Thanks in advance for that certain life saver out there.
>-Garrick
If eversomeby finds a solution to this question, mail it to:
martin.labrecque@usa.net
thanks
------------------------------
Date: 30 May 1998 14:46:50 +0100
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Subject: What does the FSF want? (was Re: GPL documentation == unspeakable evil
Message-Id: <m3af7zyiph.fsf_-_@cenderis.demon.co.uk>
lvirden@cas.org writes:
> Frankly, because of the distance between meanings of 'free' that
> people have, it seems unproductive to attempt to come to an
> agreement.
The intended meaning doesn't seem difficult to divine. The FSF wants
people like RedHat to be able to include the documentation on CDs (and
to make a profit by doing so), and it doesn't seem that the authors
disagree with that, so long as they get suitable credit.
The trickier bit is that the FSF want to be able to modify the
documentation if they see fit (to improve parts, perhaps, or if they
modify perl itself, to modify the documentation to match).
I'd have thought there could be some compromise in this area too
(crediting the original authors, but making clear that their work has
been changed). But apparently I'm wrong.
In any case, as far as I remember the original intention was to ask
for free (as in modifiable, redistributable) documentation which reads
like the book, which is different to a bunch of documents each of
which is very good, but perhaps lacks the overall structure of, say,
the Emacs manual. I didn't understand the request to be about the
manpages at all.
------------------------------
Date: 8 Mar 97 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 8 Mar 97)
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.
To submit articles to comp.lang.perl.misc (and this Digest), send your
article to perl-users@ruby.oce.orst.edu.
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.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
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 V8 Issue 2769
**************************************
