Dave Cross <[EMAIL PROTECTED]> writes: > > > * either of what should be in guidelines or where there are some i > > > could ste^H^H^H use as a base. > > > > Let's try it. > > > > thou shalt use strict > > > > thou shalt use tainting > > > > thou shalt use warnings > > > > thou shalt not mix code and html if you can possibly avoid it. > > > > OTOH, this *could* get a little religious... > > What happened to: > > thou shalt use CGI.pm Because CGI.pm is a bloated overweight piece of crap that breaks the 'thou shalt not mix code and html...' guideline big up massive stylee, and has some more than a little scary action at a distance stuff going on with it. Oh yes, and it can screw up your Apache::Request structure if you use it in the wrong handler. Apache::Request is probably your friend.
- Re: cgi coding guidelines James Powell
- Re: cgi coding guidelines robin
- Re: cgi coding guidelines Steve Mynott
- Re: cgi coding guidelines James Powell
- Re: cgi coding guidelines Robin Szemeti
- Re: cgi coding guidelines Struan Donald
- Re: cgi coding guidelines Dave Cross
- Re: cgi coding guidelines David Cantrell
- Re: cgi coding guidelines Steve Mynott
- Re: cgi coding guidelines Michael Stevens
- Re: cgi coding guidelines Piers Cawley
- Re: cgi coding guidelines Leon Brocard
- Re: cgi coding guidelines Piers Cawley
- Re: cgi coding guidelines Shevek
- Re: cgi coding guidelines Roger Burton West
- Re: cgi coding guidelines Mark Fowler
- Re: cgi coding guidelines Piers Cawley
- Re: cgi coding guidelines Roger Burton West
- Re: cgi coding guidelines David Cantrell
- Re: cgi coding guidelines Robin Szemeti
- Re: cgi coding guidelines David Cantrell
