Re: Why, in Wine, are some unimplemented APIs not marked as stubs but instead commented out?

If it's a stub, applications that link to it but don't actually call it 
works. If it's commented out,
application might be able to handle its absence and fallback to other 
functions. Either way, if
a application actually calls the function, it fails. So for such cases, 
you would need to implement the function.


On 5/6/25 14:57, zhengxianwei wrote:
> This results in a situation where, due to the missing API, the program 
> doesn't report an error but instead directly aborts; whereas if it 
> were marked as a stub, it would produce a clear error
>
> eg: 
> https://github.com/wine-mirror/wine/blob/226a7eeabbc13345e49da1ff8c018d6f06211c66/dlls/user32/user32.spec#L805
>
> Does this involve some of wine's development philosophy?