This is the mail archive of the
c++-embedded@sourceware.cygnus.com
mailing list .
Re: iostreams (was template bloat)
- To: "Embedded C++" <c++-embedded at cygnus dot com>
- Subject: Re: iostreams (was template bloat)
- From: "Kenneth Porter" <shiva at well dot com>
- Date: Thu, 27 Aug 1998 20:58:46 +0700
- Reply-To: "Kenneth Porter" <shiva at well dot com>
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!)