On 12/16/11 11:18 PM, Aaron Faanes wrote:
The bug is due to msvcp90 missing its file I/O stuff.
There's a lot of classes/functions that io classes depends on. My
current goal is to implement cout in msvcp90, in order to do it I need
to add support for locales first (there's still around 40 classes to
implement before it's done).
You can start implementing functions that don't depend on missing
functionality, but I think it's better to implement the functionality it
depends on first.
My intention is to implement these classes as wrappers of ntdll's file
I/O API. Is this the right approach, or is there another API that is
more preferable?
Streams behaviour may be affected by msvcrt related settings. If so you
will need to use msvcrt io functions. It should be quite easy to check
by e.g. locking stdout in msvcrt and trying to write to it using c++
functions.
