On 10/11/2012 7:52 PM, Wan-Teh Chang wrote:
NSPR public functions need to stay backward compatible. This means the prototypes of public functions and the definitions of public types cannot change. (There are exceptions, if done carefully.) Bugs in function behavior can certainly be fixed. Wan-Teh

I think the discussion that's currently going around the block with respect to NSPR is the entire PR types issue, particularly the fact that PRUint64 != uint64_t on some platforms (notably BSD). I do realize that changing this in NSPR carries backwards-compatibility issues that are important to manage, but I wonder if there is a way to let users of NSPR choose whether or not to have stdint-compliant definitions of PR types instead of the backwards-compatible variants.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to