Ya, fusedocs seem best if you treat them like function 'statements' in other
languages. Only show what goes into the function(file) and what goes out of
it. Your globals file tells the rest.
----- Original Message -----
From: "Erki Esken" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, February 23, 2001 2:51 PM
Subject: Re: fusedoc philosophy
> Alan, think about what if you take a fuse from one app and put it into
> another. If you wrote down every global variable (even the ones that this
> specific fuse DIDN'T use), then you'll have to go over the fusedocs again
> and delete the global variables that your new app doesn't use. Because if
> you leave them in, they'll definately cause misunderstandings in the
> future.
>
> Erki
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
