> This seemed to be a pretty cool method because you create an
> object and then
> you can define methods (read fuseactions) of that object. So the
> query would
> be a method and then you could refer to that object and pass it
> that method
> and it would return the query object.
one solution, if you want to do some object programming, is to use a object
programming language. CF is not such a beast. I think it's a good idea to
keep in mind the old adage about "if all you've got's a hammer, then
everything looks like a nail". SmartObjects, CFObjects, etc and the like are
all very very interesting--but they beg the point: "why?" If you want to
write object orientated code then write in an object orientated language,
otherwise you're just forcing a square peg into a round hole--S.O. and
C.F.O. simply provide some sanding paper to smooth the square peg's edges,
they can't address the underlying issue of why the peg needed to be in that
particular hole in the first place
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
