> > Can you think of a case where a Thing returned from > createObject will > > behave differently from a Thing returned from > createObect(...).init() > > (where init returns this of course). It certainly seems to act (in > > every possible > > way) > > the same as a CFC instance, to the point where you can pass > it to an > > argument where type="the name of the cfc". > > > If it walks and talks like a duck, it must be a duck. Well > no, you can have two different things that act the same in > every way, but not be the same. Does it matter in that case? > No, but it is important to understand they are not the same > should that change in the future.
I would agree with you except for one thing - CFCs themselves (well, cfargument) allows the Thing to be passed in when type=X. This isn't a hack like the pseudo-constructor. The CF engine itself is saying that Thing == a CFC. Any MACR folks on the list that can answer this more fully? -rc ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
