>If you don't want the argument to appear when you don't pass it, simply don't declare the CFARGUMENT tag.
If one is developing an API as we are, we need the documentation component of the <cfargument> tag. Well really all we expect to do is to be able to use the tag as it was intended, which isn't too far-fetched an idea, I think. The <cfargument> tag is not *supposed* to create the argument (with an unusable default value): that's the problem. <cfargument> is for defining what an argument might be. IF it's passed. And if you *want* to give it a default, the mechanism is there. CF should not be setting a default automatically. Adam ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
