It doesn't throw an error, but it does confuse the API. Either the argument is required (meaning you have to pass one in), or it is not (in which case you can set a default for it if you choose). In my mind, if you specify a default value, that means the argument isn't required.
On 10/16/07, Aaron Rouse <[EMAIL PROTECTED]> wrote: > > Why not? Sure the default sets which means it really is not required, but > it does not throw any errors. I have some old CFCs from I think a > BlueDragon project that do this almost consistently in but not sure why > since inherited them. I do know on CF6, CF7, and CF8 they all run fine. > Guess they will remain that way until the day it throws an error or they are > retired. > > On 10/16/07, Dan Wilson <[EMAIL PROTECTED]> wrote: > > > > > > 2) You may declare a default attribute for a cfargument, or you may > > declare required=true. Not both. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
