From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12160 invoked by alias); 23 Jun 2005 16:19:21 -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 12140 invoked by uid 22791); 23 Jun 2005 16:19:13 -0000 Received: from smtp.e7even.com (HELO smtp.e7even.com) (83.151.192.5) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Thu, 23 Jun 2005 16:19:13 +0000 Received: (qmail 13147 invoked from network); 23 Jun 2005 16:19:07 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 23 Jun 2005 16:19:07 -0000 Received: from smtp.e7even.com ([127.0.0.1]) by localhost (gateway [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 11628-10 for ; Thu, 23 Jun 2005 17:19:06 +0100 (BST) Received: (qmail 13140 invoked from network); 23 Jun 2005 16:19:06 -0000 Received: from unknown (HELO localhost.localdomain) (83.151.202.178) by smtp.e7even.com with SMTP; 23 Jun 2005 16:19:06 -0000 Date: Thu, 23 Jun 2005 16:19:00 -0000 To: "K. Sinan YILDIRIM" 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> <200506231325.41733.sinany@beko.com.tr> From: "Richard Forrest" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <200506231325.41733.sinany@beko.com.tr> User-Agent: Opera M2/7.54 (Linux, build 955) Subject: [ECOS] ECOS - MIPS X-SW-Source: 2005-06/txt/msg00226.txt.bz2 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 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