Please report any other irregularities here.
Created attachment 319123 [details] [diff] [review] Proposed patch Update an old comment that's no longer accurate. Describe the caveats of using PR_FileDesc2NativeHandle.
Attachment #319123 - Flags: review?(nelson)
Comment on attachment 319123 [details] [diff] [review] Proposed patch r=nelson >+** If you use this function, you need to understand what NSPR does to >+** the native handle. For example, NSPR puts native socket handles in >+** non-blocking mode or associates them with an I/O completion port (the >+** WINNT build configuration only). Your use of the native handle should >+** not interfere with NSPR's use of the native handle. I might suggest making a stronger statement, e.g. If your code changes the configuration of the underlying native socket, (e.g. changes it to blocking, or binds it, or closes it) NSPR will not work correctly.
Attachment #319123 - Flags: review?(nelson) → review+
Created attachment 319236 [details] [diff] [review] Proposed patch (as checked in) Thank you for the suggestion, Nelson. I added that sentence to the comment. I checked in the patch on the NSPR trunk (NSPR 4.7.2). Checking in pprio.h; /cvsroot/mozilla/nsprpub/pr/include/private/pprio.h,v <-- pprio.h new revision: 3.17; previous revision: 3.16 done
Attachment #319123 - Attachment is obsolete: true
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 4.7.2
You need to log in before you can comment on or make changes to this bug.