Should include files be bug for bug compatible?

[Alexandre Julliard]

Dylan Smith <dylan.ah.smith at gmail.com> writes:

> In richedit.h CHARFORMAT2[AW] is padded differently on the Windows
> PSDK depending on whether it is included for a c or c++ source file.
>
> Should the include file be fixed, or does bug for bug compatibility
> mean that a correct CHARFORMAT2 structure should be declared in a
> private include file?

It's OK to fix the include to reflect what the actual dll expects, as
determined by test cases. The test cases themselves will have to work
around it so that they can work with either header.

-- 
Alexandre Julliard
julliard at winehq.org