wine/ library/debug.c include/wine/library.h i ...

[Dimitrie O. Paun]

On January 3, 2003 12:45 pm, Alexandre Julliard wrote:
> The thing is that it's not only internal, it's useful in Winelib apps
> because there are no good debugging functions in the Windows API. And
> everybody I know who has tried to use the debug API in a Winelib app
> has been confused by the different names.

That includes me. But since we're not going to rename everything
(and this makes me so happy, I would have hate it if we did), the
confusion is still going to be there. People are still going to
have to learn that there is this mapping. But than, for magically
chosen, obscure functions, they will have to learn another rule!

Thing is, inconsistency always hurts more, even if done toward
a better goal. How can things be any easier in such a situation?
Furthermore, in this very case it's not clear at all to me we are
aiming at anything better. I have seen no project that uses this
long names for its debugging API. There are many reasons why not,
I will not hash them here, but this simple observation should tell
us something.

I stand by my suggestion of having a way of exporting the shorter
API independently of defining __WINE__.  99% of apps will be able
to use it as is, and they'll be a lot happier. Our own internal
apps will certainly be able to, and that's going to eliminate all
confusion. For the ones that can't use it, most likely they'll go
through the exercise of defining a shorter API anyhow, so nothing
is lost or made harder for them.

-- 
Dimi.