> Garrett D'Amore wrote: > Having an old binary on Solaris stop working would, I think, be bad news.
But at the same time, to stop working that old binary would have to use a construct that has been explicitly documented to NOT necessarily work in Solaris (and before that SunOS) for at least 20 years. This strikes me as similar to the issue that occurs when a programmer moves from a system that has historically zeroed automatic variables as a side effect of its implementation to one that doesn't and their programs break (or alternatively, one that needed "-fwritable-strings" to avoid crashing when compiled with gcc.) I understand the argument for fixing this, but where do you draw the line in supporting code that broke because "undefined" happened to work in its favor in the past and no longer does? -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
