Re: Symbol Name Length (Was: STL Memory leak?)
On Apr 8, 9:52 pm, Sherm Pendley <spamt...@dot-app.org> wrote:
Daniel Pitts <newsgroup.spamfil...@virtualinfinity.net> writes:
blargg wrote:
By the way, your naming convention is very verbose, and
thus obscures things. The scope of a variable should play a
part in the length of its name; smaller scope, shorter
name. But this is just a style issue.
Not to start a flame war, but I disagree. Names should
*always* reflect the semantics of what they represent as
concisely as possible. Take away all you can, but no more.
Completely agreed, with one exception: Using "i" for a loop
counter is well- established and acceptable, even though it's
semantically meaningless. :-)
Actually, for a loop _counter_, I'll use count, e.g.:
for ( int count = n ; count > 0 ; -- count ) ...
On the other hand, i, j, k... are the standard indexes in every
book on mathematics I've ever seen. If I'm iterating through
indexes, then the first should be i, the second j, etc.;
anything else is obfuscation. Of sorts: there are certainly
exceptions, e.g. two independent indexes into different things
can't both be called i.
Now if only I could find an equivalent convention for iterators.
I'm currently using iter, jter, kter, etc. Which certainly
isn't universal (and luckily I rarely have nested loops with
iterators).
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34