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]

Re: kernel API


Jonathan Larmour <jifl at eCosCentric dot com> writes:

> Koeller, T. wrote:
> > [snip]
> > 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.
> 
> The problem is that we have to have flexibility to change how the kernel
> _implementation_ works, even if the _interface_ has to say the same. Right
> now the C++ stuff is just directly what is required by the implementation.
> Defining the internal API to be "official" will tie our hands unreasonably
> in the future if the API is to have any stability (and stability is one of
> the defining features of an API really!).

Besides, the C++ stuff has a rather boring deficiency. I do use C++ stuff
directly (through my own C++ wrappers), but I still can't find any reasonable
answer to the question why condvars and mutexes have been put into the same
header 'mutex.hxx'. I don't think anybody would expect to find a
'ConditionVariable' class in a 'mutex' header ;)

-- 
Sergei.


-- 
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]