While it is true that you won't use explicitly a symbol which you won't make public, the temptation is still there for those which you make public, for which you have to set up "rules" (with the same = nil support in both in C and asm) anyway.

For example, you cannot declare a public symbol "read only". Or you cannot distinguish a value from an address in asm (as in mov r0,address vs. mov r0,#address, with an intention to do something with @r0 later).

Isn't programming much of an art of self-control, rather than just churning out lines of - well - code? :-)

JW