RE: [CFCDev] More CFMX Excellence with Component Inheritance

[Roland Collins]

Title: Message

This harkens back exactly to the “empowering non-programmers” argument.  It may be bad coding to us, but to the novice, which CF purports to be the ideal language for, this may not be so obvious.  But again, I think it comes down to consistency.  If the tag behaves slightly differently in a CFC than it does elsewhere in code, it should be a different tag!  Maybe a “cfinline” tag is in order that does indeed emulate the cut-and-paste paradigm.   Roland Collins   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Rafferty Sent: Friday, January 30, 2004 4:25 PM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] More CFMX Excellence with Component Inheritance   Brian Kotek wrote: Not sure that's the point, Todd.  What if he's using a database that doesn't support stored procedures?  I think the point is that in some cases, cfinclude behaves in different ways, and aside from trial-and-error there's really no way to know for sure how it's going to respond.   Agreed, but I think that the point that Sean is trying to make is that if you opened up a file with nothing but half-assed SQL statements and CFQueryparams... to someone that didn't know the system or anything, what are they supposed to expect?  Why would anyone consider this to be "acceptable" programming?  It sounds like an excuse for bad coding more than a "we need this because ..." My .02 cents, nothing more.  Just one rat's opinion... ~Todd