From: "Richard Forrest" <richard@forrestit.com>
To: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] ECOS - MIPS
Date: Thu, 23 Jun 2005 16:19:00 -0000 [thread overview]
Message-ID: <opsstzl6uzzf95a8@localhost.localdomain> (raw)
In-Reply-To: <200506231325.41733.sinany@beko.com.tr>
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 <sinany@beko.com.tr>
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
next prev parent reply other threads:[~2005-06-23 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <W646741726646371119364845@webmail3>
2005-06-22 7:09 ` K. Sinan YILDIRIM
2005-06-22 10:21 ` Fabian Scheler
2005-06-22 18:28 ` L D
2005-06-23 6:29 ` K. Sinan YILDIRIM
2005-06-23 7:03 ` Andrew Lunn
[not found] ` <200506231102.17394.sinany@beko.com.tr>
2005-06-23 8:07 ` K. Sinan YILDIRIM
2005-06-23 8:34 ` Jerome Souquieres
2005-06-23 9:02 ` Andrew Lunn
2005-06-23 10:27 ` K. Sinan YILDIRIM
2005-06-23 15:28 ` [ECOS] " Grant Edwards
2005-06-24 6:14 ` K. Sinan YILDIRIM
2005-06-24 9:07 ` Nick Garnett
2005-06-24 14:08 ` Grant Edwards
2005-06-24 14:52 ` K. Sinan YILDIRIM
2005-06-24 16:39 ` Grant Edwards
2005-06-23 16:19 ` Richard Forrest [this message]
2005-06-24 0:04 ` Grant Edwards
2005-06-24 7:48 ` Richard Forrest
2005-06-23 15:17 ` Grant Edwards
2005-06-21 13:40 [ECOS] " K. Sinan YILDIRIM
2005-06-21 13:53 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=opsstzl6uzzf95a8@localhost.localdomain \
--to=richard@forrestit.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=sinany@beko.com.tr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).