- Darren Hiebert wrote:
> Dominique Colnet wrote:A similar situation arises in BeOS, where there is no alternative but to
> > > - When is C++ support planned for the "external" clause?
> > This is not planned at all.
> > One raison is that you can call C++ code from an ordinary C function.
> I cannot agree that this reasoning is sufficient. If one wishes to call a
> C++ library from Eiffel, the above reasoning leaves no choice but to write
> additional code in yet a third language to support the interface, further
> increasing the risk of coding errors in a language which not more prone to
> them, but also provides no support for Design By Contract. It would be far
> more convenient and safer to simply write all the code in Eiffel (up until
> the library call).
> Because Fox is a C++ library, you can imagine how daunting a task I
> consider it to have to write a C wrapper around every single class member
> function which I wish to have access to, essentially doubling the amount
> of interface code I would have to write.
interface with C++ classes to do anything. (I havent yet looked at the
latest SWIG to see if it can help here.) I embarked on an initial attempt to
write intermediate glue, but its currently on "back-burner" status.
Is anyone doing anything with CORBA and SE?