On Thu, 27 Jan 2005 14:33:52 -0000, Kerry <[EMAIL PROTECTED]> wrote: > > But why make the rest of us programmers figure out your proprietary > > objArgs technique? > in this particular case, my boss would be very happy if i made the app > incomprehensible to anyone outside the company, but i see your point.
What if you grow hire a new developer? You may not want outsiders to know how to use your app, but there's no reason to confuse a new hire. I just wrote a blog post on "brown box" APIs (brown box = muddy, hard to use attempt at a black box API) - http://clearsoftware.net. > > How do you make individual arguments required? > CFC is generic, it has no idea what its going to be passed (decides what to > look for depending on what you init it with), so if i used the > argumentCollection technique, there would be no <cfargument> tags in the > functions. (which means im not so sure about your 2nd point in this case) This could violate encapsulation pretty seriously - if the CFC doesn't know what args to be passed, the outside world must then know what it needs to pass. That implies the outside world must have knowledge of the implementation of the CFC - it should only have knowledge of the interface, which, in the case of methods, is largely defined by <cfargument> tags! -joe -- For Tabs, Trees, and more, use the jComponents: http://clearsoftware.net/client/jComponents.cfm ---------------------------------------------------------- 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]
