From: bonnardv@pratique.fr (Valentin Bonnard)
To: c++-embedded@cygnus.com
Subject: wide streams in EC++
Date: Sat, 26 Sep 1998 20:38:00 -0000 [thread overview]
Message-ID: <v01530502b2335c224b5c@[195.68.3.34]> (raw)
>[pjp] Bet you didn't know that a fully conforming Standard C++ Library defines
>*four* wide-stream objects in <iostream>,
Well, I know that, but I also know that you weren't talking to me.
>along with the four better-known
>char-based stream objects. And given the bizarre initialization requirements
>for these eight objects, it's rather difficult to eliminate all code for these objects
>*even if they're not used in the program.*
Well, it's certainly possible for the compiler to deal with that but
I trust you that w/o any compiler support it might be quite difficult
for the library writer.
>That's one way in which the mere
>presence of a feature in a specification can quietly cost you even when you
>make no specific use of the feature.
Well, here the problem seems to be with initialisation problems.
Why didn't you relaxed the 'bizarre' initialisation rules instead
of removing wios and all (ok, I know, you didn't _removed_ anything,
you didn't made wios mandatory) ?
It seems to me that:
- many (not all of course) embeded devices can be/are localised
- wchar_t makes it possible or at least easier to write portable
localised applications
Valentin Bonnard mailto:bonnardv@pratique.fr
info about C++/a propos du C++: http://pages.pratique.fr/~bonnardv/
next reply other threads:[~1998-09-26 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-26 20:38 Valentin Bonnard [this message]
1998-09-30 9:56 P.J. Plauger
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='v01530502b2335c224b5c@[195.68.3.34]' \
--to=bonnardv@pratique.fr \
--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).