This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: C++ API Reference manual


On Mon, Aug 12, 2002 at 10:42:56AM +0200, Martin Buck wrote:
> 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...

My customers who write their apps in C++ have also grumbled
when they found out that they're supposed to use the C API
rather than the C++ API.  IMHO, having a C++ API to a C++
kernel would be a nice differentiator for eCos.

[An aside on having the binary semaphore made available via the
C API: I've already argued in favor of that and lost.  Is eCos
more "open" now?

-- 
Grant Edwards
grante@visi.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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]