Closed Bug 154 Opened 27 years ago Closed

warning fix : ns/nsprpub/pr/src/threads/prtpd.c

Categories

(NSPR :: NSPR, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rick, Assigned: wtc)

Details

Created by Rick Osborne (rick@rixsoft.com) on Sunday, April 12, 1998 6:14:28 PM PDT Additional Details : (In the continuing quest to eliminate even compiler warnings ... ) This was a pleasant switch.  Just some nice *normal* unreferenced vars, instead of these no-fun compiler directive problems.  Oh well. --- prtpd.c     Sun Apr 12 02:01:03 1998 +++ prtpd.old.c Wed Apr 08 17:55:09 1998 @@ -126,4 +126,3 @@ PR_IMPLEMENT(PRStatus) PR_NewThreadPriva          PRThreadPrivateDTOR *old = NULL; -        /* unreferenced - why is this here? */ -        /* PRIntn _is; */ +               PRIntn _is; @@ -194,4 +193,3 @@ PR_IMPLEMENT(PRStatus) PR_SetThreadPriva      { -        /* Why is this here? */ -        /* PRIntn _is; */ +               PRIntn _is; Updated by Wan-Teh Chang (wtc@netscape.com) on Friday, April 24, 1998 12:40:07 PM PDT Additional Details : Assigned bug to myself. The _is variables in this file may still be referenced on some platforms. See the definition of these two macros at the beginning of the file prtpd.c: #define _PR_LOCK_TPINDEX() _PR_INTSOFF(_is) #define _PR_UNLOCK_TPINDEX() _PR_INTSON (_is)
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Wan-Teh, these are some pretty old bugs. i can't help but assume they have been fixed by now. If you don't have any objections, i will close out and verify these bugs in a couple of days: 146, 148, 149, 150, 151, 152, 154
please take corrective action if this is not doing the Right Thing, but, as it has been a while, i'm marking these fixed and will immediately verify: bugs 146, 148, 149, 150, 151, 152, 154
Status: RESOLVED → VERIFIED
verified.
NSPR now has its own Bugzilla product. Moving this bug to the NSPR product.
You need to log in before you can comment on or make changes to this bug.