Andrew Scott wrote:
Spike, Why should this be a warning? * Using variables for the paths to components, cfmodule calls and cfincludes (WARNING)
When it comes to code maintenance it is much easier for maintainers to debug and follow code if the paths are hard coded rather than set as variables.
It is also possible that the value of the variable may change for one reason or another leading to more difficulties when maintaining the codebase.
Finally, we plan to provide code assist for CFCs and possibly custom tags. Neither of these will be possible if you have used a variable as part of the path, while it will be possible if you haven't.
Ultimately, it isn't any more of a problem than leaving some optional attributes off the cfargument or cffunction tags which is why all of these things would be configurable in the cfeclipse preferences page.
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]
