RFC CGI.new(nil)

ruby-talk
1

rubyists-

how many of you are actually using the CGI tag methods? i currently am using
Amrita for all of my html generation and thus do not need my cgi objects to be
dynamically extended with ‘html3’ or ‘html4tr’, etc. also, as someone pointed
out a week ago on this list it is this (the dynamic extension) part of CGI.new
which is exceedingly slow. is there any reason then why we should not be able
to :

cgi = CGI.new(nil)

-a

···

–

Ara Howard
NOAA Forecast Systems Laboratory
Information and Technology Services
Data Systems Group
R/FST 325 Broadway
Boulder, CO 80305-3328
Email: ahoward@fsl.noaa.gov
Phone: 303-497-7238
Fax: 303-497-7259
====================================

2

For me, under 1.6.8, that works just fine. What result do you get?

Regards,

Brian.

···

On Tue, Mar 25, 2003 at 01:59:01AM +0900, ahoward wrote:

how many of you are actually using the CGI tag methods? i currently am using
Amrita for all of my html generation and thus do not need my cgi objects to be
dynamically extended with ‘html3’ or ‘html4tr’, etc. also, as someone pointed
out a week ago on this list it is this (the dynamic extension) part of CGI.new
which is exceedingly slow. is there any reason then why we should not be able
to :

cgi = CGI.new(nil)

3

I never use the tag methods. I simply use the CGI module for pulling form
variables:

cgi = CGI.new

if cgi.has_key?(‘whatever’) …

–frank

···

On Mon, 24 Mar 2003 16:41:42 +0000, ahoward wrote:

rubyists-

how many of you are actually using the CGI tag methods? i currently am using
Amrita for all of my html generation and thus do not need my cgi objects to be
dynamically extended with ‘html3’ or ‘html4tr’, etc. also, as someone pointed
out a week ago on this list it is this (the dynamic extension) part of CGI.new
which is exceedingly slow. is there any reason then why we should not be able
to :

cgi = CGI.new(nil)