[boulder.pm] CGI.pm basics

[Stevi Deter]

the reasons i use cgi.pm:
1. taking care of parsing the variables; instead of having to add the
routine to each and every cgi program, it's all done for you. libraries are
your friends.
2. minimizing the html i have to encode in the program. i'm in the "hate to
see it in the script" camp, and find my cgi.pm-using scripts to be far
easier to read and debug.
3. debugging - cgi.pm can emulate the cgi environment and make command-line
debugging easy. this has saved me hours and hours and hours of work. the
carp module is also exceedingly useful in this arena.

--stevi
  you can pry my cgi.pm from my cold, dead, rsi-crippled fingers...


> -----Original Message-----
> From: owner-boulder-pm-list at pm.org
> [mailto:owner-boulder-pm-list at pm.org]On Behalf Of Eric Shore Baur
> Sent: Thursday, January 20, 2000 5:15 PM
> To: boulder-pm-list at happyfunball.pm.org
> Subject: RE: [boulder.pm] CGI.pm basics
>
>
>
> 	Something I've been wondering for awhile...  What are the benits
> of using cgi.pm?  Right now, my cgi scripts just parse the content
> themselves using environment variables and then a foreach
> loop and a %form
> hash to store the key/value pairs.
> 	Is cgi.pm faster, offer more service that I'm missing
> (other than
> off-line checking of script - and no, I haven't really read
> the docs on
> it, but the references to it don't seem to do much that I
> can't do as fast
> by hand)?
>
> 	Kind of an open ended question, I guess... but is that last
> example script the kind of thing people use it for - or are
> there other
> neat tricks that I'm missing?
>
> Eric
>
>
> On Thu, 20 Jan 2000, Stevi Deter wrote:
>
> > there's always "official guide to programming with cgi.pm"
> by lincoln stein
> > himself - isbn 0-471-24744-8. i refer to this book more
> often than i do to
> > the man pages for cgi.pm.
> >
>