M
Marian Edu
Guest
I can almost feel Gilles pain, the language is way to ambiguous and things won't probably get better as backward compatibility reigns 
If any of those ever gets implemented I would really like the 'use strict' annotation at file level much as in javascript... something that is ignored by previous versions and used to switch the compiler in strict mode what a file with that annotation is compiled. That way one can 'catch-up' in time, a compiler flag to compile the whole codebase will probably just make too many nervous 
As for warnings those have little to do with strict mode, even more if someone has an option to decide what to be ignored... this can well be added in the tooling (psdoe) and can be displayed as warnings even if not in strict mode (unless the developer/team choose to ignore particular warnings for reasons that they know better). However, if 'use strict' annotation is set in a file there should be no option to fake that by 'cherry picking' the rules... is that too much for one, just remove the annotation and keep that on the todo list for later Bref, the error conditions for strict mode might not be that long and have nothing to do with code formatting/case used for keywords, abbreviations and other things that might be nice to be reported as 'code style warnings'... there is still room for a 'lint' tool to help with those kind of things.
Continue reading...
If any of those ever gets implemented I would really like the 'use strict' annotation at file level much as in javascript... something that is ignored by previous versions and used to switch the compiler in strict mode what a file with that annotation is compiled. That way one can 'catch-up' in time, a compiler flag to compile the whole codebase will probably just make too many nervous As for warnings those have little to do with strict mode, even more if someone has an option to decide what to be ignored... this can well be added in the tooling (psdoe) and can be displayed as warnings even if not in strict mode (unless the developer/team choose to ignore particular warnings for reasons that they know better). However, if 'use strict' annotation is set in a file there should be no option to fake that by 'cherry picking' the rules... is that too much for one, just remove the annotation and keep that on the todo list for later Bref, the error conditions for strict mode might not be that long and have nothing to do with code formatting/case used for keywords, abbreviations and other things that might be nice to be reported as 'code style warnings'... there is still room for a 'lint' tool to help with those kind of things.Continue reading...