Andrew Scott wrote:
Spike, 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. Just because you can't do it doesn't mean that you should mark it as being bad practice either.
The point of having these things as warnings is so that you can turn the warnings off and on as you desire. I notice you didn't pick up on the fact that use of cfinclude would also trigger a warning. I would have thought that would have been just as contentious.
As Sean said, the whole point of the warnings is that you can use them to check your code for consistency. If you think variables in cfmodule, cfobject and createobject calls are ok then turn that warning off. Likewise, if you think cfinclude is ok turn that warning off. I just happen to think that there are good arguments for keeping them out of code, so it would be in my interests to add those warnings as an option. As long as I'm the one implementing the functionality I'll make sure it fits my needs.
There is also a very good chance that more than half of the possible warnings would be turned off by default. The two I mentioned would almost certainly be off by default because there is so much code out there that commonly follows that practice. Many people, you included, obviously think there's nothhing wrong with that, others think there is. It seems to me that with that in mind, it makes sense to provide an option to see what's going on in the codebase in that regard. Especially if you can turn the warning off simply by checking a checkbox.
Spike -- -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org ---------------------------------------------------------- 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]
