Oh, please don't say that, Hal. That goes against the Fusedoc definition that
allows tools like Harness to exist. After all, the variable called
"Portfolio | Cluster | Market | Region" can't exist, even though the notation
makes sense to us humans. I'd definitely recommend
--> [Portfolio]: an INTEGER
--> [Cluster]: an INTEGER
--> [Market]: an INTEGER
--> [Region]: an INTEGER
Harness understands this notation perfectly, without need for additional costly
parsing.
- Jeff
On 25 May 2001, at 12:37, Hal Helms wrote:
> ***************************** Team Allaire *****************************
> That's exactly how I'd do it, Laura.
>
> -----Original Message-----
> From: Riccomi, Laura [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 25, 2001 11:42 AM
> To: Fusebox
> Subject: Fusedocs Q
>
>
> Using Fusedocs, if a script requires one and only one of a group of
> variables, how would you show this?
>
> For example, if Portfolio is passed to the script, then Cluster, Market and
> Region should not be passed to the script. If Cluster is passed to the
> script, then Portfolio, Market and Region should not be passed to the
> script.
>
> Having a perl background, I've been using the following notation, but I'm
> not sure this would be totally clear to a non-Perl person:
>
> --> [Portfolio | Cluster | Market | Region]: an INTEGER
>
> How would you guys do it?
>
> Laura R
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
