Closed
Bug 178590
Opened 22 years ago
Closed 20 years ago
fix compiler warning in string/public/nsBufferHandleUtils.h
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: benjamin, Assigned: benjamin)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
787 bytes,
patch
|
jag+mozilla
:
review+
alecf
:
superreview+
|
Details | Diff | Splinter Review |
This is just a little patch that fixes a minor compiler warning in
string/public/nsBufferHandleUtils.h -- line 71 has an assignment inside an if().
Assignee | ||
Comment 1•22 years ago
|
||
-u patch
Comment 2•22 years ago
|
||
Which compiler?
I thought compilers would warn for
if ( foo = bar )
but not for
if ( (foo = bar) )
Regardless, there is nothing wrong with an assigment inside an if, it's nice
that the compiler tries to tell us we may have meant == instead of =, but I
don't think we need to make this change just to make some compiler not warn.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Summary: fix compiler warning in string/public/nsBufferHandleUtils.h → fix compiler warning in string/public/nsBufferHandleUtils.h
Assignee | ||
Comment 3•22 years ago
|
||
Compiler is MSVC6 (warning-level 4)
I normally don't care about warnings in mozilla source files, but this is a
header that I was including (through nsASharableString) in another application,
and getting warnings on each source file that included it.
Truly it doesn't make a big difference, but the change can't hurt, can it? I
thought that providing a patch might make it a painless fix ;)
Comment 4•22 years ago
|
||
Alec, dbaron, what do you two think?
It's a shame MSVC6 doesn't take the parentheses hint that this was really what
we meant and not a typo.
Making the change is ok with me. Just wait to check it in until something else
comes around that triggers a world-rebuild.
Comment 6•22 years ago
|
||
Comment on attachment 105288 [details] [diff] [review]
-u patch
sounds fine to me too. sr=alecf
Attachment #105288 -
Flags: superreview+
Assignee | ||
Comment 7•22 years ago
|
||
Reopening per comments. This is obviously not urgent, so it could wait even
until the 1.4 tree opening if need be.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 8•22 years ago
|
||
Comment on attachment 105288 [details] [diff] [review]
-u patch
r=jag
Attachment #105288 -
Flags: review+
Updated•22 years ago
|
Blocks: buildwarning
Assignee | ||
Comment 9•22 years ago
|
||
Mine, this will go in after 1.4
Assignee: jaggernaut → bsmedberg
Status: REOPENED → NEW
Priority: -- → P5
Target Milestone: --- → mozilla1.5alpha
Comment 10•21 years ago
|
||
Comment on attachment 105288 [details] [diff] [review]
-u patch
bsmedberg (or anyone):
Can you check in your r+/sr+ patch ? Thanks.
Comment 11•21 years ago
|
||
Retargeting: v1.5a -> v1.7a.
Severity: minor → trivial
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: mozilla1.5alpha → mozilla1.7alpha
Assignee | ||
Comment 12•20 years ago
|
||
This code has disappeared ;)
Status: NEW → RESOLVED
Closed: 22 years ago → 20 years ago
Resolution: --- → WONTFIX
Updated•20 years ago
|
Priority: P5 → --
Target Milestone: mozilla1.7alpha → ---
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•