On 7/4/07, Jaime Metcher <[EMAIL PROTECTED]> wrote:
One could argue that in CF there is only one constructor, and it's CreateObject(). It's always accessible, and as the developer of a CFC I can do nothing to turn it off, influence its behaviour, or rely on any initialization being run other than the no-argument non-method "pseudo-constructor". Surely that was Gilad's other main point?
No. And your supposition is not actually true anyway. Your pseudo-constructor can throw an exception if certain conditions are met, thus preventing use of createObject(). You can use the metadata of the object as "static" data and implement full fledged singletons, for example. The problem is that you're taking an argument that is essentially leveled against Java and applying it against ColdFusion. Your logic is flawed. I also think you're over-analyzing an academic issue that has no basis in reality - which is essentially what happens in Gilad's thread... the "who cares?" responses. Can you state a *specific* problem that you think needs to be solved rather than appealing to abstract -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood 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]
