On 12/19/11 07:44, Aaron Faanes wrote:
My plan is to put codecvt stuff in a new dlls/msvcp90/codecvt.c file,
with header definitions in msvcp90.h. Is this a good idea, or should
it go elsewhere?
I would probably add it to locale.c file.
If I do put them in a new file, should I put myself as th
On Sun, Dec 18, 2011 at 4:39 AM, Piotr Caban wrote:
> On 12/17/11 10:10 PM, Aaron Faanes wrote:
>>
>> I agree that the locale stuff should come first. Would implementing the
>> stubs in dlls/msvcp90/locale.c be a good place to start?
>
> I'm working on implementing collate and ctype classes. You
On 12/17/11 10:10 PM, Aaron Faanes wrote:
I agree that the locale stuff should come first. Would implementing
the stubs in dlls/msvcp90/locale.c be a good place to start?
I'm working on implementing collate and ctype classes. You can pick
some other locale facet classes to implement (e.g. codec
On Sat, Dec 17, 2011 at 6:29 AM, Piotr Caban wrote:
> 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
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 clas
Howdy!
I ran into this bug when running a game of mine, and it seemed doable
for me. The bug is due to msvcp90 missing its file I/O stuff. Here's
the link:
http://bugs.winehq.org/show_bug.cgi?id=25966
My intention is to implement these classes as wrappers of ntdll's file
I/O API. Is this the rig
