Closed ghost closed 8 years ago
Thank you, but no, because it will encourge the thing I want to avoid. If it's optional, there will be no guarantee that your code will always work the same regardless of your FutureScript version.
I have a CoffeeScript use case: I had some CoffeeScript code, but when I upgraded CoffeeScript to 1.9.0, it didn't work, because of language incompatibility. I had to modify my code. See its changelog:
Changed strategy for the generation of internal compiler variable names. Note that this means that
@example
function parameters are no longer available as nakedexample
variables within the function body.
On the other hand, because CoffeeScript must consider version compatibility very seriously to eliminate these things (at least as far as possible), this will make the language grammar very hard to improve later.
I think version line should be optional. If no version line, default settings will be used. Furthermore, version line should be a (special) comment, something like:
Something like encoding settings in ruby. Thank you for futurescript.