I would contend CFMX supports overloading, just in a very un-java way. Instead of defining multiple methods with different argument sets, you define a single method with optional arguments.
That's not overloading. Overloading is *specifically* where you have multiple methods with the same name and the language processor chooses the best match to call.
Now, where did I put that draft white paper "99% of Overloading is Bad"...?
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
