> ++> application.userID NUMERIC = global variable
hi John,
I'm not sure that global vars get any special treatment, since they can be
passed out or required and passed out without change, just like any other
scoped variable. I think the point to the directionals is to simply track
the potential changes TO a variable.
for for a global var, often APPLICATION. scope, the directionals ++>, <++,
and <+> seem to work too.
I think we are all on the same page on this but just to re-iterate to be
sure: everyone seems to be positive about the directions. The real question,
as Lee as accurately pointed out, is whether any given section has to occur
in some particular order. What I liked about Lee's idea was that the
documenting of variables, say, could occur throughout the documentation, not
necessarily in any one section and the end of sections is defined clearly
(rather than being dependent on white space and non-visible carriage
returns.)
Also, I know everyone was holding their breath on this: I traced down that
it was Lee's post, not Fred's that I was quoting from when I mentioned
"Fred's technique". Sorry for the confusion. Hal's and Lee's techniques are
firmly before us ... This is not to imply that Fred has no techniques! :)
------------------------------------------------------------------------------
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.
