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]

ECOS - MIPS



K. Sinan YILDIRIM


I am new to eCos and embedded programming and still have lots to learn about both. Probably like yourself I am experienced in *nix and Windows programming with boundless resources. My initial impressions were that the coding style in eCos was rather old fashioned. We are probably both used to the amazing things that can be done with STL, boost, template metaprogramming etc. However I realise that many of these libraries and techniques are not appropriate for embedded programming. On the other hand it is possible that some modern C++ techniques could be useful in this context. Currently I do not have enough experience of embedded programming to give an opinion.

Could you provide an example of how some part of eCos could be improved using a specific design pattern. This could form the basis of a more focused discussion of the benefits of what you are proposing. If your ideas are practical and would genuinely make eCos more easily configured then I am certain that the eCos maintainers would be very happy to help you incorporate them.

Richard Forrest





On Thu, 23 Jun 2005 13:25:41 +0300, K. Sinan YILDIRIM <sinany@beko.com.tr> wrote:

there are patterns for limited memory systems and real time systems. there are
papers, books... you can find them and read them.


patterns doesnt always mean run-time configurability. what u can do with
compile time can also be done with patterns.

patterns means reusability of the design and architecture. if u want your
opearting system to fullfill future requests, i must strongly suggest to use
them.the things that eCos uses is traditional C programming way of doing
reusability and maintainability.modern operating systems must modern software
ideas and architecture. Pattern oriented architecture is not a new idea but
none of the embedded operating systems uses them.


Java classes are dynamically loaded. Java will be a future for embedded
systems. Many companies started to use java. it has many benefits. If
performance problems are solved, Java will be a revolution for embedded
systems.

i am going to write an operating system with patterns and reusable
architecture. i will share it with you in the future when i finish.




--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]