[MacPerl-WebCGI] Re: CGI.pm versus the long way...

[Leland Beaudrot <leland@arpsynod.org>]

Richard Smith wrote:
> 
> Off the back of my post about file uploading, I have a question about using
> CGI.pm. To date I have used a subroutine modified from another script to do
> all the read-parse activity in my scripts. Now I find that this module can
> handle many of the tasks that I have been writing code for myself.
> 
> However, I have an in-built dislike of using anything when I don't really
> know what it is up to. I wondered if anyone could offer me their pros and
> cons of using the CGI.pm over doing it the long way. I am about to start a
> whole heap of coding, and would like to get settled on a method before I
> start banging away at the keyboard.

"CGI.pm has become the de facto standard module for writing CGIs with
Perl. It is so widely used that it has been included in the standard
distribution and is the recommended method for writing CGIs in Perl.

CGI.pm eases much of the 'grunt work' of doing CGIs, including entity
translation, input processing, address redirection, and header
manipulation. It also includes methods for producing HTML and forms more
easily." - Vicki Brown & Chris Nandor, _MapPerl_Power_and_Ease_, pp.
236-237.  For a more detailed summary of CGI methods, see O'Reilly's
_Perl_in_a_Nutshell_ <http://www.oreilly.com/catalog/perlnut/>, Ch. 10.

This about sums it up for me.  I love a programming environment in which
I don't have to reinvent the wheel every time I want to process a web form.
-- 
Leland R. Beaudrot
A fisher of men using the Net.  >((((("> ~Jesus
http://www.arpsynod.org/

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-webcgi-request@macperl.org