WarrenM:
So either you're saying:
1) STRICT should enforce syntactic rules that do not exist (i.e. prevent people from writing legal, unambiguous code). This is not so much STRICT as BIZARRE.
2) Or that BMax should be case-sensitive, and STRICT should correctly enforce this, but that programmers should be "intelligent" enough to name their variables as if it were case-insensitive. This is STRICT and BIZARRE.
There are many good programming practices that STRICT does not enforce, e.g. tidy coding, meaningful variable names, and consistent indentation. It may be good programming practice to consistently capitalize variable names, but it's also good practice to do a lot of other things.
Perhaps STRICT should also require users to submit to a urine test before compiling?
So either you're saying:
1) STRICT should enforce syntactic rules that do not exist (i.e. prevent people from writing legal, unambiguous code). This is not so much STRICT as BIZARRE.
2) Or that BMax should be case-sensitive, and STRICT should correctly enforce this, but that programmers should be "intelligent" enough to name their variables as if it were case-insensitive. This is STRICT and BIZARRE.
There are many good programming practices that STRICT does not enforce, e.g. tidy coding, meaningful variable names, and consistent indentation. It may be good programming practice to consistently capitalize variable names, but it's also good practice to do a lot of other things.
Perhaps STRICT should also require users to submit to a urine test before compiling?