On Feb 27, 2013, at 2:34 PM, pulkomandy@xxxxxxxxxxxxx wrote: > This means we will always be running in a kind of hybrid environment, where > the 'previous' and 'current' APIs will each be sandboxed in its own world. > Starting with gcc2/4 now allows us to spot most of the issues with doing that > and think about the solutions. 3rd-party developers should also learn how to > package their apps properly, because that knowledge will be useful for future > versions of Haiku as well. We may also have similar situations with x86 32/64 > bit hybrids, and maybe some other processors in the future. What's the advantage over the industry standard approach of symbol and type versioning? I understand why the gcc2/gcc4 split exists, but that's an unusual problem that nobody wants to repeat (or, afaik, has since). -landonf