> The problem was that it lacked some stuff like sub-second timeout, > support for hexadecimal floating-point values etc. > [ ... ] > No clue. Main issue was to avoid code duplication, maintaince issues and > footprint.
As per my response to Garrett, that's hardly an inherent limitation. Were we really spending a lot of time maintaining sleep? I'd bet more time has been wasted on sleep-related matters in the past two weeks than in the last 20 years. > Erm... what exactly did cost too much ? The biggest problem so far is > that I was careless, stupid and kept my brain offline - otherwise I > would've noticed that I have to BFU my test system _twice_ (one time to > update to the ksh93-integration update1 tree and the 2nd time to test > BFU with the new codebase) instead of only once. That's causing all the > trouble right now, but we're cleaning up (and learned some lessions for > the next time). I'm more concerned about the random breakage like 6793120. This is a waste of time and effort. I fear I will be unable to convince you this was a mistake, so I'll stop now and move onto more fruitful pursuits. -- meem _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
