public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "K. Sinan YILDIRIM" <sinany@beko.com.tr>
Cc: Andrew Lunn <andrew@lunn.ch>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ECOS - MIPS
Date: Thu, 23 Jun 2005 09:02:00 -0000	[thread overview]
Message-ID: <20050623090215.GF12265@lunn.ch> (raw)
In-Reply-To: <200506231104.32693.sinany@beko.com.tr>

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

  parent reply	other threads:[~2005-06-23  9:02 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 [this message]
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                   ` [ECOS] " 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=20050623090215.GF12265@lunn.ch \
    --to=andrew@lunn.ch \
    --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).