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]

kernel API


Hi,

the question of which kernel API is the one officially
supported has been discussed before. As I remember,
the result of all those discussions was that only the
C API, as defined in kapi.h, has the status of an
officially supported API, and using the C++ kernel
API directly is discouraged.

The way that kapidata.h and thread.hxx declare the
same things in different ways and require both
declarations to always be in sync contradicts just
about everything that is generally considered good
programming practice ;-) It is IMO an ugly kludge, error-
prone and has indeed caused the very problems one would
expect during the transition from gcc-2.x to gcc-3.x.

Now everyone programming for eCos has a C++ compiler,
and I am quite sure that a significant number of us
code their applications in C++ (at least I do). In
this case using the C API only complicates things; I
get additional overhead and the above-mentioned
problems, but no benefits at all.

For all the reasons listed above, I am raising the
topic again. My proposal is to award the status of
an officially supported API to the C++ kernel API, too.

tk
----------------------------------------------- 
Thomas Koeller, Software Development 

Basler Vision Technologies 
An der Strusbek 60-62 
22926 Ahrensburg 
Germany 

Tel +49 (4102) 463-390 
Fax +49 (4102) 463-46390

mailto:Thomas dot Koeller at baslerweb dot com 
http://www.baslerweb.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]