On 6/15/05, Andrew Scott <[EMAIL PROTECTED]> wrote: > I understand your reasons, but we don't use cfeclipse and I don't believe > that a unit testing should pin something that is very legal either.
If you don't use CFEclipse, why do you even care what constructs the tool flags as bad practice? Personally, I like the idea that CFEclipse would flag variables in component paths as a warning. You can't use variables in extends= (or cfargument type=) so there's a consistency argument here as well. Lint style tools generally flag lots of things that some people think are just fine. The only way to make a comprehensive tool that suits everyone is to flag everything that is even vaguely suspicious and let people choose to switch warnings off. Warnings don't mean "WRONG" they just mean "caution: check this manually". -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ---------------------------------------------------------- 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]
