> -----Original Message-----
> From: Aaron Ardiri [mailto:[EMAIL PROTECTED]]
...
> it is common that the API's are backward compatable.. so it does not
> hurt to build against 3.3 API's for 3.1 or 3.0 devices :> i dont
> clobber my include dirs.. however someone who wants to replace them
> can :>
>
Oh? They've changed their practices? It certainly
-used- to be the case that the headers were -not- backwards
compatible. That is, when OS3 headers came out, code for
OS2 using (for example) "CategoryEdit" would not compile.
Why? Because the CategoryEdit they had been expecting to use
had been renamed CategoryEditV20 and the new CategoryEdit
had a completely different prototype.
For backwards compatibility, the NEW one should have had
a new name and the old name should have continued to exist
unchanged.
Look through the docs -- see all the xxxV10 and xxxV20 functions?
All of those represent BREAKS in code backward compatibility.
So ... are you saying now that the 3.3 headers do not break
code written to the 3.1 headers? If so, huzzah and hooray
they've finally got it! If not .........
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
