Isn't the *whole point* of method overloading that you don't have to muck with the existing methods one jot, you just write a different method with a different set of args?
So the approach you're suggesting of having conditional code within a method to determine which "submethod" it should be executing given the arg combination is not really the same thing. It's not "method overloading" it's "a big elseif statement". It's the need for this sort of approach that makes me cringe whenever someone uses the term "OO" in reference to CF. Adam ---------------------------------------------------------- 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).
