Sean, Thanks for taking the time.
> > I don't see a Part II there - is that the correct URL? Sorry, "part II" refers to my part II email to this list. > > In ColdFusion, you could have a singleton CFC instance (of type > MyThingClass) associated with your regular CFC instances (of type > MyThing) and use the Smalltalk-style model. In fact, if MyThingClass > was really a factory CFC for MyThing objects, the chances are that > you'd be squarely in the Smalltalk-style world here - your "class > methods" and "class variables" would simply be (non-static) methods > and variables on your factory object and you could ask the factory for > actual instances of MyThing. Yes, this is what I'm doing. Does anyone think this is weird? > > > Is Hal's point that if you need to solve these sorts of > problems, don't use > > ColdFusion? > > Hal's point - at least in the article you link to above - is somewhat > along the lines of using Java for Java problems (large, > well-specified, rarely changing, enterprise systems) and ColdFusion > for ColdFusion problems (various scale, perhaps loosely-specified, > fast-changing / evolving, new systems). > Yes, I'm totally with Hal on most of this. I know it wasn't his main point, but I can't see why you'd say the Smalltalk-style class object isn't totally suited to loosely specified evolving systems. You know, while we're crystal ball gazing about the next version, why would this be out rather than in? Accepting that all the PDF/Flash stuff is a higher priority anyway. 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]
