> On Wed, 05 Nov 2003 17:22:43 -0600, Dan Muey wrote: > >> If it comes to the point where you need to "hack around" > CGI.pm, I'd > >> say go with your original inclination to just do it yourself. > > > Give me one example when you'd need to hack CGI.pm to handle input > > that you can't do without hacking it. > > This might not justify as "hacking" the CGI.pm, but once I > had to do something really special related to session > handling. The solution wasn't to hack, change or write my > own CGI handling module, but simply subclass the original CGI.pm.
So that was basically taking input and doing something specific with it right? The OP was simply parsing form data to do whatever with it. Whether that is printing it out, emailing it, putting in a database, or doing some special session handling, they never said so it's all still the same, close but no cigar :) -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
