From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2980 invoked by alias); 23 Jun 2005 08:07:36 -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 2363 invoked by uid 22791); 23 Jun 2005 08:07:28 -0000 Received: from mss3.koc.net (HELO mss3.koc.net) (193.243.207.68) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 23 Jun 2005 08:07:28 +0000 Received: from smtp01a.aspkoc.net ([195.87.204.31]) by mss3.koc.net with InterScan Messaging Security Suite; Thu, 23 Jun 2005 11:07:15 +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 11:06:29 +0300 From: "K. Sinan YILDIRIM" To: Andrew Lunn Date: Thu, 23 Jun 2005 08:07:00 -0000 User-Agent: KMail/1.5 Cc: ecos-discuss@sources.redhat.com References: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> <20050623070257.GB26538@lunn.ch> <200506231102.17394.sinany@beko.com.tr> In-Reply-To: <200506231102.17394.sinany@beko.com.tr> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506231104.32693.sinany@beko.com.tr> Subject: Re: [ECOS] ECOS - MIPS X-SW-Source: 2005-06/txt/msg00218.txt.bz2 i wont make it configurable with make files. i would use object oriented configurabilitiy. just inspect Java. you register classes, you program for interfaces, you use abstract classes. just inspect bridge or adapter pattern. you will understand me. > Per=C5=9Fembe 23 Haziran 2005 10:02 =C3=B6=C3=B6 tarihinde, Andrew Lunn = =C5=9Funlar=C4=B1 yazm=C4=B1=C5=9Ft=C4=B1: > > On Thu, Jun 23, 2005 at 09:27:32AM +0300, K. Sinan YILDIRIM wrote: > > > People may have positive and negative comments about a SW product. Do= es > > > this group for only positive ones ? Or only positive questions ? > > > > > > I have been writing SW for about 10 years. I have just examined eCOS > > > and found that it is configurable on some way and unconfigurable ( ha= rd > > > to reconfigure ) on some way. May be it is much more configurable than > > > the existing ones but not a super really configurable OS. > > > > > > I am the user. This is a user point of view . Having a seperate HAL > > > layer or a structured file tree doesnt make an operating system really > > > configurable. Configurability means to change the operating system > > > according to your needs in a quick way : not being able to change it = in > > > a month... > > > > > > configurable modern SW is done with SW patterns. Architectural and > > > Design patterns makes SW configurable, easy to change, etc... Embedded > > > SW needs good architectural design with really reusable architectural > > > and design patterns. What makes JAVA popular is these points. It is a > > > programming framework that fullfills these points. > > > > > > eCOS is not a really framework. When you read the documentation, it > > > seems to be an OS framework but indeed it doesn't. > > > > > > What i try to mean is we must make it better in order to make it usab= le > > > in the future. > > > > Could you give some examples of what you would change? > > > > 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