Re: [orbitcpp-list] idl compiler has arrived

[Braden N. M. <br...@en...>]

On Wed, 1 Mar 2000, Phil dawes wrote:

> "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.

Which is an inevitability, IME. Of course, I am very likely biased by my
own coding style, where I've found that indentation schemes are good
*guidelines* which should occasionally be bent a bit to do things like
keeping lines from getting Way Too Long or line up a bunch of related
assignments, all in order to accommodate the higher goal of readability. I
also do things like

  void Class::method(Type arg1,
                     Type arg2)
  {}

> > 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. 

Yes, but it will be tedium rather than thought-intensive work. Sounds like
a good introductory task, perhaps. If you all decide to do this, I offer
to help with the conversion.

-- 
Braden N. McDaniel
br...@en...
<URL:http://www.endoframe.com>