Hey Pete, >I think interfaces,
I don't really think they're needed, and it'd really be a giant engineering feat to pull them off without making more people mad than happy. As for now, I consider an interface as existing "on paper only," and simply make sure the contracts are maintained via unit tests. >proper namespaces (Read later message in thread)...yes, per-application mappings etc. could make things easier at times, so I agree! > and typable > structs would make me very happy. This is also possible now via CFCs - why not create your "collection" as a CFC that only accepts a certain type of other CFCs in an internally managed collection? -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ---------------------------------------------------------- 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). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
