-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Bell
>The fact is that components only take you so far for reuse anyway. Even if >you use strong typing and interfaces, components don't specify how errors >are handled, they don't explicitly document preconditions and >postconditions, they don't explain the structure or semantic meaning of >data passed (great - I have a struct - but what does each of the keys >mean?!). Errors should be thrown via cfthrow. That, or the hint field can be used to explain returned exceptional values, but for my money, throwing errors that can't be handled by the component internally is the best practice. Objects should not have pre and post-conditions for operation. If they do, they're not properly (or fully, anyway) encapsulated. If you were using strong typing, you would no longer pass structs - you would create objects with member definitions to handle the data elements. Roland ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
