public inbox for c++-embedded@sourceware.org
 help / color / mirror / Atom feed
From: Brendan Kehoe <brendan@cygnus.com>
To: c++-embedded@cygnus.com
Subject: biggest deterrant to using C++?
Date: Wed, 12 Aug 1998 10:44:00 -0000	[thread overview]
Message-ID: <13777.54370.844413.730830@lisa.cygnus.com> (raw)

I was curious what folks in the embedded development world might see as their
key persuasion to avoid using C++ for embedded applications.

Is it size?  Of particular features?  Is it Speed?  Perhaps general memory
footprint because of poor implementations (in some places) of certain
features, like templates or exception handling?  Other?

I've heard some discussion that one reason could be the number of embedded
programmers who are still using assembly language, or slowly moving up to C,
and see C++ as too far-reaching a learning curve.  Is that related?

Thanks,
B

             reply	other threads:[~1998-08-12 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-12 10:44 Brendan Kehoe [this message]
1998-08-14 10:18 Saffi Hartal
1998-08-14 16:04 Kenneth Porter
1998-08-17 16:43 Kenneth Porter
1998-08-23 18:37 Michael Bruck
1998-08-24 18:39 Kenneth Porter
1998-08-25 11:57 Michael Bruck
1998-08-25 18:04 Kenneth Porter
1998-08-26 10:38 Michael Bruck

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=13777.54370.844413.730830@lisa.cygnus.com \
    --to=brendan@cygnus.com \
    --cc=c++-embedded@cygnus.com \
    /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).