Closed
Bug 714563
Opened 13 years ago
Closed 13 years ago
Fix unused variable compiler warnings for Handle<T> class
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 713311
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(1 file)
1.55 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
I'm still getting warnings with gcc 4.6.1.
Attachment #585234 -
Flags: review?(bhackett1024)
Comment 1•13 years ago
|
||
Better compiler analysis is just going to uncover that, could we use something like this http://stackoverflow.com/questions/965093/selectively-disable-gcc-warnings-for-only-part-of-a-translation-unit ?
Updated•13 years ago
|
Attachment #585234 -
Flags: review?(bhackett1024) → review+
Comment 2•13 years ago
|
||
Comment on attachment 585234 [details] [diff] [review] patch Is there anything wrong with the old-fashioned |(void)a;| ?
Assignee | ||
Comment 3•13 years ago
|
||
Does that work? I used the scheme here because that's what Chrome does in their handle class.
Comment 4•13 years ago
|
||
I've used it lots of times in the past and I don't see any reason why it wouldn't work here.
Assignee | ||
Comment 5•13 years ago
|
||
I guess Luke already fixed this here: http://hg.mozilla.org/mozilla-central/rev/f0d76403ae9c
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 6•13 years ago
|
||
Yeah, that warning was annoying. I used (void)a.
You need to log in
before you can comment on or make changes to this bug.
Description
•