Re: [orbitcpp-list] idl compiler has arrived

[Andreas K. <ak...@ix...>]

Hi again,

> or just a plain "make". If you don't want "make" to build the tests then
> we'll build the option in as a  ./configure parameter (in fact the old
> ORBit-C++ archive does this).

good idea.

> BTW, If you add the line
> TEST=foo
> to a Makefile.am, then foo is executed when you run make check.

... that makes me wonder what i did with all those
mother-in-law-comes-around-hook things :)

> Agreed - I think I've found the tool: astyle. I got it from redhat
> powertools.

i got this some time ago, but i found it too crappy to use. now that you
brought it up, i re-got it, and yes, it is crap, but it is all we have
*shrug*. for example, it does make those

some::spuriously::scoped::method(
  with,really,really,many,arguments,and,even,
  more,and,more,and,more,arguments
  );

look like

some::spuriously::scoped::method(
                                
with,really,really,many,arguments,and,even,
                                 more,and,more,and,more,arguments
                                );

which makes a reasonably readable line a particularly ugly one.
ugh-yuck. i tried to change the source to remedy this, but this thing is
so heavily obfuscated that i doubt the author ever fully understood what
his program did.

for now i believe that the following .astylerc does (partially) do what
we want:

snip ----------------------------------------------
style=kr
mode=c
indent-classes
indent-switches
indent-namespaces
indent=tab
snip ----------------------------------------------

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

> > 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 :)

> The indentation is like K&R, but without the aligned braces for
> functions. I'm quite happy to go with this indentation.
> 
> I'm not really that fussed about all the other stuff as long as the code
> is readable - most of the corba spec breaks it anyway. I think we should
> start with indentation, and leave the rest up to the developer writing
> the code.

maybe i'm too pedantic - sorry if that is so.

> I usually use m_ to refer to member variables. 

For me, this distinction was upper case (members/globals) vs. lower case
(locals).

> > tonight, i'll be looking into the string test and perhaps start adapting
> > the compiler a bit.

probably not tonight. i got to get this math stuff done... some time...
perhaps i'll get to it after midnight... when i should be in bed... uhh.

> Cool. BTW, what is CET in relation to GMT? - I reside in the UK so my
> evenings start at ~ 7.00 GMT. I'm a bit worried that If I go and run
> astyle over the code while you're changing it, then cvs will have
> problems merging. What time do you think you'll start hacking?

i'm in karlsruhe, germany. (CET=Central European Time=GMT+1) 

bye
andy