Personally, I like to use single letter prefixes for my variables (see post
a few days back on the subject). I don't scope them in most cases but
really should for the CGI related vars (url, form, cgi, cookie). I used to
like CFPARAM for defining and data validation but found that writing my own
UDF in CFSCRIPT to handle it is actually faster. I also like using the
request scope to hold temp values that will be overwritten or used multiple
times (like in loops) as I can clean it out using structclear(). I've got a
number of other practices that I use and suggest (some of which I havn't
written up yet).
I think we should section off what we want to do in each part, get the best
practices and ideas, compile them and then use them. Sections like:
variable names
data validation
error handling
when to use CFSCRIPT
when to use UDF (and how)
CFINCLUDE vs. CFMODULE - when for each
how and what to pass to CFMODULES (no CGI passed as attributes)
etc.
At 12:58 PM 8/6/01, you wrote:
> Ok now that I have just about everyone signed up on the list we have
>to come up with coding standards sheet. This should include, how variables
>are named, flow of the program, pretty much anything you can think of. Can
>anyone start suggesting some sheets they may have already come up with or
>anything they would like to suggest?
>
>Robert Everland III
>Dixon Ticonderoga
>Web Developer Extraordinaire
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
