public inbox for
 help / color / mirror / Atom feed
From: Brendan Kehoe <>
Subject: some topics for discussion
Date: Fri, 26 Jun 1998 15:00:00 -0000	[thread overview]
Message-ID: <> (raw)

Hi!  I've been meaning to send this msg, to try to get conversation going on
some of the items that prompted the creation of this list.

It'd be really interesting to hear people's thoughts on:

  * what are the primary reasons that many embedded developers tend not to use 
    C++ for their applications or other programs?

  * which particular language features are commonly problematic for an
    embedded system?  e.g., the implementation of templates in some compilers
    can make code size difficult to accept, particularly for a system with a
    limited memory footprint.

  * if there are ways that exception handling can be used without too much
    runtime cost?

  * which tasks or bodies of code are very, very commonly implemented often
    for an embedded application, that might prove suitable to be part of a
    common C++ library to do the same?  (With abstraction as necessary.)

  * if there are optimizations that could be applied (but aren't yet, or are
    only in a limited sense) to compensate for the needs of an RTOS or
    similar environment?


Brendan Kehoe                                     
Cygnus Solutions, Sunnyvale, CA                                +1 408 542 9600

Web page:

             reply	other threads:[~1998-06-26 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-26 15:00 Brendan Kehoe [this message]
1998-06-26 22:33 ` Todd Hoff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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