From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15337 invoked by alias); 23 Jun 2005 10:27:57 -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 15310 invoked by uid 22791); 23 Jun 2005 10:27:50 -0000 Received: from camlica-vw.koc.net (HELO mss1.koc.net) (193.243.207.66) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 23 Jun 2005 10:27:50 +0000 Received: from smtp01a.aspkoc.net ([195.87.204.31]) by mss1.koc.net with InterScan Messaging Security Suite; Thu, 23 Jun 2005 13:27:40 +0300 Received: from 10.254.1.131 ([81.8.18.4]) by smtp01a.aspkoc.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Jun 2005 13:27:39 +0300 From: "K. Sinan YILDIRIM" To: Andrew Lunn Date: Thu, 23 Jun 2005 10:27:00 -0000 User-Agent: KMail/1.5 Cc: ecos-discuss@sources.redhat.com References: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> <200506231104.32693.sinany@beko.com.tr> <20050623090215.GF12265@lunn.ch> In-Reply-To: <20050623090215.GF12265@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506231325.41733.sinany@beko.com.tr> Subject: Re: [ECOS] ECOS - MIPS X-SW-Source: 2005-06/txt/msg00221.txt.bz2 there are patterns for limited memory systems and real time systems. there = are=20 papers, books... you can find them and read them. patterns doesnt always mean run-time configurability. what u can do with=20 compile time can also be done with patterns.=20 patterns means reusability of the design and architecture. if u want your=20 opearting system to fullfill future requests, i must strongly suggest to us= e=20 them.the things that eCos uses is traditional C programming way of doing=20 reusability and maintainability.modern operating systems must modern softwa= re=20 ideas and architecture. Pattern oriented architecture is not a new idea but= =20 none of the embedded operating systems uses them. Java classes are dynamically loaded. Java will be a future for embedded=20 systems. Many companies started to use java. it has many benefits. If=20 performance problems are solved, Java will be a revolution for embedded=20 systems.=20 i am going to write an operating system with patterns and reusable=20 architecture. i will share it with you in the future when i finish. Per=C5=9Fembe 23 Haziran 2005 12:02 =C3=B6s tarihinde, Andrew Lunn =C5=9Fun= lar=C4=B1 yazm=C4=B1=C5=9Ft=C4=B1:=20 > 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 orient= ed > > 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