[28639] in Perl-Users-Digest
Perl-Users Digest, Issue: 10003 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 24 18:06:07 2006
Date: Fri, 24 Nov 2006 15:05:13 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 24 Nov 2006 Volume: 10 Number: 10003
Today's topics:
a short non-working Perl script <dr.mtarver@ukonline.co.uk>
Re: a short non-working Perl script <tbmoore9@verizon.net>
Re: a short non-working Perl script <mritty@gmail.com>
Re: a short non-working Perl script <spamtrap@dot-app.org>
Re: a short non-working Perl script <john@castleamber.com>
Re: a short non-working Perl script <dr.mtarver@ukonline.co.uk>
Re: a short non-working Perl script <spamtrap@dot-app.org>
Re: a short non-working Perl script krakle@visto.com
Re: a short non-working Perl script <glennj@ncf.ca>
Re: a short non-working Perl script <tony_curtis32@yahoo.com>
Re: a short non-working Perl script <wahab@chemie.uni-halle.de>
Re: a short non-working Perl script <jurgenex@hotmail.com>
Re: a short non-working Perl script <john@castleamber.com>
Re: a short non-working Perl script <wahab@chemie.uni-halle.de>
Re: a short non-working Perl script <tadmc@augustmail.com>
Re: a short non-working Perl script <tadmc@augustmail.com>
Re: ANNOUNCE: CGI::ContactForm 1.40 krakle@visto.com
Re: ANNOUNCE: CGI::ContactForm 1.40 <noreply@gunnar.cc>
Re: ANNOUNCE: CGI::ContactForm 1.40 (reading news)
Re: ANNOUNCE: CGI::ContactForm 1.40 <antispam@randometry.com>
Re: ANNOUNCE: CGI::ContactForm 1.40 <bik.mido@tiscalinet.it>
Re: ANNOUNCE: CGI::ContactForm 1.40 <tadmc@augustmail.com>
die on "use of uninitialized value"? ivowel@gmail.com
Re: die on "use of uninitialized value"? <DJStunks@gmail.com>
Re: die on "use of uninitialized value"? <bik.mido@tiscalinet.it>
Re: die on "use of uninitialized value"? <bik.mido@tiscalinet.it>
Re: die on "use of uninitialized value"? <DJStunks@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 24 Nov 2006 07:39:51 -0800
From: "Mark Tarver" <dr.mtarver@ukonline.co.uk>
Subject: a short non-working Perl script
Message-Id: <1164382791.012844.218560@j72g2000cwa.googlegroups.com>
I'm writing my first significant Perl CGI script. Its supposed to read
in the input from two forms and print them on the screen. The preamble
seems to work fine - takes the input string and spilts it into the
component tokens. The print HTML bit does not work fine. What
appears on the browser
is:
Info
--------------------------------------------------------------------------------
Name:
Email:
with neither values of name or email displayed. Why is this?
A minor niggle - Perl does not seem to match END_OF_PART2 unless I
place the redundant print statement at the bottom. No idea why.
Mark
# Here is the Code
#!/usr/bin/perl
# Reads the input from a forms file and splits it into parts.
$buffer = read(STDIN, $buffer, $ENV{'CONTENT_LENGTH'});
$token = "";
@tokens = ( );
while ($buffer ne "")
{$c = chop($buffer);
if ($c eq "&" || $c eq "=")
{$tokens = push(@tokens, $token); $token = "";}
else
{$token = $c . $token;}
};
push(@tokens, $token);
@tokens = reverse(@tokens);
# Grabs name and email.
shift(@tokens);
$name = shift(@tokens);
shift(@tokens);
$email = shift(@tokens);
#__________________________HTML begins here
print <<END_OF_PART1;
Content-type: text/html
<HTML>
<HEAD>
<TITLE> Info</TITLE>
</HEAD>
<BODY>
<H1> Info</H1>
<HR>
<PRE>
END_OF_PART1
print "Name: $name <br>";
print "Email: $email <br>" ;
print <<END_OF_PART2;
</PRE>
<HR>
</BODY>
</HTML>
END_OF_PART2
print "";
------------------------------
Date: Fri, 24 Nov 2006 15:58:11 GMT
From: boyd <tbmoore9@verizon.net>
Subject: Re: a short non-working Perl script
Message-Id: <tbmoore9-86BE83.10581024112006@news.verizon.net>
In article <1164382791.012844.218560@j72g2000cwa.googlegroups.com>,
"Mark Tarver" <dr.mtarver@ukonline.co.uk> wrote:
>
> $buffer = read(STDIN, $buffer, $ENV{'CONTENT_LENGTH'});
> $token = "";
> @tokens = ( );
>
Well, this is not what you want. From perldoc -f read:
Attempts to read LENGTH characters of data into variable SCALAR from
the specified FILEHANDLE. Returns the number of characters actually
read...
You are overwriting the $buffer contents with the number of characters.
Boyd
------------------------------
Date: 24 Nov 2006 08:18:08 -0800
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: a short non-working Perl script
Message-Id: <1164385088.843053.84470@l39g2000cwd.googlegroups.com>
Mark Tarver wrote:
> I'm writing my first significant Perl CGI script.
Then now is the perfect time to trash whatever book or website has
taught you such horrendous coding methods. Please read:
perldoc CGI
and learn the *right* way to write a CGI script in Perl.
> Its supposed to read
> in the input from two forms and print them on the screen. The preamble
> seems to work fine - takes the input string and spilts it into the
> component tokens. The print HTML bit does not work fine. What
> appears on the browser
> is:
>
> Info
>
> --------------------------------------------------------------------------------
>
> Name:
> Email:
>
> with neither values of name or email displayed. Why is this?
>
> A minor niggle - Perl does not seem to match END_OF_PART2 unless I
> place the redundant print statement at the bottom. No idea why.
Probably because you're not using a HEREDOC correctly. It must be the
only thing on the line, and it must be terminated with a newline. My
guess is you added an extra line using print "", but a blank line would
have "fixed" it just as well.
> # Here is the Code
>
> #!/usr/bin/perl
You've neglected:
use strict;
use warnings;
use CGI qw/:standard/;
use CGI::Carp qw/fatalsToBrowser/;
Those four should be in EVERY Perl CGI script you write. The first two
should be in EVERY Perl script you write.
> # Reads the input from a forms file and splits it into parts.
>
> $buffer = read(STDIN, $buffer, $ENV{'CONTENT_LENGTH'});
> $token = "";
> @tokens = ( );
>
> while ($buffer ne "")
> {$c = chop($buffer);
> if ($c eq "&" || $c eq "=")
> {$tokens = push(@tokens, $token); $token = "";}
> else
> {$token = $c . $token;}
> };
> push(@tokens, $token);
> @tokens = reverse(@tokens);
>
> # Grabs name and email.
>
> shift(@tokens);
> $name = shift(@tokens);
> shift(@tokens);
> $email = shift(@tokens);
Get rid of this entire mess. Everything from my last comment to this
one. Replace it ALL with these two lines:
my $name = param('name');
my $email = param('email');
(presuming, of course, that you did in fact name your inputs 'name' and
'email', respectively.
>
> #__________________________HTML begins here
> print <<END_OF_PART1;
> Content-type: text/html
>
> <HTML>
> <HEAD>
> <TITLE> Info</TITLE>
> </HEAD>
> <BODY>
Get rid of this entire mess and replace with:
print header();
print start_html('Info');
> <H1> Info</H1>
> <HR>
> <PRE>
> END_OF_PART1
> print "Name: $name <br>";
> print "Email: $email <br>" ;
> print <<END_OF_PART2;
>
> </PRE>
> <HR>
print h1('Info');
print hr();
print pre("Name: $name<br>\nEmail: $email<br>\n");
> </BODY>
> </HTML>
print end_html();
> END_OF_PART2
> print "";
Learning to code the correct way now will save you endless frustrations
as you write more complex scripts in the future.
Paul Lalli
------------------------------
Date: Fri, 24 Nov 2006 11:40:47 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: a short non-working Perl script
Message-Id: <m2ejrsbxww.fsf@Sherm-Pendleys-Computer.local>
"Mark Tarver" <dr.mtarver@ukonline.co.uk> writes:
> I'm writing my first significant Perl CGI script. Its supposed to read
> in the input from two forms and print them on the screen. The preamble
> seems to work fine - takes the input string and spilts it into the
> component tokens.
Reinventing the wheel is most certainly *not* fine. Use the standard CGI
module to parse form input - that's what it's there for.
> The print HTML bit does not work fine. What
> appears on the browser
> is:
>
> Info
>
> --------------------------------------------------------------------------------
>
> Name:
> Email:
>
> with neither values of name or email displayed. Why is this?
I'd guess that there's a bug in your reinvented wheel. Sorry, but I have
little interest in debugging it, aside from repeating the above advice -
use CGI.pm. It's the standard, and it works.
> A minor niggle - Perl does not seem to match END_OF_PART2 unless I
> place the redundant print statement at the bottom. No idea why.
Perl's "here docs" break if the delimiter is on the last line of the file,
and that line doesn't end with a \n. (Or \r\n, or whatever your OS's idea
of an end-of-line sequence is.)
Adding any statement after the second END_OF_PART2, or even just ending
that line with an EOL sequence, would work just as well. Most programmer's
editors have an option to add an EOL to the last line automatically when
a file is saved.
sherm--
--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
------------------------------
Date: 24 Nov 2006 17:35:43 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: a short non-working Perl script
Message-Id: <Xns988575F42AA6Fcastleamber@130.133.1.4>
Sherm Pendley <spamtrap@dot-app.org> wrote:
> Adding any statement after the second END_OF_PART2, or even just
> ending that line with an EOL sequence, would work just as well. Most
> programmer's editors have an option to add an EOL to the last line
> automatically when a file is saved.
And trimming trailing spaces (and tabs), which is another way to make here
docs fail (having whitespace other then EOL after the marker)
--
John Experienced Perl programmer: http://castleamber.com/
Perl help, tutorials, and examples: http://johnbokma.com/perl/
------------------------------
Date: 24 Nov 2006 10:00:19 -0800
From: "Mark Tarver" <dr.mtarver@ukonline.co.uk>
Subject: Re: a short non-working Perl script
Message-Id: <1164391219.159933.181570@14g2000cws.googlegroups.com>
Ah ,much clearer, thanks.
Mark
P.S. what is the significance of 'my' in the code?
------------------------------
Date: Fri, 24 Nov 2006 14:05:32 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: a short non-working Perl script
Message-Id: <m2wt5kacn7.fsf@Sherm-Pendleys-Computer.local>
"Mark Tarver" <dr.mtarver@ukonline.co.uk> writes:
> Ah ,much clearer, thanks.
*What* is much clearer?
> P.S. what is the significance of 'my' in the code?
*What* code?
Please - quote enough of the messages you're responding to, for your own
message to make sense. Have you read the group guidelines that are posted
here frequently?
sherm--
--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
------------------------------
Date: 24 Nov 2006 11:30:52 -0800
From: krakle@visto.com
Subject: Re: a short non-working Perl script
Message-Id: <1164396652.442110.15230@m7g2000cwm.googlegroups.com>
On Nov 24, 10:18 am, "Paul Lalli" <mri...@gmail.com> wrote:
> > #__________________________HTML begins here
> > print <<END_OF_PART1;
> > Content-type: text/html
>
> > <HTML>
> > <HEAD>
> > <TITLE> Info</TITLE>
> > </HEAD>
> > <BODY>Get rid of this entire mess and replace with:
> print header();
> print start_html('Info');
>
> > <H1> Info</H1>
> > <HR>
> > <PRE>
> > END_OF_PART1
> > print "Name: $name <br>";
> > print "Email: $email <br>" ;
> > print <<END_OF_PART2;
>
> > </PRE>
> > <HR>print h1('Info');
> print hr();
> print pre("Name: $name<br>\nEmail: $email<br>\n");
>
> > </BODY>
> > </HTML>print end_html();
>
> > END_OF_PART2
His way of outputting HTML to the browser is better than your
suggestion of using CGI.pm to display HTML. Since when does programming
on top of an additional layer of abstraction better than dealing with
the markup language directly?
Nobody who makes a serious Perl script for the web uses CGI.pm to write
HTML. It's just far too limiting and makes it virtually impossible to
easily update..
------------------------------
Date: 24 Nov 2006 19:45:07 GMT
From: Glenn Jackman <glennj@ncf.ca>
Subject: Re: a short non-working Perl script
Message-Id: <slrnemeiu3.df8.glennj@smeagol.ncf.ca>
At 2006-11-24 02:30PM, "krakle@visto.com" wrote:
> Nobody who makes a serious Perl script for the web uses CGI.pm to write
> HTML. It's just far too limiting and makes it virtually impossible to
> easily update..
You can't be serious. TIMTOWTDI.
Nevertheless, my favourite is CGI + HTML::Template.
--
Glenn Jackman
Ulterior Designer
------------------------------
Date: Fri, 24 Nov 2006 15:02:19 -0500
From: Tony Curtis <tony_curtis32@yahoo.com>
Subject: Re: a short non-working Perl script
Message-Id: <ek7j4b$lq4$1@knot.queensu.ca>
krakle@visto.com wrote:
> His way of outputting HTML to the browser is better than your
> suggestion of using CGI.pm to display HTML. Since when does programming
> on top of an additional layer of abstraction better than dealing with
> the markup language directly?
Because HTML is a structured language. Just printing out the HTML
directly as text confuses (IMHO) the actual structure of the document,
with serialization for transmission to the client.
print html( head(...) . body(...) );
Using the abstraction layer afforded by a module allows you to write to
your purpose, not to the underlying implementation (HTML).
hth
t
------------------------------
Date: Fri, 24 Nov 2006 21:18:33 +0100
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: a short non-working Perl script
Message-Id: <ek7kbq$t8q$1@mlucom4.urz.uni-halle.de>
Thus spoke krakle@visto.com (on 2006-11-24 20:30):
> On Nov 24, 10:18 am, "Paul Lalli" <mri...@gmail.com> wrote:
>> > <BODY>Get rid of this entire mess and replace with:
>> print header();
>> print start_html('Info');
>
> His way of outputting HTML to the browser is better than your
> suggestion of using CGI.pm to display HTML. Since when does programming
> on top of an additional layer of abstraction better than dealing with
> the markup language directly?
Because you end up reinventing most of the
functionality of CGI.pm if you plan to do
'CGI level' work. If that's your objective,
fine.
> Nobody who makes a serious Perl script for the web uses CGI.pm to write
> HTML. It's just far too limiting and makes it virtually impossible to
> easily update..
True, but there are usually some steps
involved - when you climb your learning
curve.
Usually you start with 'heredocs' of html
and some simple perl code above, discovering
CGI.pm after this frustrating step. Then, you
divide your stuff into the Perl code and some
nice templates - in the end you will do
Mason or TT (depends on your view of the
whole process).
The interaction between the OP and Paul L.
was therefore 'close to perfect' ;-)
Regards
Mirco
------------------------------
Date: Fri, 24 Nov 2006 21:16:20 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: a short non-working Perl script
Message-Id: <EiJ9h.4683$_x3.255@trndny02>
> Thus spoke krakle@visto.com (on 2006-11-24 20:30):
>> Since when does
>> programming on top of an additional layer of abstraction better than
>> dealing with the markup language directly?
Hmmm. I am surprised that you are frequenting a Perl NG.
After all when taking this argument serious I would expect you to program in
binary code (aka machine code) using dip switches.
Don't use assembler, that's already a layer of abstraction!
jue
------------------------------
Date: 24 Nov 2006 21:30:10 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: a short non-working Perl script
Message-Id: <Xns98859DB3754B5castleamber@130.133.1.4>
krakle@visto.com wrote:
> His way of outputting HTML to the browser is better than your
> suggestion of using CGI.pm to display HTML.
Depends. But it's extremely important to note that CGI.pm spits out XHTML
(horror, surprise) unless that has been changed. Hence I never use it for
HTML generation :-D.
> Since when does programming
> on top of an additional layer of abstraction better than dealing with
> the markup language directly?
I can come up with several examples, and I am sure you as well.
> Nobody who makes a serious Perl script for the web uses CGI.pm to write
> HTML. It's just far too limiting and makes it virtually impossible to
> easily update..
Have you concluded this from serious research, or it's just how you would
like to see things? When is a Perl script serious?
--
John Experienced Perl programmer: http://castleamber.com/
Perl help, tutorials, and examples: http://johnbokma.com/perl/
------------------------------
Date: Fri, 24 Nov 2006 22:55:35 +0100
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: a short non-working Perl script
Message-Id: <ek7q1n$264$1@mlucom4.urz.uni-halle.de>
Thus spoke Jürgen Exner (on 2006-11-24 22:16):
>> Thus spoke krakle@visto.com (on 2006-11-24 20:30):
>>> Since when does
>>> programming on top of an additional layer of abstraction better than
>>> dealing with the markup language directly?
>
> After all when taking this argument serious I would expect you to program in
> binary code (aka machine code) using dip switches.
> Don't use assembler, that's already a layer of abstraction!
The funny thing is -- I actually *had* this argument
(many years ago) with a young scientist who started
molecular modelling (sort of) and didn't believe that
one could use C (instead of assembler) for writing
programs. A "perfect" machine code simulation program
would of course be "much better" - or wouldn't it? ;-)
(you only brought these memories up ...)
Regards
M.
------------------------------
Date: Fri, 24 Nov 2006 13:05:21 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: a short non-working Perl script
Message-Id: <slrnemegjh.7fl.tadmc@tadmc30.august.net>
Mark Tarver <dr.mtarver@ukonline.co.uk> wrote:
> P.S. what is the significance of 'my' in the code?
"Coping with Scoping":
http://perl.plover.com/FAQs/Namespaces.html
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 24 Nov 2006 16:29:33 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: a short non-working Perl script
Message-Id: <slrnemesid.8tv.tadmc@tadmc30.august.net>
John Bokma <john@castleamber.com> wrote:
> Pinocchio@visto.com wrote:
>> Nobody who makes a serious Perl script for the web uses CGI.pm to write
>> HTML.
> When is a Perl script serious?
Whenever it is not being executed.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 24 Nov 2006 11:34:11 -0800
From: krakle@visto.com
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <1164396851.742949.65020@h54g2000cwb.googlegroups.com>
On Nov 21, 6:04 pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
> CGI::ContactForm is a module for generating web contact forms. It lets
> you create an unlimited number of forms with a minimum of effort, and
> makes it possible for e.g. web hosting providers to offer their
> customers an easy way to set up a contact form.
>
> Version 1.40 includes a feature that makes automated submissions by spam
> robots more difficult, without the inconvenience of CAPTCHA. Also, since
> some people don't like that a copy is sent to the submitted sender
> address, an option has been added to not send sender copies.
>
> http://search.cpan.org/src/GUNNAR/CGI-ContactForm-1.40/readme.html
>
> Enjoy!
Gunnar you of all people should know that comp.lang.perl.misc isn't a
place to post announcements for crappy modules that noone will use...
------------------------------
Date: Fri, 24 Nov 2006 22:31:57 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <4sp6mhF10pgkjU1@mid.individual.net>
krakle@visto.com wrote:
> On Nov 21, 6:04 pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
>>CGI::ContactForm is a module for generating web contact forms. It lets
>>you create an unlimited number of forms with a minimum of effort, and
>>makes it possible for e.g. web hosting providers to offer their
>>customers an easy way to set up a contact form.
>>
>>Version 1.40 includes a feature that makes automated submissions by spam
>>robots more difficult, without the inconvenience of CAPTCHA. Also, since
>>some people don't like that a copy is sent to the submitted sender
>>address, an option has been added to not send sender copies.
>
> Gunnar you of all people should know that comp.lang.perl.misc isn't a
> place to post announcements for crappy modules that noone will use...
So you think it's crappy? Then I look forward to your insightsful code
criticism.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 24 Nov 2006 21:34:24 GMT
From: "Mumia W. (reading news)" <paduille.4060.mumia.w@earthlink.net>
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <AzJ9h.3478$1s6.1725@newsread2.news.pas.earthlink.net>
On 11/24/2006 01:34 PM, krakle@visto.com wrote:
>
> Gunnar you of all people should know [...]
troll
--
paduille.4060.mumia.w@earthlink.net
------------------------------
Date: Fri, 24 Nov 2006 23:03:17 +0100
From: Ric <antispam@randometry.com>
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <ek7q79$i2i$1@online.de>
Gunnar Hjalmarsson schrieb:
> krakle@visto.com wrote:
>> On Nov 21, 6:04 pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
>>> CGI::ContactForm is a module for generating web contact forms. It lets
>>> you create an unlimited number of forms with a minimum of effort, and
>>> makes it possible for e.g. web hosting providers to offer their
>>> customers an easy way to set up a contact form.
Woah, have you seen those powerful form designers for example from 1and1 ?
>>>
>>> Version 1.40 includes a feature that makes automated submissions by spam
>>> robots more difficult, without the inconvenience of CAPTCHA. Also, since
>>> some people don't like that a copy is sent to the submitted sender
>>> address, an option has been added to not send sender copies.
>>
>> Gunnar you of all people should know that comp.lang.perl.misc isn't a
>> place to post announcements for crappy modules that noone will use...
>
> So you think it's crappy? Then I look forward to your insightsful code
> criticism.
Well the first thing I had in mind ->I can tell Contact Form to setup a
form with certain fields that I name. But after having a quick look at
the source I saw that this is not possible *LOL*.
This .pm is a great beginners tutorial, but that's it:-)
>
------------------------------
Date: Fri, 24 Nov 2006 23:41:00 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <assem2h7jnl87susqrr0fhi1p9us7eok86@4ax.com>
On 24 Nov 2006 11:34:11 -0800, krakle@visto.com wrote:
>Gunnar you of all people should know that comp.lang.perl.misc isn't a
>place to post announcements for crappy modules that noone will use...
While I cannot comment on how crappy or not the announced module could
ever be, since I've not looked at it, and I'm not potentially
interested in it, I also strongly doubt that it is. But irrelevant of
how crappy or not it could be, I would amend your claim that clpmisc
is not a place to post announcements for modules at all, which makes
some sense because on the one hand that would raise the traffic, and
OTOH it would raise it too high. It would be better suited to
occasionally post about some(one's own) module if it were for a RFC or
if unsure about it, but that's only MHO...
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 24 Nov 2006 16:40:21 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: ANNOUNCE: CGI::ContactForm 1.40
Message-Id: <slrnemet6l.8tv.tadmc@tadmc30.august.net>
Mumia W. (reading news) <paduille.4060.mumia.w@earthlink.net> wrote:
> On 11/24/2006 01:34 PM, krakle@visto.com wrote:
>>
>> Gunnar you of all people should know [...]
>
>
> troll
... who has been dropping in here for years.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 24 Nov 2006 11:00:21 -0800
From: ivowel@gmail.com
Subject: die on "use of uninitialized value"?
Message-Id: <1164394821.116294.244510@m7g2000cwm.googlegroups.com>
dear perl experts: is it possible to instruct perl to die on run-time
if it accesses an undefined scalar ? I would rather know right away
when I have committed a programming error.
sincerely,
/iaw
------------------------------
Date: 24 Nov 2006 11:26:28 -0800
From: "DJ Stunks" <DJStunks@gmail.com>
Subject: Re: die on "use of uninitialized value"?
Message-Id: <1164396388.153215.39150@h54g2000cwb.googlegroups.com>
ivowel@gmail.com wrote:
> dear perl experts: is it possible to instruct perl to die on run-time
> if it accesses an undefined scalar ? I would rather know right away
> when I have committed a programming error.
use warnings FATAL => qw{ uninitialized };
-jp
------------------------------
Date: Fri, 24 Nov 2006 23:42:47 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: die on "use of uninitialized value"?
Message-Id: <j8tem2h2unld3qipde6tq34mm18sb9tk88@4ax.com>
On 24 Nov 2006 11:00:21 -0800, ivowel@gmail.com wrote:
>dear perl experts: is it possible to instruct perl to die on run-time
>if it accesses an undefined scalar ? I would rather know right away
>when I have committed a programming error.
Yes, but that would be rather strange since that particular warning is
probably the most common and reasonable one for which people
consciously wants to temporarily disable warnings.
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Fri, 24 Nov 2006 23:43:59 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: die on "use of uninitialized value"?
Message-Id: <hbtem2503063nc2ci8ckkiv77a85eil2i3@4ax.com>
On 24 Nov 2006 11:26:28 -0800, "DJ Stunks" <DJStunks@gmail.com> wrote:
> use warnings FATAL => qw{ uninitialized };
Whoa! I was thinking about writing a die handler myself. I didn't know
about this semantic. Thank you!!
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 24 Nov 2006 14:57:04 -0800
From: "DJ Stunks" <DJStunks@gmail.com>
Subject: Re: die on "use of uninitialized value"?
Message-Id: <1164409024.084873.30220@j72g2000cwa.googlegroups.com>
Michele Dondi wrote:
> On 24 Nov 2006 11:26:28 -0800, "DJ Stunks" <DJStunks@gmail.com> wrote:
>
> > use warnings FATAL => qw{ uninitialized };
>
> Whoa! I was thinking about writing a die handler myself. I didn't know
> about this semantic. Thank you!!
No problem. :-)
Another advantage of lexical warnings (people always ask...)
-jp
------------------------------
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 V10 Issue 10003
****************************************
