[17076] in Perl-Users-Digest
Perl-Users Digest, Issue: 4488 Volume: 9
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Oct 2 09:10:11 2000
Date: Mon, 2 Oct 2000 06:05:16 -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: <970491916-v9-i4488@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Mon, 2 Oct 2000 Volume: 9 Number: 4488
Today's topics:
Re: "use Foo qw(bar)" vs. "use Foo qw(&bar)" -- What's nobull@mail.com
A warning about ActiveState Perl/IIS ajmayo@my-deja.com
Add on kily@my-deja.com
Re: AppConfig fsconzo@my-deja.com
Re: automatic email attachments (Villy Kruse)
Re: benefits of perl (Mark-Jason Dominus)
Re: benefits of perl (Martien Verbruggen)
CGI.pm / saving records <philipp.schill@t-online.de>
Re: CGI.pm / saving records <flavell@mail.cern.ch>
Re: CGI.pm / saving records <anders@wall.alweb.dk>
Re: CGI.pm / saving records <brian+usenet@smithrenaud.com>
DBI.pm for MySQL & Perl 5 kellymartin@my-deja.com
Re: DBI.pm for MySQL & Perl 5 <anders@wall.alweb.dk>
Re: die() ignores tied STDERR? (Daniel Chetlin)
Re: die() ignores tied STDERR? (Martien Verbruggen)
Re: Executing a program from a CGI (Rafael Garcia-Suarez)
Re: File upload testing if it's there <lr@hpl.hp.com>
Re: How to detect modules currently in use? (Daniel Chetlin)
Re: How to get length of scalar? <bcaligari@my-deja.com>
Re: Huh? (Anno Siegel)
Re: Huh? <mauldin@netstorm.net>
Re: Inserting HTML into CGI script as if it was beingin <bart.lateur@skynet.be>
Install problem on SCO <proton@iiidns.iii.org.tw>
Digest Administrivia (Last modified: 16 Sep 99) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 02 Oct 2000 08:46:44 +0100
From: nobull@mail.com
Subject: Re: "use Foo qw(bar)" vs. "use Foo qw(&bar)" -- What's the difference?
Message-Id: <u9em1zhcup.fsf@wcl-l.bham.ac.uk>
Jeff Pinyan <jeffp@crusoe.net> writes:
> On Sep 29, nobull@mail.com said:
> >How about looking at the source of Exporter.pm? It clearly strips
> >leading '&' from things in the list. Since this is undocumented and
> >all the examples in the documentation don't have a leading '&' I think
> >it would be better to leave it off.
>
> I don't think YOU looked at the source of Exporter.pm. ;)
>
> The only place it strips the &'s is in the module USING Exporter:
>
> [line 39]
Not the _only_ place:
[line 94]
foreach $sym (@imports) {
if (!$exports{$sym}) {
# [snip]
} elsif ($sym !~ s/^&// || !$exports{$sym}) {
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Mon, 02 Oct 2000 10:52:22 GMT
From: ajmayo@my-deja.com
Subject: A warning about ActiveState Perl/IIS
Message-Id: <8r9pd5$beu$1@nnrp1.deja.com>
If you were considering replacing VBScript with ActiveState Perl using
Microsoft IIS, be aware that server-side debugging is not supported. I
thought I was looking at a bug when I reported that the debugger didn't
work, but apparently this is not supported. In other words, sure, you
can write backend server-side code in Perl and use it with IIS, but for
debugging, you're back in the dark ages of print statements. They sure
don't put that up in big red letters on the ActiveState site, eh?
Since Apache and mod_perl have server-side debugging facilities
(admittedly a little crude, and a little hard to get working under
Win32, though it can be done), you might like to consider this in
planning which server to deploy.
I would also like to mention that under Win2000, IIS5 has bluescreened
the OS twice on me during casual development, and has on several
occasions 'come over all strange,like', requiring a reboot to cure the
problem - stopping and starting the IIS server doesn't fix the problem.
On the other hand, Apache on NT, despite being described by the Apache
people as beta software, has never once malfunctioned in any way
whatsoever, nor have I ever encountered anything that could be
construed as a bug. In any event, stopping and restarting Apache can
easily be done without a server reboot - I know that IIS theoretically
allows this but experience shows that some stuff appears to remain in
memory and a reboot is necessary to clear it out.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Mon, 02 Oct 2000 10:49:41 GMT
From: kily@my-deja.com
Subject: Add on
Message-Id: <8r9p84$b62$1@nnrp1.deja.com>
Hello,
I'm wondering for a script which can read a file
containing two columns seperated by unknown number of tabulation or
space, then delete the first column (which is a complete name of
unsers). The second column is the user-ID as: 008253A, 008256X,...etc.
I want script to be able to delete the first two charecters and
transform majuscule (A, X, B,...etc) to minuscules ones.
PS: I'm workong under Windows NT Server 4.
Thanks
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Mon, 02 Oct 2000 12:15:30 GMT
From: fsconzo@my-deja.com
Subject: Re: AppConfig
Message-Id: <8r9u8u$epv$1@nnrp1.deja.com>
OK - thanks, your suggestions helped!
Best Regards,
Frank Sconzo
In article <970353536.18302@iglou.com>,
Ted Zlatanov <tzz@iglou.com> wrote:
> In article <8r31k7$iv0$1@nnrp1.deja.com>, fsconzo@my-deja.com wrote:
> >Does anyone know what I am doing wrong?
>
> Sure!
>
> 1) use the -w flag to perl:
> #!/usr/local/bin/perl -w
>
> 2) use the strict pragma
> use strict;
>
> 3) import the argcount constants from AppConfig
> use AppConfig qw/:argcount/;
>
> 4) use Data::Dumper to see if things are OK, rather than writing your
own
> (possibly wrong) loops
> use Data::Dumper;
> ...
> print Dumper $config->groupcode();
>
> With (1) and (2), you would have had warnings about (3) and you would
have
> found the problem. Following these recommendations will make your
life much,
> much easier.
>
> (4) is my personal preference, as it is simpler and easier to see a
complex
> structure with Data::Dumper than doing it yourself, especially for
nested data
> structures.
>
> --
> Teodor Zlatanov <tzz@iglou.com>
> "Brevis oratio penetrat colos, longa potatio evacuat ciphos." -
Rabelais
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: 2 Oct 2000 08:21:06 GMT
From: vek@pharmnl.ohout.pharmapartners.nl (Villy Kruse)
Subject: Re: automatic email attachments
Message-Id: <slrn8tghbi.nek.vek@pharmnl.ohout.pharmapartners.nl>
On Sun, 1 Oct 2000 11:07:02 +0100, Dave <dave@marballs.co.uk> wrote:
>Thank you for your input. Another basic question I am afraid.
>
>I am using someone else's server who has perl installed. Can I assume they
>already have these modules on there commercial server because I surely would
>not be able to install new modules on my web space providers server. They
>say they have full cgi-bin support.
>
A good question you should ask this "someone else".
Villy
------------------------------
Date: Mon, 02 Oct 2000 04:33:16 GMT
From: mjd@plover.com (Mark-Jason Dominus)
Subject: Re: benefits of perl
Message-Id: <39d83553.6ed8$115@news.op.net>
Keywords: inculcate, lew, maximum, tic
In article <m31yy122ee.fsf@solo.david-steuber.com>,
David Steuber <nospam@david-steuber.com> wrote:
>http://dev.scriptics.com/
>
>If they get there server back up ;-). They make some grandiose claims
>wrt to Tcl vs Perl.
Yeah, they say
...though it is possible in principle to extend Perl, it is
rarely done in practice.
which I think can be accurately characterized as a big fat lie.
------------------------------
Date: Mon, 2 Oct 2000 21:36:29 +1100
From: mgjv@tradingpost.com.au (Martien Verbruggen)
Subject: Re: benefits of perl
Message-Id: <slrn8tgp9d.jr6.mgjv@martien.heliotrope.home>
On Mon, 02 Oct 2000 04:33:16 GMT,
Mark-Jason Dominus <mjd@plover.com> wrote:
> In article <m31yy122ee.fsf@solo.david-steuber.com>,
> David Steuber <nospam@david-steuber.com> wrote:
> >http://dev.scriptics.com/
> >
> >If they get there server back up ;-). They make some grandiose claims
> >wrt to Tcl vs Perl.
>
>
> Yeah, they say
>
> ...though it is possible in principle to extend Perl, it is
> rarely done in practice.
>
> which I think can be accurately characterized as a big fat lie.
Oh, come on... You're not going to say that CPAN is worth mentioning,
are you? Everyone knows that CTclAN is much, much larger.
Martien
PS. For the sarcasm-impaired: ;)
--
Martien Verbruggen |
Interactive Media Division | I took an IQ test and the results
Commercial Dynamics Pty. Ltd. | were negative.
NSW, Australia |
------------------------------
Date: Mon, 2 Oct 2000 11:36:06 +0200
From: "Philipp Schill" <philipp.schill@t-online.de>
Subject: CGI.pm / saving records
Message-Id: <8r9kri$cjo$11$1@news.t-online.com>
hi,
i read in "perl in a nutshell" that it's possible to save data temporarely
with CGI.pm. but it's not described how it does. can you help me ?
thanks
phil
------------------------------
Date: Mon, 2 Oct 2000 12:27:49 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: CGI.pm / saving records
Message-Id: <Pine.GHP.4.21.0010021210390.25668-100000@hpplus03.cern.ch>
On Mon, 2 Oct 2000, Philipp Schill wrote:
> i read in "perl in a nutshell" that it's possible to save data temporarely
> with CGI.pm. but it's not described how it does. can you help me ?
I see that you posted this same question separately to
comp.lang.perl.misc. Don't do that. [now x-posted and f'ups set]
Read your usenet new users guide to understand why this is wrong
(presumably de.newusers.infos would be good for that in your case).
Now, about your question, which is not entirely clear.
Look at http://stein.cshl.org/WWW/software/CGI/ , in particular
the section http://stein.cshl.org/WWW/software/CGI/#saving
Are any of these options the answer to your question?
------------------------------
Date: Mon, 2 Oct 2000 12:48:54 +0200
From: Anders Lund <anders@wall.alweb.dk>
Subject: Re: CGI.pm / saving records
Message-Id: <rLZB5.1561$Qu1.139525@news000.worldonline.dk>
Philipp Schill wrote:
> hi,
>
> i read in "perl in a nutshell" that it's possible to save data temporarely
> with CGI.pm. but it's not described how it does. can you help me ?
>
> thanks
>
> phil
>
>
perldoc CGI
using less, you can search for the word "save" (case independant) by typing
"/save<return>", press n to go to next instance...
-anders
--
[ the word wall - and the trailing dot - in my email address
is my _fire_wall - protecting me from the criminals abusing usenet]
------------------------------
Date: Mon, 02 Oct 2000 08:15:51 -0400
From: brian d foy <brian+usenet@smithrenaud.com>
Subject: Re: CGI.pm / saving records
Message-Id: <brian+usenet-2E9AF1.08155102102000@news.panix.com>
In article <8r9kri$cjo$11$1@news.t-online.com>, "Philipp Schill"
<philipp.schill@t-online.de> wrote:
> i read in "perl in a nutshell" that it's possible to save data temporarely
> with CGI.pm. but it's not described how it does. can you help me ?
see the CGI.pm documentation.
--
brian d foy
Perl Mongers <URL:http://www.perl.org>
CGI Meta FAQ <URL:http://www.smithrenaud.com/public/CGI_MetaFAQ.html>
------------------------------
Date: Mon, 02 Oct 2000 07:39:09 GMT
From: kellymartin@my-deja.com
Subject: DBI.pm for MySQL & Perl 5
Message-Id: <8r9e2t$3lq$1@nnrp1.deja.com>
It appears that I need to install DBI.pm in order to get my Perl5
talking with the MySQL database for my web-based discussion forum. Both
of these (perl & mysql) are working properly, and I installed them
using RPM binaries for my linux machine.
Here is the problem: I have found the proper DBI-1.13.tar.gz but I do
not know how to compile this program. I am essentially a newbie, though
I have learned a great deal in the past while (setting up a firewall,
samba, dhcp, etc.)
Reason: the 'make' command does not exist on my system *at all* and so
I thought maybe I just didn't have 'gcc' installed... so I spent much
time installing that package along with a whole bunch of others that
were dependencies. It took forever to download. And still no 'make'!!
Can someone please help me? Ideally, if you could send me a DBI.pm
binary for i386 linux and tell me where to put it (assuming that I only
need one file).
My email address is kelm@NOSPAM.home.com (remove the 'NOSPAM'). If you
reply here can you please mail me a copy too?
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: Mon, 2 Oct 2000 11:14:31 +0200
From: Anders Lund <anders@wall.alweb.dk>
Subject: Re: DBI.pm for MySQL & Perl 5
Message-Id: <YmYB5.1549$Qu1.137482@news000.worldonline.dk>
kellymartin@my-deja.com wrote:
> It appears that I need to install DBI.pm in order to get my Perl5
> talking with the MySQL database for my web-based discussion forum. Both
> of these (perl & mysql) are working properly, and I installed them
> using RPM binaries for my linux machine.
>
> Here is the problem: I have found the proper DBI-1.13.tar.gz but I do
> not know how to compile this program. I am essentially a newbie, though
> I have learned a great deal in the past while (setting up a firewall,
> samba, dhcp, etc.)
>
> Reason: the 'make' command does not exist on my system *at all* and so
> I thought maybe I just didn't have 'gcc' installed... so I spent much
> time installing that package along with a whole bunch of others that
> were dependencies. It took forever to download. And still no 'make'!!
>
> Can someone please help me? Ideally, if you could send me a DBI.pm
> binary for i386 linux and tell me where to put it (assuming that I only
> need one file).
>
> My email address is kelm@NOSPAM.home.com (remove the 'NOSPAM'). If you
> reply here can you please mail me a copy too?
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Go to http://rpmfind.net and see if there is a rpm for it from the same
source that your perl came from (your dist?).
On my Mandrake system, the package is perl-DBI-1.13-2mdk.rpm (it's perl 5.6)
-anders
--
[ the word wall - and the trailing dot - in my email address
is my _fire_wall - protecting me from the criminals abusing usenet]
------------------------------
Date: 2 Oct 2000 07:18:25 GMT
From: daniel@chetlin.com (Daniel Chetlin)
Subject: Re: die() ignores tied STDERR?
Message-Id: <8r9cs1060i@news2.newsguy.com>
On Mon, 2 Oct 2000 16:09:14 +1100,
Martien Verbruggen <mgjv@tradingpost.com.au> wrote:
>Can I ask WHY you are doing all this? The code above obviously can't be
>your ultimate goal, because it doesn't add anything. If all you want to
>do is redirect STDERR output to a file, then:
>
>open(STDERR, ">/tmp/stderr") or die $!;
>
>will do that. If you want it redirected to STDOU, you can do that as
>well. If you want formatted output to STDOUT, then use CGI::Carp or
>something like that.
>
>If you do that, then the output of a die will nicely follow.
>
>I don't know what die internally cals, but redirecting the whole STDERR,
>instead of trying to do this with tied filehandles doesn't care :)
While I agree with you that I don't think the OP is seeing all of his
options, I'm actually thinking that this is a bug.
C<die> seems to obey wherever STDERR goes in other instances:
[~] $ perl -wle'open F,">/tmp/foo" or die "$!";*STDERR=*F;die "Help!"'
[~] $ cat /tmp/foo
Help! at -e line 1.
And there's certainly no problem in C<tie>-ing STDERR:
[~] $ perl -wle'sub TIEHANDLE {bless {}} sub PRINT {print "tied"}
tie *STDERR,"main"; print STDERR "untied"'
tied
So why aren't C<warn> or C<die> following a C<tie>-ed STDERR?
[~] $ perl -wle'sub TIEHANDLE {bless{}} sub PRINT {print "tied"}
tie *STDERR,"main"; warn "untied"'
untied at -e line 1.
And if I haven't convinced you yet, take a look at this:
[~] $ perl -wle'sub TIEHANDLE {bless{}} sub PRINT {print "tied"}
tie *F,"main"; *STDERR = *F; print STDERR "untied"'
Segmentation fault (core dumped)
(This only happens in 5.6 and later, 5.5 does the "right" thing and says
`Filehandle main::STDERR never opened at -e line 1.')
There are actually two or possibly three things here that I think are
probably bugs. I'm in the process of playing with a couple of them, but
I'm interested in your thoughts on if I'm right or not.
Thanks!
-dlc
------------------------------
Date: Mon, 2 Oct 2000 21:33:56 +1100
From: mgjv@tradingpost.com.au (Martien Verbruggen)
Subject: Re: die() ignores tied STDERR?
Message-Id: <slrn8tgp4k.jr6.mgjv@martien.heliotrope.home>
On 2 Oct 2000 07:18:25 GMT,
Daniel Chetlin <daniel@chetlin.com> wrote:
> On Mon, 2 Oct 2000 16:09:14 +1100,
> Martien Verbruggen <mgjv@tradingpost.com.au> wrote:
> >Can I ask WHY you are doing all this? The code above obviously can't be
> >your ultimate goal, because it doesn't add anything. If all you want to
> >do is redirect STDERR output to a file, then:
> >
> >open(STDERR, ">/tmp/stderr") or die $!;
> >
> >will do that. If you want it redirected to STDOU, you can do that as
> >well. If you want formatted output to STDOUT, then use CGI::Carp or
> >something like that.
> >
> >If you do that, then the output of a die will nicely follow.
> >
> >I don't know what die internally cals, but redirecting the whole STDERR,
> >instead of trying to do this with tied filehandles doesn't care :)
>
> While I agree with you that I don't think the OP is seeing all of his
> options, I'm actually thinking that this is a bug.
>
> C<die> seems to obey wherever STDERR goes in other instances:
>
> [~] $ perl -wle'open F,">/tmp/foo" or die "$!";*STDERR=*F;die "Help!"'
> [~] $ cat /tmp/foo
> Help! at -e line 1.
Yes. But redirecting STDERR isn't the same as tie-ing STDERR. One
happens at a very low level (system level, I believe that you are
actually working with the system calls), while the other happens at
some much higher level in perl. Calls to print, write and printf are
caught for these filehandles, and control is passed to a sub. With an
open(STDERR, ">file") the file descriptors get changed around, and that
includes perl's own stderr.
> And there's certainly no problem in C<tie>-ing STDERR:
>
> [~] $ perl -wle'sub TIEHANDLE {bless {}} sub PRINT {print "tied"}
> tie *STDERR,"main"; print STDERR "untied"'
> tied
Agreed. I tested that as well.
> So why aren't C<warn> or C<die> following a C<tie>-ed STDERR?
>
> [~] $ perl -wle'sub TIEHANDLE {bless{}} sub PRINT {print "tied"}
> tie *STDERR,"main"; warn "untied"'
> untied at -e line 1.
Possibly because warn and die use perl's internal stderr, or more
directly, the file descriptor that goes with it. warn and die are not
implemented as Perl code, but are part of perl's internals, and
therefore don't need to pass their control through the Perl STDERR
filehandle, but can directly work with the stderr or file descriptor 2.
i don't _know_ that this is what is happening, but I can easily see that
there is a potential large difference between STDERR and the channels
warn and die use. Maybe there shouldn't be, but that's for the perl
developers to decide.
> And if I haven't convinced you yet, take a look at this:
>
> [~] $ perl -wle'sub TIEHANDLE {bless{}} sub PRINT {print "tied"}
> tie *F,"main"; *STDERR = *F; print STDERR "untied"'
> Segmentation fault (core dumped)
>
> (This only happens in 5.6 and later, 5.5 does the "right" thing and says
> `Filehandle main::STDERR never opened at -e line 1.')
That last one looks like a bug. perl should never segfault. 5.004_05
acts the same as 5.005_03.
Whether or not all of the above is intended behaviour is hard to say.
I've tried to second-guess in the past what intended behaviour is with
Perl, and have as often as not been totally wrong :)
> There are actually two or possibly three things here that I think are
> probably bugs. I'm in the process of playing with a couple of them, but
> I'm interested in your thoughts on if I'm right or not.
Let me just see what I can find in the documentation..
# perldoc -f warn
warn LIST
Produces a message on STDERR just like `die', but
doesn't exit or throw an exception.
# perldoc -f die
die LIST
Outside an `eval', prints the value of LIST to
`STDERR' and exits with the current value of `$!'
(errno).
Both _explicitly_ mentione STDERR, and don't use something vague like
'standard error output' or some such thing. If the documentation can be
taken to reflect the intention, than this misbehaviour is certainly a
bug.
However, if it's broken, it has been broken at least since version
5.004_05, for which warn and die output also bypasses a tied STDERR.
You could try submitting a bug report. If nothing else, it should get
people to decide whether this is 'correct' behaviour or not.
Martien
--
Martien Verbruggen |
Interactive Media Division | In the fight between you and the
Commercial Dynamics Pty. Ltd. | world, back the world - Franz Kafka
NSW, Australia |
------------------------------
Date: Mon, 02 Oct 2000 07:39:32 GMT
From: rgarciasuarez@free.fr (Rafael Garcia-Suarez)
Subject: Re: Executing a program from a CGI
Message-Id: <slrn8tgfaa.p25.rgarciasuarez@rafael.kazibao.net>
Scott Dellar wrote in comp.lang.perl.misc:
>Hey there,
>I am trying to execute either (preferably both of) postgres or pg_dump from
>within a CGI. I am doing this so I can back up and restore a postgres
>database - with a single click from the Internet.
>The commands are:
>'pg_dump groupa00 > backup.txt' (for backing up to a text file)
>'psql -e groupa00 < backup.txt' (for getting the data back from the text
>file)
>If you can help with the execution of either of these programs it would make
>my day.
If your CGI program does not perform much more tasks than those actions,
why don't you write it as a shell script instead of a perl script?
BTW, you're looking for the perl system() function. At the prompt:
perldoc -f system
--
# Rafael Garcia-Suarez / http://rgarciasuarez.free.fr/
------------------------------
Date: Mon, 2 Oct 2000 00:38:28 -0700
From: Larry Rosler <lr@hpl.hp.com>
Subject: Re: File upload testing if it's there
Message-Id: <MPG.1441db4a297d70f498ade8@nntp.hpl.hp.com>
In article <8r7uvl$uu$1@nnrp1.deja.com>, jim_marshall2268@hotmail.com
says...
> O well - live and learn. I was trying to reduce the clutter in the
> post, obviously this is not the right thing to do in this newsgroup.
You have drawn the wrong conclusion.
Trying to cut away irrelevancies bfore posting is an excellent idea.
But you must then test whatever you intend to post, to be sure that at
least it compiles. Otherwise no one will pay attention, except to carp.
And often the original problem will clarify itself as part of this
process, so you won't have to post at all. That really helps to reduce
the clutter. :-)
--
(Just Another Larry) Rosler
Hewlett-Packard Laboratories
http://www.hpl.hp.com/personal/Larry_Rosler/
lr@hpl.hp.com
------------------------------
Date: 2 Oct 2000 07:21:00 GMT
From: daniel@chetlin.com (Daniel Chetlin)
Subject: Re: How to detect modules currently in use?
Message-Id: <8r9d0s160i@news2.newsguy.com>
On Mon, 2 Oct 2000 12:01:02 +1100,
Martien Verbruggen <mgjv@tradingpost.com.au> wrote:
>On 1 Oct 2000 23:30:38 GMT,
> Daniel Chetlin <daniel@chetlin.com> wrote:
>> require $filename unless exists $INC{$filename};
>
>I suspect you already know this, but just to make it clear to anyone
>else reading this thread: require already does this checking for you.
>There is no need to check whether a module is already loaded before
>loading it.
You're right in pointing this out. I had a bit of tunnel vision when
making my post -- I answered the exact question without looking around
to see if the wrong question was being asked.
>That's what I'd do. Simply use or require the module wherever you need
>it, and let perl worry about whether or not it has already been loaded.
Quite.
-dlc
------------------------------
Date: Mon, 02 Oct 2000 12:38:40 GMT
From: Brendon Caligari <bcaligari@my-deja.com>
Subject: Re: How to get length of scalar?
Message-Id: <8r9vkg$fnj$1@nnrp1.deja.com>
In article <slrn8tg8dc.e2u.dha@panix6.panix.com>,
dha@panix.com (David H. Adler) wrote:
> On Sun, 01 Oct 2000 19:03:48 GMT, David Steuber
> <nospam@david-steuber.com> wrote:
>
> >As for on-topic posts, I've tried to post to comp.lang.perl and
> >cross-post to comp.lang.perl.misc (or modules) as clp has less
traffic
> >than clpm.
>
> There's a reason for this. Said reason is that c.l.p *no longer
> exists* (cf. Crazy Vaclav, some simpsons episode that I can't be
> bothered to look up the code for...)
>
> >Perhaps that alt.perl group I see in the headers could be used for
the
> >off topic rants?
>
> By definition, off-topic rants should not appear in *any*
> newsgroup... :-) (1/2).
>
> dha
In the good old days of BBSes we had a lot of technical forums.
Most threads used to decay into lame conversations, and being
a closely knit community (I live on an island) messages such
as "managed to crack problem such and such...where are we
going for a binge?" were not uncommon. We had a board set
up specifically for transferrign such threads.....conveniently
named "Idle chatter". Something like alt.perl.culture would
be nice... <sigh>
* Brendon *
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Date: 2 Oct 2000 10:30:23 -0000
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Huh?
Message-Id: <8r9o3v$5uo$1@lublin.zrz.tu-berlin.de>
Jeff Zucker <jeff@vpservices.com> wrote in comp.lang.perl.misc:
>P.S. Gene: the French dude was just having trouble executing his
>scripts. If it had been anything more general, I would have translated.
So what's more general than having trouble executing your scripts?
Anno
------------------------------
Date: Mon, 02 Oct 2000 12:27:50 GMT
From: Jim Mauldin <mauldin@netstorm.net>
Subject: Re: Huh?
Message-Id: <39D87F06.EE919E8D@netstorm.net>
Anno Siegel wrote:
>
> Jeff Zucker <jeff@vpservices.com> wrote in comp.lang.perl.misc:
>
> >P.S. Gene: the French dude was just having trouble executing his
> >scripts. If it had been anything more general, I would have translated.
>
> So what's more general than having trouble executing your scripts?
>
> Anno
The OP wrote:
>
> Bonjour,
> J'essaie en vain d'appeler un fichier perl sur mon cgi-bin
> J'ai vérifier les CHMOD, l'emplacement #!usr/bin/perl.
> Comment faire ?
This means:
Hello,
I'm trying in vain to execute a perl file in my cgi-bin
I've checked the CHMODs, the location of #!usr/bin/perl.
How can I get it to work?
-- Jim
------------------------------
Date: Mon, 02 Oct 2000 11:05:50 GMT
From: Bart Lateur <bart.lateur@skynet.be>
Subject: Re: Inserting HTML into CGI script as if it was beinging #NCLUDEd via SSI
Message-Id: <4tqgtsgeh2272v8tfh46f32m5n3vonjthc@4ax.com>
Mick Beeby wrote:
>How can I open this file from within a CGI script and read the
>contents and write them to the browser screen as if the file had been
>#INCLUDEd using SSI.
It sounds as if you want to use a template mechanism. I don't of any SSI
compatible template modules, but you can check out CPAN
(<http://search.cpan.org/> yourself.
Otherwise, read in the HTML file sections into your program, and a
simple
s/($pattern)/$insert{$1}/g;
will do, after which you can print out the result.
--
Bart.
------------------------------
Date: 2 Oct 2000 09:21:11 GMT
From: =?iso-8859-1?Q?=B0=AA=B7=D8=A9=FA?= <proton@iiidns.iii.org.tw>
Subject: Install problem on SCO
Message-Id: <39D853AE.7CA8383D@iiidns.iii.org.tw>
This is a multi-part message in MIME format.
--------------AAC71EA0289AF1A4E9961E93
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I always encounter the following problem when installation,
Undefined first referenced
symbol in file
Perl_safesysmalloc opmini.o
Perl_safesysrealloc opmini.o
Perl_call_sv opmini.o
Perl_get_cv opmini.o
Perl_safesysfree opmini.o
miniperl: fatal error: Symbol referencing errors. No output written to
miniperl
*** Error code 1 (bu21)
What I miss when installing??
Thanks a lot for your help!!
-----------------------------------------------------------
Brad, Huan-Ming Kao (Institute for Information Industry)
--------------AAC71EA0289AF1A4E9961E93
Content-Type: text/plain; charset=us-ascii;
name="myconfig"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="myconfig"
#!/bin/sh
# This script is designed to provide a handy summary of the configuration
# information being used to build perl. This is especially useful if you
# are requesting help from comp.lang.perl.misc on usenet or via mail.
# Note that the text lines /^Summary of/ .. /^\s*$/ are copied into Config.pm.
cat <<'!NO!SUBS!'
Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
Platform:
osname=sco, osvers=3.2v5.0.5, archname=i386-sco
uname='sco_sv www 3.2 5.0.5 i386 '
config_args=''
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
Compiler:
cc='cc', optimize='-O0', gccversion=
cppflags='-U M_XENIX -D PERL_SCO -D PERL_SCO5 -w0 -belf -I/usr/local/include'
ccflags ='-U M_XENIX -D PERL_SCO -D PERL_SCO5 -w0 -belf -I/usr/local/include'
stdchar='unsigned char', d_stdstdio=undef, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=undef, longlongsize=, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
alignbytes=4, usemymalloc=y, prototype=define
Linker and Libraries:
ld='ld', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib
libs=-lintl -lsocket -lnsl -lndbm -ldbm -lld -lm -lc -lcrypt -lsec -lPW -lx
libc=, so=so, useshrplib=true, libperl=libperl.so
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Bexport -L/usr/local/lib'
cccdlflags='-Kpic', lddlflags='-G -L/usr/local/lib'
!NO!SUBS!
--------------AAC71EA0289AF1A4E9961E93--
------------------------------
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 V9 Issue 4488
**************************************
