public inbox for
 help / color / mirror / Atom feed
From: "P.J. Plauger"  <>
Subject: Re: iostreams (was template bloat)
Date: Fri, 28 Aug 1998 05:55:00 -0000	[thread overview]
Message-ID: <> (raw)

From: "Kenneth Porter" <>
To: "Embedded C++" <>
Date: Thu, 27 Aug 1998 20:58:46 +0700
Subject: Re: iostreams (was template bloat)

On Fri, 28 Aug 1998 10:34:39 +1000, Chris Johns wrote:

>iostream goes beyond just a printf replacement with type-safety. It
>allows all sorts of stream management and control to be performed. I see
>very little need for this in an embedded system.

Depends on the embedded system. You might not want it for a microwave
oven, but it would be handy in some network toasters like a router or
even an advanced VCR with web-based programming. Knowing the cost of
iostreams lets one decide whether it makes sense to use it for a given

How hard is it to factor iostreams so that one doesn't get more than
one needs?

[pjp]  It's much easier to factor Embedded C++, which is one of the main
reasons for defining that subset. For the size of embedded systems
contemplated by the EC++ Technical Committee, EC++ makes eminent

NEC Semiconductor Application Engineering Division reports
the following typical embedded code sizes:

Application      Current KB        Future KB

camera           48-64                96-256
rice cooker      16-48                64
celluar phone   384+                768+
printer             32-64               64-128
television         16-48              32-96
VCR               192-256           320+
HDD               32-64               64-128

             reply	other threads:[~1998-08-28  5:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-28  5:55 P.J. Plauger [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-08-28 19:08 Michael Bruck
1998-08-27 20:59 Kenneth Porter
1998-08-27 16:40 Kenneth Porter
1998-08-27 17:36 ` Chris Johns

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