From: "Michael Bruck" <mbruck@rft.de>
To: "Embedded C++" <c++-embedded@cygnus.com>
Subject: Re: template bloat
Date: Thu, 27 Aug 1998 04:05:00 -0000 [thread overview]
Message-ID: <01bdd1aa$6f94a520$0b1cafc1@gretel.ins-coin.de> (raw)
>>Do you have any experience about the STL using in an embedded
>>multi-tasking environment? Is it feasible or not-workable?
>
>Actually, I was speaking theoretically from a position of ignorance.
>:-)
>
>I would be curious to hear of any list members' experiences with STL as
>well. I've read lots about it in C++ Report but haven't any experience
>coding with it.
I know I have always negative examples ... but first thing I noticed when I
tried to use the STL for embedded modules was that there are some
places where it uses iostreams. (f.e. in the new operator). Thats why I
had to modify (means remove) some things to work without them. I have
not yet looked at the impact that it has on code size and placement.
>
>Ken
Micha
next reply other threads:[~1998-08-27 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-27 4:05 Michael Bruck [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-27 5:12 Jackie Chen
1998-08-27 6:23 ` Pete Becker
1998-08-26 15:51 Kenneth Porter
1998-08-25 17:50 Kenneth Porter
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='01bdd1aa$6f94a520$0b1cafc1@gretel.ins-coin.de' \
--to=mbruck@rft.de \
--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).