Re: [ECOS] ECOS - MIPS

["K. Sinan YILDIRIM" <sinany@beko.com.tr>]

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.

Perşembe 23 Haziran 2005 12:02 ös tarihinde, Andrew Lunn şunları yazmıştı: 
> On Thu, Jun 23, 2005 at 11:04:32AM +0300, K. Sinan YILDIRIM wrote:
> >  i wont make it configurable with make files. i would use object oriented
> >  configurabilitiy.  just inspect Java.
>
> So you are talking about using run time configurability?
>
> Does this mean that every application must contain all of eCos? Java
> works this way as far as i know. You must have all of Java available
> because you never know what parts of it the application may use. Does
> such a system make sense with a deeply embedded system where i have
> limited memory and no secondary storage?
>
> > you register classes, you program for interfaces, you use abstract
> > classes.
> >
> > just inspect bridge or adapter pattern. you will understand me.
>
> Actually, i don't. I've never used patterns as such. Its a relatively
> new name to what i suspect are old ideas. So please could you explain
> these patterns and how they are appropriate to extreamly small memory
> systems?
>
>         Thanks
>                 Andrew


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