Am Donnerstag, 30. April 2026, 19:41:53 Ostafrikanische Zeit schrieb David CF via Wine-Devel:
I was wondering whether it is OK to use information learned from this header to document the Wine API. I was also wondering whether it would be acceptable to patch some of the functions based on what I learned from this header.
Learning from headers is OK. Facts and interfaces aren't copyrightable or using them is fair use, depending on jurisdiction. What is NOT ok is copypasting from a copyrighted header. What is also NOT ok is looking at incompatibly licensed *implementations*. I sense that your concern is that you don't know how the header got into public view, and that it might be leaked code. Looking at leaked implementations would be a no-go, but a header shouldn't contain implementation code. My best guess is that the header came from an OS/2 SDK. Maybe you can find a more official source for it. The ideal approach is something like this: 1) You have a real world application that does not work with Wine's cabinet.dll 2) The documentation you found in this header offers an explanation of what the application needs 3) You write tests in dlls/cabinet/tests that demonstrate the behavior of the native DLL 4) You implement the behavior in Wine. Somewhere in step 3 or 4 you'll likely need additional defines. Add them to Wine's header by typing them yourself, but don't copypaste from Microsoft's header.