I'm still waiting to hear a decent example of when this type of
specification is actually needed. For all we know (with due respect to the
initial poster asking about this), the only reason it came up was because of
some odd logic requirement *in the coding*. If it's odd, then I'd rather
read about it in the Responsibilities section or in the variable
description. If it's not odd, then I'd like to see a decent real-world
example. And, even if we get a real world example, as I know Hal has one at
the ready, I'm still not sure that Fusedocs has to accomodate everything to
be successful. Remember that quote from Jurassic Park where the Jeff
Goldblum character says something like "you got so excited knowing that you
could do something that you never stopped to think whether you should do
it."
It seems to me, and here a lot of you will hear my most latest refrain, is
that the Fusedocs should be designed to tell the developer WHAT the template
will do, not HOW to do it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
