Andrew Scott wrote:
Sean,
Because Macromedia are looking at cfeclipse as the new tool for development,
and when that happens then I would imagine we would swap from homesite /
dreamwaever to this when MM have released it.
Holy Crap!
You're even better informed than I am!
Where did you get this info from?
Tell me your sources dammit ;)
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.
Variables in extends and cfargument would be shown as an error, not a
warning since the code will not work at all.
Let me try to clarify exactly how this mechanism would work in cfeclipse
because I don't think very many people have seen how the Java stuff
warning/error stuff works.
In the cfeclipse preferences there would be a new preference tab called
errors/warnigs.
In that tab there would be a whole list of the things that the parser
can check for. Beside each of those would be a checkbox. If the checkbox
is checked, the parser will put a warning/error in the line number ruler
on the line where the relevant code was found. If the checkbox is
un-checked the parser doesn't even bother checking for that code construct.
We may decide to implement drop-downs instead of check-boxes. There
would be 3 options in each drop-down: ignore, warning, error. This would
allow you to completely control what the parser should do with regard to
those code constructs.
Bearing in mind that I have already said that about half of these will
probably set to "ignore" by default, I really don't see why there would
be a problem with your chosen code style.
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]
