Re: Bareword errors?



On Nov 28, 6:23 pm, gcr <reviewyourd...@xxxxxxxxxxx> wrote:
There were also
big back and forths on the newsgroup by those more knowledgable than I
(that would be everyone) about the pluses and minuses of cgi.pm. I
haven't been burned *yet* by using the regexes and it's been in pretty
constant use for a while. I like to be able to control what is being
decoded for various reasons which I wasn't able to figure out in cgi.pm.
I've also fixed other peoples broken cgi's (again, linebreak issues) by
taking cgi.pm out and using regexes. YMMV.

What makes Perl so great is CPAN and all the available reliable
well-mantained quality modules.

Countless programmers have spent hours writing and mantaining module
code so we can have the capabilities to perform certain operations
trouble and stress free. This saves us from unneccessary development
time and headachs. You wouldn't spend hours and hours trying to
reinvent the wheel when the wheel is right infront of you ready to be
used.

What you have is a piece of code that dumps all parameters into Global
variables regardless of size. This will be stored in memory during the
duration of run time. Your sub form parsing technique is dated and
though may get the job done it also does ZERO error and safety handling
which makes it open to all sorts of future and present catastrophes.

You claim you want full control over how the form data is processed yet
you use it in the most generic way which makes your statement reflect
your inexperience even more so. If you have several CGIs and each use
the same copied sub-routine you are actually limiting functionality and
mantainability. Eventually you'd end up dumping the code in a module.
Then you will soon or later be forced into spending hours trying to
make your code more strict and bug free. Which would be reinventing the
wheel.

Modules are created for a reason. It's so programmers can use reliable
safe code instead of trying to reinvent the functionality of an
operation for every project. CGI.pm is the standard for parsing form
data if you choose not to use it you are only limiting yourself and
putting your web site, server and users at risk.

.

Relevant Pages

  • Re: Somerset and Dorset tears
    ... turn ourselves around in circles to reinvent the wheel. ... We have had the Commission on Integrated Transport ...
    (uk.railway)
  • Re: Embedded OSD (Not STV5370A)
    ... >>would not reinvent the wheel, unless it is a project to learn about. ... been messing with video and image processing for too many years. ...
    (comp.arch.embedded)
  • Re: Sympatico ADSL on freebsd
    ... reinvent the wheel? ... This and the rest of your response betrays an attitude that is confusing to ... they don't administer anything because for them a computer is a tool. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: question about a simple for `ls` script
    ... Maybe my question is too stupid, or you guys think I can google ... You are trying to reinvent the wheel. ... Jens Goerke, mobilcom Server Systeme ...
    (comp.unix.solaris)
  • Re: [OT] .NET Rant
    ... Obviously, if you have to reinvent the wheel, the built in classes are ... The lazy programmer would use what is built in. ...
    (microsoft.public.dotnet.languages.csharp)