On Sat, Oct 13, 2012 at 3:25 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com>wrote:
> In some cases in the past (such as bug 563082), we've needed to change the > semantics of some of the NSPR functions to make them work better for some > things, such as more precise time measurements, but we've had to implement > our own APIs (e.g., > http://mxr.mozilla.org/mozilla-central/source/xpcom/ds/TimeStamp_windows.cpp) > which we've since heavily optimized (for example, in bug 784859). Would > such improvements be interesting to NSPR? I guess in a lot of cases we > just don't know whether NSPR would accept a patch if we make one, so we end > up implementing our own APIs. > One thing is that most of our new library APIs tend to be C++ and NSPR is a C library. I don't think we would want to restrict new APIs to C just so they could be folded into NSPR. (TimeStamp and Mutex, for example, really benefit from being C++ APIs.) Rob -- “You have heard that it was said, ‘Love your neighbor and hate your enemy.’ But I tell you, love your enemies and pray for those who persecute you, that you may be children of your Father in heaven. ... If you love those who love you, what reward will you get? Are not even the tax collectors doing that? And if you greet only your own people, what are you doing more than others?" [Matthew 5:43-47] _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
