Re: [orbitcpp-list] idl compiler has arrived

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

I've been kinda eyeballing this project for a while, lurking. I'd like to
participate, but my current project load really won't accommodate it. As a
non-participant, I realize my comments on these issues might well be
dismissed, and I can't say I'd blame you terribly for doing just that. But
if you'll humor me, and entertain the viewpoint of a *potential*
contributor...

On Tue, 29 Feb 2000, Andreas Kloeckner wrote:

> > Why not just use tabs? That way people can change their editors to use
> > the amount of indentation appropriate to their display (19 inch monitor
> > or 80 char teletype).
> 
> agreed.

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.

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.

> > > snip ---------------------------------------------------------
> > >
> > > template <class T>
> > > class tplApple : public cPear { // <-- opening brace here
> > > // "tpl"/"c" class prefixes if we may choose
> > 
> > I prefer not to use hungarian notation for classes and types. It's ugly
> > and the fact that it is a template class / normal class should be
> > obvious by the context.
> 
> hmmm. it is a bit ugly, but keeps types from clashing with other global
> identifiers (which start in upper case in my code), such as:
> 
> cState State;
> 
> > >         void eatThisApple(); // func naming just like java
> > 
> > If you like, except that a lot of the corba methods don't apply to this
> > rule E.g. string_to_object() etc...
> 
> yes_but_underscores_are_so_damn_ugly :)

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

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?

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