From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29274 invoked by alias); 24 Jun 2005 06:14:50 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 29236 invoked by uid 22791); 24 Jun 2005 06:14:43 -0000 Received: from mss3.koc.net (HELO mss3.koc.net) (193.243.207.68) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 24 Jun 2005 06:14:43 +0000 Received: from smtp01a.aspkoc.net ([195.87.204.31]) by mss3.koc.net with InterScan Messaging Security Suite; Fri, 24 Jun 2005 09:14:27 +0300 Received: from 10.254.1.131 ([81.8.18.4]) by smtp01a.aspkoc.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 24 Jun 2005 09:14:22 +0300 From: "K. Sinan YILDIRIM" To: Grant Edwards , ecos-discuss@ecos.sourceware.org Date: Fri, 24 Jun 2005 06:14:00 -0000 User-Agent: KMail/1.5 References: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> <200506231325.41733.sinany@beko.com.tr> <20050623152839.21EAE49B78@rivatek.dnsalias.net> In-Reply-To: <20050623152839.21EAE49B78@rivatek.dnsalias.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506240912.23039.sinany@beko.com.tr> Subject: Re: [ECOS] Re: ECOS - MIPS X-SW-Source: 2005-06/txt/msg00229.txt.bz2 SW is a different concept. You make code really faster but after 2 months = you=20 cannot improve it. Also you write it in a really maintanainable way, but it= =20 may consume too much space... vice versa...Modern SW is done with reusing t= he=20 architecture, not only reusing components or codes. There are plenty of=20 documents, you may read and learn. Embedded SW is behind the general PC=20 software. PC SW evolved so much, many problems are solved but embedded=20 systems are just popular and there are many problems to be solved. These=20 discussions are the result of this situation. I just mention that eCOS didnt fullfill my needs. The only thing eCOS provi= des=20 is using reusable components like the ones in visual programming languages. If u substract components, uCOS is much more usable than it if I compare it= =20 with eCOS. uCOs is small, deterministic etc... For example i may write=20 components to uCOS and then it becomes eCOS :P (just a joke...)=20 Just examine the books : + Real Time Design Patterns + Patterns for Small Memory Systems + Pattern Oriented SW Architecture .. they are the experiences of embedded SW developers. There are the things th= at=20 they know much better... I think Operating systems are the products that mu= st=20 live longer. If you want your SW to live longer, you must learn new SW=20 concepts, you must apply them... For example having an HAL layer as an architecture is not a new concept. Un= ix,=20 Linux and also Windows have HAL layers. Also HAL layer is a must for embedd= ed=20 systems. eCOS is written in C++ . You may use Bridge or Adapter pattern to= =20 build an HAL layer. ("Program for interfaces, not for the implementation" i= s=20 the main concept of modern SW. ) There are many operating systems that are done with C++. Have u ever examin= ed=20 them ? For example Chorus, L4, Amobea... etc. They have new ideas,they try = to=20 use new SW techniques. Per=C5=9Fembe 23 Haziran 2005 06:28 =C3=B6s tarihinde, Grant Edwards =C5=9F= unlar=C4=B1 yazm=C4=B1=C5=9Ft=C4=B1:=20 > In gmane.os.ecos.general, you wrote: > > 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. > > Right. > > > modern operating systems must modern software ideas and > > architecture. > > You're free to write your own. eCos suits my needs quite > nicely. > > > Pattern oriented architecture is not a new idea > > but none of the embedded operating systems uses them. > > Firstly, there might be a reason for that. We're not stupid, > you know. > > Secondly, I have no idea what you mean by "pattern oriented > architecture" can you point to a description? The things that > Google found were either describing ways to fail: > > Pattern oriented architecture - A trend that's found in > systems created by architects who've recently read and > digested books on architectural patterns and come to the > conclusion that implementing patterns (such as > front-controller, etc) is the key to a successful > architecture. Rather than determining if common patterns are > appropriate, and picking the most suitable one, all patterns > that can be applied are done so, on top of one another, > creating an entangled, schizophrenic system. > > or were marketing buzword-bullshit: > > A standards-based, pattern-oriented architecture that follows > industry best-practices assures that the NEFS will fit right > into your development environment. > > > 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. > > People have been saying that for 10 years. I stopped paying > much attention 5 years ago. Java requires MASSIVE amounts of > storage compared to eCos. > > > 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. > > OK. > > -- > Grant Edwards grante Yow! I own > seven-eighths at of all the artists in visi.com=20=20=20=20= =20=20=20=20=20=20=20 > downtown Burbank! -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss