Tom Schneider wrote:
| I actually think that your existing convention (1st upper, rest | lower) is an excellent way to resolve most things. I am quite sure | I don't have a grasp of the conflicting systematic
I also don't understand the conflicts, but this rule is painful. If I name a variable 'something' then I expect to be able to search the error messages for 'something' but of course it got changed to 'Something'. So if I want to cut and paste to search for the name in my program, it fails.
I didn't like this as well, and that's exactly why I've brought up the issue.
Why not take the first occurence of a variable as the name to use on all output?
The first, or the most recent one, that's still a question. After some experimenting, there seem to be points for both ways. I'm implementing the latter now (though it should be easy to change). So, e.g.:
program Baz;
procedure Foo; var BaR: Integer; begin end;
begin WriteLn (bar) end.
will complain about an unknown identifier `bar', not `BaR' ...
Note: only Germans like to capitalize all nouns!
I know, and that's not the reason why this rule was introduced (long ago). Rather it was to avoid asmname conflicts with libc routines etc. -- see, e.g., Pierre's mail for detailed explanations.
Frank