[19047] in Perl-Users-Digest
Perl-Users Digest, Issue: 1242 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jul 4 06:10:32 2001
Date: Wed, 4 Jul 2001 03:10:13 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <994241412-v10-i1242@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Wed, 4 Jul 2001 Volume: 10 Number: 1242
Today's topics:
two changes <rlogsdon@io.com>
Re: two changes <magilfix@us.ibm.com>
Re: two changes <ubl@schaffhausen.de>
Re: two changes <pne-news-20010704@newton.digitalspace.net>
Re: two changes <pne-news-20010704@newton.digitalspace.net>
Re: two changes (Rasputin)
Re: Vapo-Rub (nospam)
Re: Vapo-Rub (Eric Bohlman)
Re: Vapo-Rub <somewhere@in.paradise.net>
Re: Vapo-Rub (Tim Hammerquist)
Re: web fetching <pne-news-20010704@newton.digitalspace.net>
XS and perlcrt <Florian.Albrecht@alcatel.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 4 Jul 2001 02:35:49 -0500
From: Reuben Logsdon <rlogsdon@io.com>
Subject: two changes
Message-Id: <Pine.LNX.4.33.0107040228220.8117-100000@fnord.io.com>
Would somebody please decide on a default path-to-perl for Unix and then
have all the Unix/Linux vendors implement it?
I default my CGI scripts to /usr/local/bin/perl. For 20% of my customers,
that path just doesn't seem to exist and they get all confused because
Apache returns internal server error, etc.
Also, could somebody make Unix Perl be forgiving about Perl CGI scripts
that have been uploaded in binary mode from a Windows machine?
If we added up all the hours of frustration and wasted time caused by
these two issues, it would exceed the lifetimes of everyone reading this
message. The human cost is very high and I think it reflects badly on
Perl.
Thanks,
Reuben
------------------------------
Date: Wed, 4 Jul 2001 02:52:56 -0500
From: Michael Gilfix <magilfix@us.ibm.com>
Subject: Re: two changes
Message-Id: <9huhtj$2fru$1@ausnews.austin.ibm.com>
Hiya. While I definitely agree that this would be really nice, it's really
difficult to guarantee because people might install different versions of Perl
in different places on a system while knowledge is not necessarily shared
across all of the IT staff :) In fact, many vendors ship with /usr/bin/perl
instead of /usr/local/bin/perl and the local ones tend to be
compiled-in-house. However, you could probably get around that by adding a
shell wrapper. Try something like:
#!/bin/sh -- # Last bit is to stop perl looping
eval 'exec `which perl` -S $0 ${1+"$@"}'
if 0;
By wrapping the `which perl` in backticks, you should probably be able to get
around this. I don't think this should affect your CGI either but there's only
one way to be sure :)
-- Mike
On Wednesday 04 July 2001 02:35%, Reuben Logsdon wrote:
> Would somebody please decide on a default path-to-perl for Unix and then
> have all the Unix/Linux vendors implement it?
>
> I default my CGI scripts to /usr/local/bin/perl. For 20% of my customers,
> that path just doesn't seem to exist and they get all confused because
> Apache returns internal server error, etc.
>
> Thanks,
> Reuben
--
Michael Gilfix
Extreme Blue Group - IBM (Austin)
magilfix@us.ibm.com
------------------------------
Date: Wed, 04 Jul 2001 11:14:50 +0100
From: Malte Ubl <ubl@schaffhausen.de>
Subject: Re: two changes
Message-Id: <3B42EC9B.7E7E2D8A@schaffhausen.de>
Reuben Logsdon schrieb:
>
> Would somebody please decide on a default path-to-perl for Unix and then
> have all the Unix/Linux vendors implement it?
uhmm, maybe some people in a UNIX newsgroup might do it, and then they tell
everybody to reinstall their BSD systems with 20 years of uninterrupted
uptime.
> I default my CGI scripts to /usr/local/bin/perl. For 20% of my customers,
> that path just doesn't seem to exist and they get all confused because
> Apache returns internal server error, etc.
As far as I know /usr/bin/perl is far more common, although both work most
of the time. Anyway, if you write applications with only a single executable
Perl file, there isnt much to change. Reading Apache's error log also helps
a lot.
> Also, could somebody make Unix Perl be forgiving about Perl CGI scripts
> that have been uploaded in binary mode from a Windows machine?
I think the problem lies not within Perl but within the shebang line not
being terminated in the way UNIX-systems like it. On my lovely mac with
the even more lovely BBEdit I can by default save files with unix line
breaks so they work even with binary upload. You can probably do the
same
thing under Windows. However, your scripts might not run there anymore.
Bye bye,
->malte
------------------------------
Date: Wed, 04 Jul 2001 11:40:10 +0200
From: Philip Newton <pne-news-20010704@newton.digitalspace.net>
Subject: Re: two changes
Message-Id: <50n5ktctns4mig4fem80vjopvtcgaisqcs@4ax.com>
On Wed, 4 Jul 2001 02:52:56 -0500, Michael Gilfix <magilfix@us.ibm.com>
wrote:
> Try something like:
>
> #!/bin/sh -- # Last bit is to stop perl looping
> eval 'exec `which perl` -S $0 ${1+"$@"}'
> if 0;
Or #!/usr/bin/env perl , if you know that Perl is going to be on
the default search path (well, it has to be for `which perl` to work, as
well). I believe that's what a lot of Python scripts do on their shebang
line.
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Wed, 04 Jul 2001 11:40:11 +0200
From: Philip Newton <pne-news-20010704@newton.digitalspace.net>
Subject: Re: two changes
Message-Id: <22n5kto1uembli45eq33n0u89jgile9vem@4ax.com>
On Wed, 4 Jul 2001 02:35:49 -0500, Reuben Logsdon <rlogsdon@io.com>
wrote:
> Also, could somebody make Unix Perl be forgiving about Perl CGI scripts
> that have been uploaded in binary mode from a Windows machine?
It is -- at least newer Perls copy fine with scripts that are terminated
by "\r\n". What you may be having problems with is the kernel; it takes
the filename from the shebang line and tries to execute that program
with the name of the script as an argument. And if you have
#!/usr/bin/perl^M
(with ^M representing the control-M or "\r" at the end of the line
before the Unix newline), then the kernel will complain that it can't
find a program called 'perl^M' living in /usr/bin. But if you use
#!/usr/bin/perl -wT^M
, then it should work fine since /usr/bin/perl is found. Yet another
reason to use -w :)
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Wed, 04 Jul 2001 09:46:56 GMT
From: rasputin@shaft.techsupport.co.uk (Rasputin)
Subject: Re: two changes
Message-Id: <slrn9k5pgp.1vo.rasputin@shaft.techsupport.co.uk>
Reuben Logsdon wrote:
> Would somebody please decide on a default path-to-perl for Unix and then
> have all the Unix/Linux vendors implement it?
>
> I default my CGI scripts to /usr/local/bin/perl. For 20% of my customers,
> that path just doesn't seem to exist and they get all confused because
> Apache returns internal server error, etc.
See other posts. Most half decent ISP/ hosting providedrs
should be symlinking /usr/bin/oerl to /usr/local/bin/perl,
or vice versa.
> Also, could somebody make Unix Perl be forgiving about Perl CGI scripts
> that have been uploaded in binary mode from a Windows machine?
??? Surely after years of getting errors, you've learned how to upload
in ASCII mode?
--
"These are the propulsion systems used by NASA for the moonshots,"
said Tom apologetically.
Rasputin :: Jack of All Trades - Master of Nuns ::
------------------------------
Date: Wed, 04 Jul 2001 05:26:01 GMT
From: Mark <"Beardedbear"@(nospam)Worldnet.att.net>
Subject: Re: Vapo-Rub
Message-Id: <JNx07.22191$C81.1754946@bgtnsc04-news.ops.worldnet.att.net>
No, just do it.
Anonymous wrote:
> I am thinking of using Vapo-Rub as a lubricant when I do the Wild Thing?
> Anyone know of precautions or tips?
>
> --------== Posted Anonymously via Newsfeeds.Com ==-------
> Featuring the worlds only Anonymous Usenet Server
> -----------== http://www.newsfeeds.com ==----------
------------------------------
Date: 4 Jul 2001 05:41:49 GMT
From: ebohlman@omsdev.com (Eric Bohlman)
Subject: Re: Vapo-Rub
Message-Id: <9huaat$rvh$1@bob.news.rcn.net>
In comp.lang.perl.misc Tad McClellan <tadmc@augustmail.com> wrote:
> Eric Bohlman <ebohlman@omsdev.com> wrote:
>>In comp.lang.perl.misc Anonymous <anonymous@anonymous.anonymous> wrote:
>>> I am thinking of using Vapo-Rub as a lubricant when I do the Wild Thing?
>>> Anyone know of precautions or tips?
>>
>>perldoc perlsex
> While RTFM still expands as it always does, it seems to take on
> a different meaning in the context of this thread...
Reminds me of the story about a rather obnoxious, drunk passenger on an
overnight flight. Sometime after he passes out, the pilot turns up the
lights, causing the passenger to wake up and yell "who turned on the
fucking lights?" The flight attendant goes to him and says "sir, these
are the reading lights. The fucking lights were on while you were
asleep."
ObPerl: I wonder what percentage of all Perl programs, CGI or not, exist
to support the operation of porn sites.
------------------------------
Date: Wed, 4 Jul 2001 16:35:00 +1000
From: "Tintin" <somewhere@in.paradise.net>
Subject: Re: Vapo-Rub
Message-Id: <vPy07.18$o76.233585@news.interact.net.au>
"Dallas McCarthy" <whitetip@iprimus.com.au> wrote in message
news:3b429d0a$1@news.iprimus.com.au...
> > >> I am thinking of using Vapo-Rub as a lubricant when I do the Wild
Thing?
> > >> Anyone know of precautions or tips?
> > >
> > >perldoc perlsex
> >
> >
> > While RTFM still expands as it always does, it seems to take on
> > a different meaning in the context of this thread...
>
> What the hell is this post about?
> Beat it.
Yes, you're on the right track there.
> Just Get Off.
You obviously know more than you let on.
------------------------------
Date: Wed, 04 Jul 2001 06:40:14 GMT
From: tim@vegeta.ath.cx (Tim Hammerquist)
Subject: Re: Vapo-Rub
Message-Id: <slrn9k5f8m.ru.tim@vegeta.ath.cx>
Eric Bohlman <ebohlman@omsdev.com> wrote:
> ObPerl: I wonder what percentage of all Perl programs, CGI or not, exist
> to support the operation of porn sites.
I can cite one, never-released, custom CGI script I wrote for a porn
site based in Dayton, NV.
I was quite proud of it. It was easily extendable,
and I learned most of the Perl language while writing it. It was my
first commercial script!
Of course, coming from so far back in my experience, I would probably
wince looking at the code now.
But in answer to your question, most porn sites (AFAIK) work like the
client-side programmer on the porn site:
- Frequent downloads from JavaScript.com and similar sites.
My script was never released because the site shortly went under. But
he paid well in the mean time. ;)
--
-Tim Hammerquist <timmy@cpan.org>
Just because my fingers are in my ears doesn't mean I'm ignoring you.
-- Larry Wall
------------------------------
Date: Wed, 04 Jul 2001 10:05:33 +0200
From: Philip Newton <pne-news-20010704@newton.digitalspace.net>
Subject: Re: web fetching
Message-Id: <jsh5kt40o28l1ehdiitjletb9l6uubf610@4ax.com>
On Tue, 3 Jul 2001 15:18:44 -0500 (CDT), dennis100@webtv.net (BUCK
NAKED1) wrote:
> Why do this? Because not all servers have LWP.pm or Socket.PM, or they
> don't allow you to install them.
Not even in your own home directory? You should be able to put anything
you want there. Nothing forces you to install modules under
/usr/local/lib/perl or wherever Perl stores its own modules.
> I really do think LWP and the other modules it requires to work, SHOULD
> be included in the main distribution.
And now XML is really popular, so an XML parser should be part of the
core distribution? And maybe DBI and a couple of DBD modules as well,
because lots of people use databases?
You have everything you need in the core distribution: basically, the
socket() command together with connect. Then you have to speak HTTP over
the socket. And IIRC Socket.pm is also part of core Perl, and simplifies
things by providing handy functions such as inet_aton and sockaddr_in.
IO::Socket and IO::Socket::INET make it even easier, but you don't
*need* them.
Cheers,
Philip
--
Philip Newton <nospam.newton@gmx.li>
That really is my address; no need to remove anything to reply.
If you're not part of the solution, you're part of the precipitate.
------------------------------
Date: Wed, 04 Jul 2001 11:33:43 +0200
From: Florian Albrecht <Florian.Albrecht@alcatel.de>
Subject: XS and perlcrt
Message-Id: <3B42E2F7.3C41F9CD@alcatel.de>
Hi,
I am working through perlXStut and I got an error by using nmake at the
first example and got the error message below. I am using WinNT with
ActiveState Perl5.6 an MSVC++ 5.0! What's my mistake? Perl -V:libc shows
msvcrt.lib and I also looked for perlcrt.lib, but I didn't found it on
my system. So I downloaded something from
http://www.perl.com/CPAN-local/modules/by-authors/id/D/DO/DOUGL/. But
did not help anything! :(
Any ideas? Thanx in advance!
;-) Florian
-- snip --
link -out:blib\arch\auto\Mytest\Mytest.dll -dll -nologo -nodefaultlib
-release -libpath:"C:\Perl\lib\CORE" -machine:x86 Mytest.obj
C:\Perl\lib\CORE\perl56.lib oldnames.lib kernel32.lib user32.lib
gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
oleaut32.lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib
version.lib odbc32.lib odbccp32.lib msvcrt.lib -def:Mytest.def
C:\Perl\lib\CORE\perl56.lib : fatal error LNK1106: Ungueltige Datei oder
Datentraeger voll: Positionieren auf 0x3a3d3dba nicht moeglich
NMAKE : fatal error U1077: 'link' : Rückgabe-Code '0xc'
------------------------------
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.
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 1242
***************************************
