I posted the current Fusedoc standard a couple of days ago. Does anyone have
any concrete suggestions for improvements? The original standard was based
on general principles of machine/human readability, ease of learning,
clarity, etc. I don't know that reviewing those principles will be nearly as
productive as some actual suggestions along the lines of "I'd prefer to see
variables put into a structure." That kind of thing. Any ideas or
suggestions?
-----Original Message-----
From: John Foulds [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 26, 2000 6:44 PM
To: [EMAIL PROTECTED]
Subject: FuseDoc specification
Sorry for the encoding grunge, damn OLE cut and paste:
Hal, SOS:
PARSER COMMANDS
<!---FUSEDOC = starting clause
END FUSEDOC---> = ending clause
VARIABLES
--> userID NUMERIC = attribute explicitly passed into the fuse
<-- userID NUMERIC = attribute explicitly passed out of the fuse
--> [userID] NUMERIC = optional parameter passed out of the fuse
<-- [userID] NUMERIC = optional parameter passed into the fuse
<-> userID NUMERIC = pass-thru variable (passed in AND out w/o change)
++> application.userID NUMERIC = global variable
FILES
+++ FILE.CFM = required include file
[+++] FILE.CFM = optional include file
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
