> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Sean A Corfield > Sent: Friday, January 30, 2004 2:33 AM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] More CFMX Excellence with Component Inheritance > > > It actually sounds to me as if it's exactly what I identified it to be, > > to be honest... Another bug with CFCs and <cfinclude>. > > Nope. It's designed that way. And it makes perfect sense when you > understand the model behind the language.
Not to be too much of a prick here: but we shouldn't really have to understand this. I mean if this behavior were actually documented we may still argue its merits but it wouldn't come as surprise. Whether it's a bug in the behavior or a bug in the documentation I agree with Adman that it's a bug (of some kind). With CFCs, more than any other feature (although locking in CF 4x comes close) there are really just way too many surprises and not enough solid, detailed information from MM. Jim Davis ---------------------------------------------------------- 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]
