Re: [ECOS] C++ API Reference manual

[Nick Garnett <nickg at ecoscentric dot com>]

Martin Buck <martin.buck@ascom.ch> writes:

> Nick Garnett wrote:
> > Good work, but be careful. There is no guarantee that the C++
> > interface will remain constant. It was designed as an internal
> > interface for use by the components of eCos
> 
> Any chance to change this in the future? We've used eCos in a C++
> project and we wrote a C++ wrapper around eCos' C wrapper around the
> internal C++ API. Yes, it works, but it's far from elegant if you ask
> me...
> 

This is unlikely to change, flexibility at this level has proven to be
very useful and I would be reluctant to lose it.

Any "official" C++ API would probably be very similar to what you have
already done. But so long as it is implemented as a set of classes
with inline methods, it should have no runtime impact. 

-- 
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss