John VanSickle <evi### [at] hotmailcom> wrote in news:3CD46365.433CEFA3
@hotmail.com:

>> Parsing fails on line 248 of shapes.inc when the Spheroid macro
>> attempts to use 'Center' as a parameter name.
 
> A consistent naming scheme will alleviate this problem.
> 
> For instance, I prefix vector names with a v, scalars with s,
> index variables with i, and so on.

This is what I'd call putting the cart before the horse.

Given that shapes.inc and the other #macro-laden #includes are a standard 
part of the distribution, I tend to think it'd make far more sense for them 
to use a consistant naming scheme to stay out of the *users* hair rather 
than for the user to go through all kinds of contortions to stay out of the 
#include's hair.

I mean, you wouldn't like the idea of prefixing every name in a C program 
with an underscore (etc) so it wouldn't collide with names used by the C 
RTL, would you?  Of course not.  That's why the component names used by C 
RTL are prefixed with underscores: so the user gets virtually the rest of 
the non-defined namespace to himself/herself.

Post a reply to this message