If the user compiles and links with -xoscompat=s9 (or whatever), then any interface not available in S9 provokes an error. This would require a small to moderate amount of goop in the headers and libraries, and some new interfaces in the linker (to enhance the version selection logic, and maintain "OS profiles" for different minor releases). It's all very doable. The question is how important is it.
--chris Peter Memishian wrote: > > The Sun Developer Tools organization and the Sun OS/Net organization > > should collaborate to create an environment where customers can > > reliably create applications on S10 that run on S9. This could be > > done with very few caveats in the resulting system. > > Really? It seems fundamentally unsupportable to me. As Jim mentioned, > none of our APIs are designed with this consideration in mind, nevermind > how the developer would know what S10-only[1] interfaces they need to > avoid (where interfaces include more than just function calls -- e.g., > revised structure definitions that are forward but not backward-compatible > would need to be considered, among many other issues). Further, from what > I've heard, S9 is not a particularly popular release, so S9->S10 seems a > strange place to focus. > > [1] That's making the massive oversimplification that S10 is a single > release. > > -- > meem > _______________________________________________ > tools-compilers mailing list > tools-compilers at opensolaris.org
