From: Andrew Lunn <andrew@lunn.ch>
To: Yi Tang <yitang@itee.uq.edu.au>
Cc: eCos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] ecos kernel modification and kapidata
Date: Fri, 07 Sep 2007 09:19:00 -0000 [thread overview]
Message-ID: <20070907091910.GJ32192@lunn.ch> (raw)
In-Reply-To: <000501c7f10a$81073a50$82406682@itee.uq.edu.au>
> Another question is: can I directly call the c++ api of the kernel in
> application instead of the C KAPI? And do you have any document relative to
> this native C++ API?
There is nothing to stop you calling the C++ API, but we don't
recommend it. The C API is documented and frozen. The C++ is not
documented and not frozen, it can and does change.
So we reserve the right to break your application if you use the C++
API :-)
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-09-07 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 4:49 Yi Tang
2007-09-07 9:19 ` Andrew Lunn [this message]
2007-09-07 11:32 ` Paul D. DeRocco
2007-09-07 12:57 ` Nick Garnett
2007-09-07 9:32 ` Andrew Lunn
2007-09-11 14:22 ` Yi Tang
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=20070907091910.GJ32192@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=yitang@itee.uq.edu.au \
/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).