Darren New wrote:
> No. I'm saying that you're trying to impose your style on the definition 
> of C# for some reason. I'm saying that if you know C#, there's no 
> confusion about properties or variables.

BTW, C# already has naming conventions that covers much of what you're 
talking about, established by MS and used throughout the libraries. They're 
also much more extensive than simply how you capitalize variables you can 
trivially look up with the IDE. It makes it possible for me to know exactly 
the arguments to xyz.OnChange, xyz.OnChanging, and xyz.OnChanged, knowing 
nothing more than the conjucation of the verb there, for example. I also 
know how to start in the background any process I want to run that way, how 
to get the result back, what the functions will be called, etc.

I find it much more helpful to be able to look at a function call and say 
"Oh, that launches a thread that runs X, and when it finishes it'll invoke 
my Y function with two arguments that are .....".

The style guides are dozens of pages long, letting you read code written to 
that guideline and actually know useful information about it rather than 
just where to look up useful information.

I'm not against naming conventions, and I do think they improve readability. 
I just don't agree that "mCounter" vs "gCounter" is an example of that.

-- 
Darren New, San Diego CA, USA (PST)
    Eiffel - The language that lets you specify exactly
    that the code does what you think it does, even if
    it doesn't do what you wanted.

Post a reply to this message