public inbox for
 help / color / mirror / Atom feed
From: Todd Hoff <>
Subject: Re: some topics for discussion
Date: Fri, 26 Jun 1998 22:33:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

It's in large part cultural. I came to the embedded world from writing
large apps on workstations. Most of the embedded software people were
more hardware oriented. We had very little in common. Fortunately
we could divide the work along the lines of hardware/ISR/driver and
the rest the software. OO and C++ were seen a slow, bloated, and

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

As exceptions haven't been thread safe so i really haven't had a chance
to consider this :-)

>   * 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?

A big issue is changing configurations on the fly without
rebooting. This is very difficult and is very common.

   Desperate measures require the invention of desperate times. 
      -- Todd Hoff

      reply	other threads:[~1998-06-26 22:33 UTC|newest]

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

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