Sean, That's ok, but if we disagree I would like to know why you disagree with variables. Like I have stated, I strongly believe its fine, and doesn't need a warning as it's like forcing a best practice on someone.
Maybe that's why I see it differently, because newbies will come along and start calling best practices because cfeclipse throws a warning on something that is extremely valid. Just my opinion Sean, and a little curious why others would want a warning on that scenario that I gave. Regards Andrew Scott Analyst Programmer CMS Transport Systems Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9699 7988 - Fax: 03 9699 7976 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Thursday, 16 June 2005 5:41 PM To: [email protected] Subject: Re: [CFCDev] LINT like tools for coldfusion? On 6/16/05, Andrew Scott <[EMAIL PROTECTED]> wrote: > Now based on that, if the unit testing was to check for variables in extends > and cfargument I would agree. But why flag a warning for valid component > paths such as CreateObject('component','#compath#.system.security') doesn't > make sense to me because its very valid. As is <cfmodule > template="#templatePath#\module\module" and I don't think this should be a > warning at all. As usual we disagree. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
