9 Mar
2015
9 Mar
'15
8:59 a.m.
I suppose if the API "changes" (and it means, it improves, and usually
without breaking backward compatibility), then there is no reason to
provide old, broken or incomplete implementation. I doubt there is any
popular app which relies on some bugs in old API implementation which
can justify that.
Regards,
Aleksey Bragin
On 07.03.2015 18:44, Pierre Schweitzer wrote:
(as it would be done for kernel32 nowadays). How do
you handle APIs that
would have slightly changed behavior between two Windows releases?
Duplicate code? Ignore previous behavior? That can also be seen: how do
you handle API that get extended over the time, supporting more and more
flags? One who can do the most, can do less?