search

russplaysguitar / navel

Working towards a linter for cfscript
MIT License
2 stars 0 forks source link

Support for multiple versions? #6

Open russplaysguitar opened 11 years ago

russplaysguitar commented 11 years ago

Obviously it would be easiest to only support the latest Railo/Coldfusion versions (currently 4 and 10, respectively), but there might be cases where it could be useful to support multiple versions?

I could see it being helpful if the linter identified unsupported features for your version, but then again, the JIT compiler would throw an error in that case too.

russplaysguitar commented 11 years ago

Also: should the linter warn you of features that aren't supported in both Coldfusion and Railo?

adamcameron commented 11 years ago

Doesn't the code analyser that ships with CF cover the differences between CF versions?

russplaysguitar commented 11 years ago

I'm thinking more about the case where you're coding in an old CF version but still want to use the linter. If there are any deprecations between your version and the current version, the linter should warn/fail. So it might make more sense to have a "version" option rather than forcing the user to add ignore options for each deprecated function.

atuttle commented 11 years ago

I say ship linter 1.0 with support for the latest versions of supported platforms (ACF, Railo [, OBD?]), but code with the thought that we might, one day, want to support multiple versions.