For more info, see http://www.kaply.com/work/callconv.html
The main reason for all of these changes is because we need to switch some
components to use _System instead of _Optlink calling convention so that
things are more compatible with the EMX build. For instance, you should in
theory be able to use an EMX NSPR with a VACPP build.
These changes are essentially fixing bugs in the way we did the CALLBACKs
originally.
We have been discussing the possibilty of actually making CALLBACK mean
something on other platforms so breakage is caught, but right now OS/2VACPP
is the only platform that shows the breakage.
My hope is that we can simply educate people as to where the CALLBACKs are
needed.
Mike Kaply
IBM
Barry Marshall wrote:
> A question to Mike and co.
>
> I've been reading through all of the bugs you've attached to the
> CALLBACK fixes that you've been putting into the builds. I think I
> understand what you're doing now by fixing these bustages, but my coding
> knowledge is very very old and weak now.
>
> Once all of these changes have gone through, will this force other
> contributors to get the CALLBACKs right before they submit patches the
> first time or will VACPP still always expose these types of problems and
> burp on them?
