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


Sergei Organov wrote:
Nick Garnett <nickg at eCosCentric dot com> writes:


Sergei Organov <osv at javad dot ru> writes:

[...]


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 ;)


The implementations are in the same file, so they also share a header.

IMHO that's also a mistake though I don't care much where implementations are. I don't like the situation when all source files that use mutexes but don't use condvars are polluted with the condvars declarations.

I think you mean it might be a mistake if it was an official API ;-P. Although "polluted" is overstating it anyway. Namespacing is something unfortunately eCos has been very very lax about. Just try and declare "int interrupt_end;" in any application at least!


Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


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