29 Nov
2011
29 Nov
'11
1:36 p.m.
On 11/28/2011 09:27 PM, Nathan Kinder wrote:
This can lead to false assumptions when one should really consult the declaration to see what it truly is. The ability for the naming to be inconsistent with the declaration makes encoding the scope useless (and potentially bad) IMHO. I know I've been very frustrated running into variable names in C that had the type encoded originally, but someone changed the type in the declaration without changing the variable name.
Which is precisely why encoding type information into a symbol name is a bad idea. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/