Alan DuBoff wrote: >>> This would allow us to use the libCstd.so from Sun, right? >> I did ask -- the problem is that making libCstd.so 100% Standard compliant >> will break binary compatibility. Studio 12 itself is very close to being >> 100% >> Standard compliant. libCstd.so is not, because it must stay compatible with >> older versions of Workshop/Forte/Studio, going back to Workshop 5. > > I would fear we put ourselves into a similar situation as having > incompatible ABIs between SunStudio and gcc. I'm not sure that's a good > situation for us to be in. Not that I have a solution to the problem, but > it doesn't seem to solve the heart of the problem at hand, rather create > one of it's own.
I don't have a solution either ... but I've been thinking: can't we have a new *revision* of libCstd.so? I know far too little about libs and linking to know whether this is feasible, but couldn't "old" apps stick with "old" libCstd.so and newer ones with the new one - maybe have some linking glue that knows about versions, etc? Michael -- Michael Schuster Sun Microsystems, Inc. recursion, n: see 'recursion'
