* [ECOS] C++ kernel API @ 1998-12-04 10:08 Stuart Adams [not found] ` < 36682548.6C5DE767@brightstareng.com > 0 siblings, 1 reply; 2+ messages in thread From: Stuart Adams @ 1998-12-04 10:08 UTC (permalink / raw) To: ecos-discuss Is there an plan to support/document a C++ kernel API ??? (Since the underlying implementation is C++ it should simple right ?) -- Stuart ----------------------------------------- Stuart Adams Bright Star Engineering Inc. 19 Enfield Drive Andover MA 01810 USA Tel: +1-978-470-8738 Fax: +1-978-470-8878 Email: sja@brightstareng.com Web: http://www.brightstareng.com/ ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: < 36682548.6C5DE767@brightstareng.com >]
* [ECOS] Re: C++ kernel API [not found] ` < 36682548.6C5DE767@brightstareng.com > @ 1998-12-05 10:56 ` Bart Veer 0 siblings, 0 replies; 2+ messages in thread From: Bart Veer @ 1998-12-05 10:56 UTC (permalink / raw) To: sja; +Cc: ecos-discuss >>>>> "Stuart" == Stuart Adams <sja@brightstareng.com> writes: Stuart> Is there an plan to support/document a C++ kernel API ??? Stuart> (Since the underlying implementation is C++ it should Stuart> simple right ?) Actually, if you want to do things properly then it is usually more difficult to publish a C++ API then a C one. Depending on exactly how you set about doing it, for example how much functionality will be available in the form of inline functions, a C++ API tends to expose much more of the implementation details than an equivalent C API. Such implementation details then have the unfortunate habit of sneaking into application code. As a result it would be more difficult for us to move the system forwards without breaking existing code. There are certainly plans for a C++ kernel API, but we want to get it right. Or at least as close to "right" as we can make it. People who want to program entirely in C++ right now can do so by looking at the header files - usually there will be an obvious correspondence between the C++ classes and the published C API - but there is an increased risk that the application code will need to be updated as the system evolves. Bart Veer // eCos net maintainer ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-12-05 10:56 UTC | newest] Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 1998-12-04 10:08 [ECOS] C++ kernel API Stuart Adams [not found] ` < 36682548.6C5DE767@brightstareng.com > 1998-12-05 10:56 ` [ECOS] " Bart Veer
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).