From: "Kenneth Porter" <shiva@well.com>
To: "Embedded C++" <c++-embedded@cygnus.com>
Subject: Re: iostreams (was template bloat)
Date: Thu, 27 Aug 1998 20:59:00 -0000 [thread overview]
Message-ID: <199808280400.AAA23501@mail1.ispnews.com> (raw)
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
application.
How hard is it to factor iostreams so that one doesn't get more than
one needs?
Ken
mailto:shiva@well.com
http://www.well.com/user/shiva/
http://www.e-scrub.com/cgi-bin/wpoison/wpoison.cgi (Death to Spam!)
next reply other threads:[~1998-08-27 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-27 20:59 Kenneth Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-28 19:08 Michael Bruck
1998-08-28 5:55 P.J. Plauger
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:
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=199808280400.AAA23501@mail1.ispnews.com \
--to=shiva@well.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).