Roland Mainz wrote:
Michael Shapiro wrote:
... lots ...
I just don't see the "why" here. Sure, one /could/ do all sorts of spiffy things at build time iff one could just use ksh93. But, I don't see anything in the ON tree today that /requires/ the use of ksh93. In the absence of a problem that forces the adoption of ksh93 /now/, I'd suggest that we keep our focus on getting the current ksh93 project finished and integrated before we invent more work. If needed, get a limited scope exception that allows the use of ksh93 as part of the ksh93-specific build process, but treat it as an implementation detail private to the ksh93 project. Being "done" with this phase of ksh93 /now/ is infinitely better than some theoretical "perfect" that is never achieved. Then, once we have a ksh93 in the system, we can entertain all these new ideas. -John _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
