***************************** Team Allaire *****************************
Yes, I agree that those examples almost certainly fall into the category of
"True statements that are not expressible in Fusedoc". Sure, we could create
a symbology that would allow us to express that, but I think you're
right--why bother?
I'm more interested in the grey areas between something Fusedoc clearly
should be able to convey and those examples of things I think should be
outside the realm of Fusedoc. For example, should Fusedoc be able to express
this?
I'll get one (and only one of the following): a, b, XOR c
-----Original Message-----
From: Erik Voldengen [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 27, 2001 5:23 PM
To: Fusebox
Subject: RE: Fusedocs Q
> if i get a then i will also get b
>
> or
>
> if the value of fuseaction is "XFA.onSubmitForm" I set
> client.CurrentUser;
> otherwise I set client.Unregistered.
>
I wonder if it really matters if you can symbolically represent this
logic. Why not just use text comments to fill in the blanks for such
tricky situations, keeping fusedocs nice and clean.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
