Closed
Bug 401298
Opened 17 years ago
Closed 17 years ago
Including jsapi.h generates many warnings with certain compiler configurations (e.g. gcc 3.4 -Wstrict-prototypes)
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla1.9beta2
People
(Reporter: wes, Assigned: wes)
Details
Attachments
(1 file)
2.60 KB,
patch
|
mrbkap
:
review+
brendan
:
approval1.9+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 Build Identifier: jsapi.h head 3.162 jsapi.h is full if function prototypes with empty arguments. While an empty argument list in C++ means "no arguments", in C it means "any number of arguments" (think back to K&R declarations). In C89 and C99, this syntax is deprecated and generates warnings when using gcc -Wstrict-prototypes and almost certainly other C89 or C99 compilers in verbose-warning modes. The general solution is to replace all function prototypes with empty arguments lists with function prototypes with EMPTY argument lists. i.e. int myfunc(); becomes int myfunc(void); This is conformant C89, C99 and C++98. http://david.tribble.com/text/cdiffs.htm [C99: §6.7.5.3] [C++98: §8.3.5, C.1.6.8.3.5] Reproducible: Always Steps to Reproduce: 1. Embed spidermonkey in a C program 2. Compile your program with gcc -Wall -Wstrict-prototypes 3. Observe the warning messages Expected Results: Built without warnings.
Assignee | ||
Comment 1•17 years ago
|
||
Comment 3•17 years ago
|
||
Who will land? I've whinged before about not putting JS_STATIC_ASSERTS in header files -- it's a modularity killer. /be
Keywords: checkin-needed
Comment 4•17 years ago
|
||
(In reply to comment #3) > Who will land? I've whinged before about not putting JS_STATIC_ASSERTS in > header files -- it's a modularity killer. Sorry, this was for bug 401300. /be
Comment 5•17 years ago
|
||
I'm not sure why this bug is checkin-needed. There aren't any reviews on the patch at all, and it does not have approval. Am I missing something?
Assignee: general → wes
Comment 6•17 years ago
|
||
Comment on attachment 286333 [details] [diff] [review] Unified Diff of proposed patch against revision 3.162 Reed, I thought Blake had stamped his approval. /be
Attachment #286333 -
Flags: review?(mrbkap)
Comment 7•17 years ago
|
||
Please re-add the checkin-needed keyword once the patch has appropriate review(s) and approval(s).
Keywords: checkin-needed
Comment 8•17 years ago
|
||
Comment on attachment 286333 [details] [diff] [review] Unified Diff of proposed patch against revision 3.162 Sorry, I meant to but got distracted.
Attachment #286333 -
Flags: review?(mrbkap) → review+
Comment 9•17 years ago
|
||
Reed, would it have killed you to have left the keyword set for a few hours? Prolly :-P. /be
Keywords: checkin-needed
Comment 10•17 years ago
|
||
Uh, Brendan, this still can't be checked-in. This doesn't have approval at all, or is this NPOTB?
Updated•17 years ago
|
Attachment #286333 -
Flags: approval1.9+
Comment 11•17 years ago
|
||
Ok, I'll land this as soon as the tree reopens for general check-ins, unless you want to try to get this in before M9 (http://wiki.mozilla.org/TreeStatus).
Comment 12•17 years ago
|
||
Checking in js/src/jsapi.h; /cvsroot/mozilla/js/src/jsapi.h,v <-- jsapi.h new revision: 3.163; previous revision: 3.162 done
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9 M10
Updated•17 years ago
|
Flags: in-testsuite-
Flags: in-litmus-
You need to log in
before you can comment on or make changes to this bug.
Description
•