RE: [ros-kernel] Prototype conflicts in current wine port

[Steven E. <Ste...@ya...>]

> Since this is a standard C runtime library function, I 
> consider the MinGW to be more correct. LPCWSTR etc. are WinNT 
> types, not stdc types. Does the WINE team have a problem with 
> changing their stdc prototypes?

The solution that Alexandre will accept for the
Wine tree is this: 

> I think the right way would be to put that functionality in 
> libwine_unicode, and follow the naming convention that we are 
> using there (for instance wcstol would be strtolW). This way 
> we are sure the prototypes won't conflict.

This most likely will be the law of the land unless you can change
Alexandre's mind. <g>

I will be starting bugs in wine's bugzilla when ever I find a 
Prototype conflict. This may be a case where the ReactOS projects 
Wine tree will differ. Right now I just want to get the damn thing 
Built right on mingw and I doubt I can make all of the changes that 
are needed anyway.

As of right now if we were to do a import of the wine tree the only 
Thing we would need to change is this, a few other prototypes and 
The debugging interfaces for the wine tree. The wine resources are 
no longer a issue nor is most of the mingw buggy-ness (Thanks again
Alexandre). 
I have only two small patches to mingws basetsd.h and windef.h 
to shutup some warnings. I will be submitting a TODO doc in the 
Next few days to outline where we are at and what is left to do.

Once again none of this really matters for us without simple windowing
(Hint,Hint)

Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson