Closed Bug 10012 Opened 26 years ago Closed 26 years ago

Comparing on unsigned long to -1

Categories

(MailNews Core :: Database, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: slamm, Assigned: Bienvenu)

Details

Status: NEW → ASSIGNED
don't know why this would belong to mscott.
That's just where the cvsblame fell because of revision 1.40: Change m0id_scope to m_0id_id in order to fix the problem where the list of msg headers was always empty... David, should you be the owner then?
Assignee: mscott → bienvenu
Status: ASSIGNED → NEW
re-assigngint to bienvenu this is his puppy...
I've taken it, or at least I meant to. whoops. Taking it for real.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
fixed in nsMsgDatabase.cpp
QA Contact: lchiang → suresh
Target Milestone: M9
Suresh - do you know how to verify this?
I can verify this. I am waiting for a really good debug build.
David, I do not understand your fix. You are casting a negative number to an unsigned type? How does that work?
It works by fixing the warning. You'll notice in the mork code that whenever -1 gets assigned to the same variable I'm testing, the same cast happens.
Status: RESOLVED → VERIFIED
This no longer generates Build warning. Marking this as verified.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.