[orbitcpp-list] idl compiler has arrived

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

Hi phil, hi list,

  the compiler's in sourceforge cvs. for me, it does compile, it does
install, but it does not do anything even remotely sensible ;) 

Some other things you should know about:

* configure.in now has special handling (should i say "kludge") for
--enable-debug. I do not believe this is very well written, but heck, it
prevents me from growing a dwarf's beard while compiling everything with
"-O2" on.

* i put the two tests i had created so far in the tests directory. (they
are basic/ and idl-torture/, where "basic" is just plain understatement
for the kind of test. it features basic types, strings, typedefs,
scoping, diamond of death inheritance, object reference passing back and
forth, well, all this really _basic_ stuff B-> ... first job should be
to get this baby working again, i guess.)

* phil, i know you hate my indentation style, so if you want to do
something about it (or got a tool to do so), now is the time. (while
you're at it, you may also make a mess of my nice-and-plain (tm) source
file headers to keep things uniform) (if you tell me what to do, i will
help out) (call this stage "one" (tm)) 

* and for the final and most important question: what is to be done
next, after stage "one" (tm) is complete? ya, get the thing to work,
right. i almost forgot. :) but in what order? and _who_ does _what_? i'm
currently preparing for a math exam, so there's not too much time, i'll
see what i can do. (say, an hour or so each day) first thing i would
look into is doing some cleanup on the idl compiler, to remove the
clearly o2cpp-specific parts (and perhaps code new ones for your
runtime). yet, this requires completion of stage "one" (tm) :) 

tell me about your plans. i wanna get goin'!

cu
andy

PS:
phil> (I copied a load of naming conventions from Andreas' o2cpp ;-)

I just _love_ naming conventions ;)