Hi Hal,
Well, yes, the first two of these are simple enough and common enough that I
would like to see them expressible in the formal part of FuseDoc.
Number Three I can't see much chance for expressing, nor much general use.
Mind you, I can see formal ways to express MUCH of this partcular
requirement.
Anyway, just to show my own credentials as agent provocateur, I must admit
that I am not even a comprehensive user of the EXISTING FuseDoc standard.
For now, I pretty much restrict myself to these:
-->[x]: blah blah
-->x: blah blah
<--[x]: blah blah
<--x: blah blah
And guess what? I use the text part to flesh out the requirements! In most
cases relevant to FuseBox, we are looking at a piece of code less than a
page long (or less than maybe 3 in StructuredComplexity). I have not yet
felt the need to enter more deeply into the formal specification language
that is currently provided by FuseDoc.
On the other hand, I am a great fan of PDL. I just don't think that FuseDoc
is the place for PDL - that should probably be left to the coder, not the
architect.
Once again, though, I suggest that it would be worthwhile harking back to
the questions posed by Jeff - "What is the purpose of FuseDoc? What is the
purpose of the ATTRIBUTES section?"
Thanks, I think that quite enough from me on this subject ;-)
LeeBB.
>From: "Hal Helms" <[EMAIL PROTECTED]>
....
>What other sort of things would you want to see Fusedoc express, Lee? Is it
>just the case where the existence of one variable implies the existence of
>something else?
>
>What about these English statements. Should they be expressible in Fusedoc?
>
>1. Create a client variable called CurrentUser if we get an incoming
>variable called userID.
>
>2. You're going to get in a variable called "Substitute_xxx" where xxx is
>the name of a productID.
>
>3. You are going to create a client-WDDXd structure called Users with keys
>for every user returned by a query. If there are more than 50 users, you
>need to divide this into multiple structures so that no one has more than
>50
>users. Name the structures Users1, etc. and if there is more than one
>create
>a client variable called "NumberOfStructures".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
