From: Andrew Lunn <andrew@lunn.ch>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] eCos C++ API
Date: Wed, 21 Mar 2007 08:29:00 -0000 [thread overview]
Message-ID: <20070321082937.GD28547@lunn.ch> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2007-03-21 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 0:45 Paul D. DeRocco
2007-03-21 8:29 ` Andrew Lunn [this message]
2007-03-21 9:28 ` [ECOS] " Sergei Organov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070321082937.GD28547@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=pderocco@ix.netcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).