Re: [orbitcpp-list] Compiler Any support and sequence bug

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

Hi Sam, John,

Looks like we're going to have to do a merge-fest fairly soon. I've
almost finished union support (which was a bugger btw) and hope to do
a cvs commit tonight with this stuff. There are quite a few changes to
the compiler so I'd like to commit this before merging commences.

Then we have 2 options:

1) I merge the typecode/any patches manually and commit to cvs
2) We do the cvs 'thing' and each commit our stuff, merging as we go.

As a future plan, it makes sense to commit early and often - as long
as the thing compiles I'm not that fussed. (I'm guilty of not
committing early - mainly because I've had the archive to myself for
the last 3 months or so :-(

Cheers,

Phil


Sam Couter writes:
 > Phil Dawes <ph...@us...> wrote:
 > > 
 > > Sam - have you had a chance to look at this? Is there any crossover
 > > with what you've done?
 > 
 > More than that - All I can add to this is a C++ wrapper of the ORBit
 > TypeCode to create a C++ TypeCode implementation. John's implementation of
 > Any is way beyond what I've got done so far.
 > 
 > I'm attaching my TypeCode implementation as a patch to orbitcpp_orb.{cc,hh}
 > and two new files: orbitcpp_typecode.{cc,hh}.
 > John, you might like to use this C++ wrapper implementation of TypeCode in
 > your Any implementation. I don't know if it's necessary or even useful.
 > 
 > The compiler still won't generate the appropriate C++ TypeCode constants
 > for each generated type though.
 > -- 
 > Sam Couter          |   Internet Engineer   |   http://www.topic.com.au/
 > sa...@to...    |   tSA Consulting      |
 > PGP key available on key servers
 > PGP key fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C