> So far as I know, the Developer's exchange is an open forum. Buyer
> beware. Whatever someone posts get put up there.
>
> In contrast, the cflib.org is checked in an attempt to retain high
> quality of the functions and content. What they actually
> check for, I
> can't say. I believe that it is efficiency. There is some
> text about this
> on the cflib site.
>
Things we check for:
1) Does it already exist? You wouldn't believe how many submissions we
get for UDFs that mimic BIFs (built in functions)
2) Is every temp variable "var" scoped. (Cardinal sin #1 for UDFs is
forgetting a var.)
3) Does it make sense?
This is very arbitrary. We have a UDF that does Weight Watcher Points.
Will anyone use it? Probably not. Ditto for the Dog Years to Human Years
UDF. At the same time, though, if a UDF is _extremely_ particular, we
might reject it.
4) Is it "good" code?
Again, very arbitrary. I like to think I know a thing or two about good
code. So does Rob. So, for example, we would change code like this:
structval = evaluate("structname." & key)
to
structval = structname[key]
We will also rewrite code that uses loops where it's not necessary.
Etc, etc.
We always ping the author when we modify their code so that they know
what we did and why we did it.
Again, we aren't perfect, but we do try our best. ;)
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
______________________________________________________________________
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
