This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: eCos C++ API
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- Cc: eCos Discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 21 Mar 2007 09:29:37 +0100
- Subject: Re: [ECOS] eCos C++ API
- References: <01cf01c76b52$367b77a0$8d7ba8c0@PAULD>
On Tue, Mar 20, 2007 at 05:45:24PM -0700, Paul D. DeRocco wrote:
> Are the C++ objects on which eCos is based supposed to be invisible to the
> programmer, so that the designers of eCos can change them at will?
Correct. The only documented and stable API is the C API in
kapi.h. There is nothing to stop you using the C++ objects directly,
but the C++ objects have changed in the past, but not often, eg when
POSIX threads were added. We reserve the right to change the C++
objects. There is no documentation for the C++ objects except the code
itself. Only a few people know the C++ objects, so you will get little
support when you start asking questions.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss