Bug 556 is "reconcile the windows and wine spec files." The point I think is make sure all windows APIs are listed, and listed correctly. I have a question... If a particular API has four different ordinals in four different windows versions, what goes in the spec file? You can see an example of what I mean here: http://24.229.94.2/cgi-bin/query.cgi?version=&status=&type=&ordi...
If the answer is simple enough I'll start working on the bug.
On a slightly related note, I relied on the wine spec files to build the apidb. I'm getting the idea now this wasn't quite the right approach, and it says some APIs are exported by wine when in fact they are not. Should I have used the .spec.def file instead?
------------------------------------- So many Right-wing Christians. So few lions.
On August 31, 2003 04:02 am, Dave Miller wrote:
If a particular API has four different ordinals in four different windows versions, what goes in the spec file?
I guess it doesn't matter, and it should go in with an automatic ordinal, that is '@'.
On Sun, 31 Aug 2003, Dave Miller wrote:
Bug 556 is "reconcile the windows and wine spec files." The point I think is make sure all windows APIs are listed, and listed correctly. I have a question... If a particular API has four different ordinals in four different windows versions, what goes in the spec file? You can see an example of what I mean here: http://24.229.94.2/cgi-bin/query.cgi?version=&status=&type=&ordi...
It means the API is not exported by ordinal. Such APIs are sorted in alphabetical order and just get whatever ordinal number corresponds from that order.