Re: [orbitcpp-list] idl compiler has arrived

[Phil d. <ph...@us...>]

"Braden N. McDaniel" wrote:
> 
> Please don't use tabs. Quite contrary to the claim here, they *don't*
> scale well. When you indent code at a particular tab width, it isn't
> particularly likely that things will continue to line up well using
> a different tab width. Furthermore, I don't want to have to reconfigure my
> editor just to make someone else's code readable.
> 

As far as I can see, this only becomes a problem if people mix spaces
and tabs in their code. This has never been a problem for me in the past
(a single keypress in emacs sorts it out).

> Spaces offer consistency. The more aggressive indentation requirements of
> C++ (relative to C) make a large indentation level impractical--IME, 2 or
> 4 spaces work adequately.
> 

I think I agree about the indentation level of 2 or 4 being more
practical, but I don't see using tabs being a problem at this stage. If
it turns into a problem, then we'll switch to spaces.

> 
> It seems to me that for a project like this it just makes a Whole Lot Of
> Sense to use the same naming convention as the C++ binding to CORBA. I've
> found that I can adjust to just about any naming convention after staring
> at it long enough, but consistency is *important*.

I agree with this. The problem is that Andreas' compiler uses Java-ish
style conventions (no underscores), where as the C++ language mapping
uses underscores. Making all of this consistent will be quite a lot of
work. 

Maybe we should have one standard for the compiler, and one for the
runtime (and generated stubs/skels). Is this madness?! (I think it
probably is).

Andreas, would you be really upset if we went with the C++ language
mapping convention? It is the only thing we *can't* change!
 
> Now, that said, in case I have some time coming up (I might), are there
> any relatively small, well defined tasks that would be well-suited to
> someone getting his feet wet with this project?
> 

There will be in a few (2 maybe) weeks. At the moment things are up in
the air again while we stablise the new runtime with the new compiler.

Cheers,

Phil.