At 09:29 AM 4/9/01 -0400, you wrote:
>Hey everyone,
>
>I have a couple of fusedoc questions that I've been
>battling with for quite a while. How do you normally
>represent the following situations?
>
>1) Form fields: Do they count as outgoing paramters?
>If not, how do you specify their existence?
yes, they're outgoing.
>2) A parameter that is both incoming and outgoing, and
>may be changed (so it's not just a pass through <=>)?
--> paramName: STRING etcetc
<-- paramName: STRING etcetc
>3) A parameter that is optionally incoming and
>always outgoing (e.g., one that would be set by
>a <cfparam> tag)?
--> [paramName]: STRING (default="fusebox is great") etcetc
<-- paramName: STRING etcetc
something else i do.. i wonder if everyone else does this..
I don't specify the attributes scope for incoming parameters.. i make that
my "default", because almost all of my incoming parameters are attributes
scoped.
>Patrick
>----------------------------------
>Patrick McElhaney
>Application Developer
>American City Business Journals
>704-973-1019 704-236-8351 (cell)
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
