jarl wrote: > I'm currently working on rewriting the BL sources so that they use OOP > C++ Corba code, and will use this specialised software > http://www.cs.utah.edu/flux/flick/ for IDL compilation. Flick looks like it does some cool stuff, but does it work with omniORB? >From a quick glance at the page and manuals, the only ORB implementation I see mentioned (that I recognize) is TAO. Won't you have to write a back end that works with omniORB. Or am I missing something about how Flick works? > Maybe we can make the autoconfigure so that it > tries to use Flick, and if it's not availeble it falls back on the default OMNIorb > idl compiler? Sure, I don't think should be too incredibly difficult. But, will Flick and omniidl generate stubs and skeletons that are interchangable enough to support this? Brad