From: "Kenneth Porter" <shiva@well.com>
To: "Embedded C++" <c++-embedded@cygnus.com>,
"Jackie Chen" <jackie@stsl.siemens.com.tw>
Subject: Re: template bloat
Date: Wed, 26 Aug 1998 15:51:00 -0000 [thread overview]
Message-ID: <199808262251.SAA11529@mail1.ispnews.com> (raw)
On Wed, 26 Aug 1998 17:39:53 +0800, Jackie Chen wrote:
>Look at your mail about the template bloat, you mentioned the STL
>container is the good example for the template bloat.
>
>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.
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-26 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-26 15:51 Kenneth Porter [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-27 4:05 Michael Bruck
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=199808262251.SAA11529@mail1.ispnews.com \
--to=shiva@well.com \
--cc=c++-embedded@cygnus.com \
--cc=jackie@stsl.siemens.com.tw \
/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).