On 10/13/2012 09:14 AM, Alexandre Julliard wrote:
Max TenEyck Woodbury m...@mtew.isa-geek.net writes:
Now, if you are going to tell me that these definitions were *copied*
from a Microsoft *source* rather than derived from a Microsoft
specification, you would have a point, but then there would be a whole
bunch of copyright issues that would need to be worked through.
You can't copyright a typecast, and yes, the macros are broken the same
way in the Microsoft headers, we are just being compatible.
Ah, but you CAN copyright a MISTAKE! Especially if it was introduced
deliberately for the sake of catching copyright infringers. Since it
is gratuitous, like a grace note in a musical score, it can be used to
show the code was actually copied rather than being something needed to
implement the uncopyrightable idea in a specification.
Please apply the change. If you have any doubts, check with a
*copyright* lawyer. Reference the recent Oracle vs Google case.
