On Wed, 21 Feb 2007 15:04:57 -0500 James Carlson wrote: > I think that's still missing the point.
> This project is integrating ksh93 into ON. Once that's done, there's > no way that the ON source will be used to build a binary for some > other release. Having Solaris-versioning-dependent objects in the > deliverables is a syntax error. the point is the mechanisms to deal with binary differences exist upstream and outside of solaris and they won't be ripped out just for solaris you know the drill there's no such thing as a quick little comparmentalized change this is especially true for software that molds itself to different sw/hw architectures its fine for ON to believe its the only platform but don't expect that to affect ast source in the form of code removal we're willing to (and have already done so) abstract solaris/ON specific workarounds to generic features that can be probed on all systems we never maintain separate sources and we very reluctantly #ifdef on vendor specific symbols (and even then mostly to workaround bugs like bad code generation) -- Glenn Fowler -- AT&T Research, Florham Park NJ --
