linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@coritel.it>
To: Bernd Petrovitsch <bernd@firmix.at>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	Embedded Linux mailing list <linux-embedded@vger.kernel.org>,
	Alexander Neundorf <neundorf@eit.uni-kl.de>
Subject: Re: prevalence of C++ in embedded linux?
Date: Tue, 29 Jul 2008 10:35:02 +0200	[thread overview]
Message-ID: <488ED636.7090109@coritel.it> (raw)
In-Reply-To: <1217319612.24988.15.camel@spike.firmix.at>

Bernd Petrovitsch ha scritto:
> On Tue, 2008-07-29 at 09:51 +0200, Alexander Neundorf wrote:
>> On Tuesday 29 July 2008 09:40:20 Marco Stornelli wrote:
>>> Robert P. J. Day ha scritto:
>>>>   just curious -- how many folks are working in C++ in their embedded
>>>> linux work?
> 
> Not if it's in anyway avoidable.
> 
> [....]
>>> Like Linus Torvals said "...C++ is an horrible language" :)
>> If you avoid RTTI and exceptions and if you are handle templates and multiple 
>> inheritance carefully I see nothing which speaks against using it for 
>> embedded and real-time software.
> 
> That's the main reason for *not* using C++ in the embedded world in the
> first place.
> Tell people that they may use C++ and see them happy.
> Then tell them that you better not use templates, RTTI, exceptions and
> multiple inheritance if you want to boot from small space.
> 
> Yes, one *can* use the above features and get small features. But most
> people simply can't - if only that they use some tool/lib written in C++
> (and coming from the "normal" world) which simply uses them without
> thinking about space and wonder why the device won't run with "only"
> 128MB flash and run in 16MB RAM.
> 
> BTW why should I use C++ if I don't use any "fancy features"?
> 
> 	Bernd
I quite agree with you

-- 
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it

marco.stornelli@coritel.it
+39 06 72582838

  reply	other threads:[~2008-07-29  8:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 15:43 prevalence of C++ in embedded linux? Robert P. J. Day
2008-07-28 15:54 ` Chris
2008-07-28 15:55 ` Jamie Lokier
2008-07-28 16:15 ` Domenico Andreoli
2008-07-28 17:30 ` Matthias Kaehlcke
2008-07-28 21:47 ` Ben Nizette
2008-07-29  5:42   ` Roberto A. Foglietta
2008-08-02  4:14   ` Ben Nizette
2008-07-29  7:40 ` Marco Stornelli
2008-07-29  7:51   ` Alexander Neundorf
2008-07-29  8:20     ` Bernd Petrovitsch
2008-07-29  8:35       ` Marco Stornelli [this message]
2008-07-29  8:58       ` Alexander Neundorf
2008-07-29  9:47         ` Bernd Petrovitsch
2008-07-29 20:08           ` Leisner, Martin
2008-07-30  4:46             ` Bart Van Assche
2008-07-30 10:25               ` Jamie Lokier
2008-07-30 11:04                 ` Bart Van Assche
2008-07-30 11:58                   ` Haavard Skinnemoen
2008-07-30 12:38                     ` Jamie Lokier
2008-07-30 13:01                       ` Haavard Skinnemoen
2008-07-30 12:48                   ` Bernd Petrovitsch
2008-07-30 13:07                     ` Jamie Lokier
2008-07-30 13:58                       ` Bernd Petrovitsch
2008-07-30 10:16             ` Jamie Lokier
2008-07-29  8:50   ` Bart Van Assche
2008-07-29 11:39     ` Richard Danter

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=488ED636.7090109@coritel.it \
    --to=marco.stornelli@coritel.it \
    --cc=bernd@firmix.at \
    --cc=linux-embedded@vger.kernel.org \
    --cc=neundorf@eit.uni-kl.de \
    --cc=rpjday@crashcourse.ca \
    /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 NNTP newsgroup(s).