> > I don't think it would make things simpler for the vast majority of CF > programmers.
Fair enough. > Robustness doesn't really come into it. Without this sort of thing built-in, a simple CreateObject() will just do an end run around any attempt to wire in a totally dependable class-instance relationship. This is an issue because with frameworks you don't always have control over when and how objects are instantiated. If I could tell ColdFusion to *never* instantiate an object of a given type except through my given factory, the robustness issue would go away. > It might be *easier* than a proper DI-type approach, but I'd much > rather go > with ColdSpring than adding odd little language features. It's not about language features, it's about concepts. The proposition is: "every object has a class; classes are also objects; every object has as an intrinsic property a reference to its own class". I take it you're on the "NO" side. That's cool, I'm trying to get a reading on where CF people stand on this question. > > -- > > Tom Chiverton > Helping to globally disintermediate error-free eyeballs > on: http://thefalken.livejournal.com Jaime Metcher You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
