[Mono-list] Class Library coding standards

[Jason Diamond]

> Strongly agree.  The benefits of having all the code in a repository
> *formatted* in a certain way (as opposed to consistent variable naming
> conventions, etc.) definitely exist, though.

What are the advantages? I think that we're all adaptable enough to be able
to read and understand code regardless of where we put our curly braces.

I'm not advocating total anarchy--if I'm editing one of your files then I
plan on following your conventions (even though I probably don't prefer
them). Inconsistency is what makes code unreadable for me.

> An approach I've used with great success before is linking a source code
> beautifier to CVS commits.  That way, any time a source file is
> added to the
> repository, it's formatted consistently.

This might be neat but wouldn't it make any commit you make instantly out of
date and in need of merging the very next time you want to check in?

> Anybody know of a freely-available source beautifier for C#?

Can't use Mono's scanner/parser to write our own!

Jason.