public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: ECOS - MIPS
Date: Fri, 24 Jun 2005 00:04:00 -0000	[thread overview]
Message-ID: <20050624000348.F2D2E49B78@rivatek.dnsalias.net> (raw)
In-Reply-To: <opsstzl6uzzf95a8@localhost.localdomain>

In gmane.os.ecos.general, you wrote:

> My initial impressions were that the coding style in eCos was
> rather old fashioned.

Are you referring to the coding style (i.e. indentation,
variable names, etc.) or the actual architecture and design?

> 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.

Depends on the system.

> On the other hand it is possible that some modern C++
> techniques could be useful in this context.

Like what?  

Since eCos is the only RTOS kernel i know of written in C++, it
would appear it's leading the pack in using "some modern C++
techniques.  I'm no C++ expert, but the design and
implimentation of the eCos kernel looked pretty nifty what with
those objects and classes and whatnot.

Most of the drivers, OTOH, are pretty much what drivers always
are: nasty low-level C code.

Embedded systems development is just plain hard compared to
many other sorts of SW development.  It requires a lot of
knowlege about the platform hardware, the tools, and the
problem domain. There is no silver bullet.

> 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.

I'm certain they would. 

-- 
Grant Edwards                   grante             Yow!  LOU GRANT froze
                                  at               my ASSETS!!
                               visi.com            

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-06-24  0:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <W646741726646371119364845@webmail3>
2005-06-22  7:09 ` [ECOS] " 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                 ` [ECOS] " Richard Forrest
2005-06-24  0:04                   ` Grant Edwards [this message]
2005-06-24  7:48                     ` [ECOS] " Richard Forrest
2005-06-23 15:17             ` Grant Edwards
2005-06-24 15:04 Ali, Khurram

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=20050624000348.F2D2E49B78@rivatek.dnsalias.net \
    --to=grante@visi.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).