Grant Jacobs wrote:
- conventions like: globals capitalized, locals lowercase or agregates capitalized, scalars lowercase
IMHO these are archaic conventions, coming from languages such as C (where there's only one global and one local level, in contrast to Pascal which has arbitrarily many levels, and a local variable of level 1 can behave like a global variable, seen from a routine at level 2, etc.), and assembler (where there's a general difference between aggregates and scalars). So I don't care much for such conventions.
They might be archaic (and I think so too), but one thing I'd like gpc to keep in mind is porting code to and from other languages. Silly things like this can help porting. Another example might be the use of leading underscores in identifiers; de facto std. in C for internal variables in libraries. In Pascal there is no practical need for these, but they are useful when shifting code to C or some other language.
All of these are warnings and can be turned off. I basically agree with your argument, that's why I also wouldn't like to turn the underscore warnings into errors (except in strict standard Pascal mode where it's prescribed).
I tend to program case-sensitive myself, partly habit and partly to create one less problems if I have to shift the code to another language.
Me too, and the current warning does not hinder doing so (just enforces more case-sensitivity than a (declaration-wise) case-sensitive language would demand). Frank -- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707