Hi! I guess Steve Comrie has answered the first question.
As for the second question, there should be no shortfalls at all. CGI::Simple is CGI.pm compliant -- i.e. it has the same interface inputs and outputs (basically -- less the html generation). The only mandatory elements (that I know of - but don't hold me to it) are param() to access the values passed into the script, header() to generate headers and redirect() to do a redirect header. Whatever other features you use from that object are up to you. To see more on CGI::Simple's CGI.pm compatibility: http://search.cpan.org/author/JFREEMAN/Cgi-Simple-0.06/Simple.pm#COMPATI BILITY_WITH_CGI_pm To see some of the differences: http://search.cpan.org/author/JFREEMAN/Cgi-Simple-0.06/Simple.pm#DIFFERE NCES_FROM_CGI_pm A list of methods from CGI.pm that are not in CGI::Simple: http://search.cpan.org/author/JFREEMAN/Cgi-Simple-0.06/Simple.pm#METHODS _IN_CGI_pm_NOT_IN_CGI_Simple I have no idea about CGI::Minimal, but a quick glance shows a lack of header() and redirect() methods. I supposed you could subclass it and add them yourself. HTH, -Brian > I second Gerard's request -- how do you do this? And, my second question > is what type of shortfalls can I expect to find? In other words, are > there any other CGI.pm functions used by CGI::Application that may break > if I use CGI-Simple (or even say, CGI::Minimal)? http://www.gordano.com - Messaging for educators. --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
