>Required arguments without a default? How often do you run
>across those?
>It seems to me that if you're declaring an argument, you'd
>always specify a default, because you want that variable to be
>there. Otherwise you'd just use an implicit argument and
>dereference it out of the arguments array/struct.
Did you mean optional arguments without a default?
Giving a required argument a default value seems kinda strange, but maybe
I'm missing something.
As far as not specifying a default, I've seen people using code like this:
<cfunction name="saveProduct">
<cfargument name="productid" type="uuid" required="false">
<cfargument name="productname" type="string" required="true">
etc...
<cfif isDefined('arguments.productid')>
<!--- We're doing an update, so run the update query --->
<cfelse>
<!--- We're doing a crate, so run the insert query --->
</cfif>
etc...
</cffunction>
The productid has to be a UUID if it is supplied. If it is not supplied you
want to be able to tell so that you run the create operation. If it is
supplied it must be an update operation.
If you don't scope any references to productid in ARGUMENTS you could get
all sorts of bad things happening if productid exists somewhere in the
implicit lookup scopes.
Whether it is a good idea to be relying on that sort of construct is a
different question entirely, but it is certainly valid.
>
>Not to say that's not a good reason for using the arguments
>scope, but it seems a strange position to put yourself in to
>begin with.
Indeed, but I have seen a lot of code where that is exactly what people have
done.
----------------------------------------------------------
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]
