RESOLVED WONTFIX 114596
Do not generate parameter names in WebKitIDL C++ bindings
https://bugs.webkit.org/show_bug.cgi?id=114596
Summary Do not generate parameter names in WebKitIDL C++ bindings
Victor Costan
Reported 2013-04-14 15:57:13 PDT
Currently, the C++ WebKitIDL code generator adds parameter names to the function declarations in headers. This upsets the WebKit style checker, so WebKitIDL changes that re-generate the bindings (as they should) automatically fail the style checks. This bug will receive a patch that removes the parameter names, to make life easier for future WebKitIDL changes.
Attachments
Patch (13.58 KB, patch)
2013-04-14 16:05 PDT, Victor Costan
no flags
Victor Costan
Comment 1 2013-04-14 16:05:39 PDT
Victor Costan
Comment 2 2013-04-14 16:10:49 PDT
Sorry, my initial description is incorrect. Only the test cases for the WebKitIDL code generator are checked in, which means only patches that change the generators, like [20141], will get flagged by the style checker. Nevertheless, it would be nice to not have this problem. [20141] https://bugs.webkit.org/show_bug.cgi?id=20141
Brent Fulgham
Comment 3 2013-04-15 12:34:35 PDT
Comment on attachment 198013 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=198013&action=review I like the intent behind this change, but I'm wondering if we might need something more sophisticated. When we have multiple arguments of the same type, it seems like we SHOULD have an argument name to document what the different parameters are meant to do. Although the current labels are not all that helpful, some of them could be changed to be more descriptive. If the IDL does not provide an argument name, will the generator produce the desired output? Maybe fixing/adjusting the IDL would be a good thing to do instead/in addition? > Source/WebCore/bindings/scripts/test/CPP/WebDOMTestSerializedScriptValueInterface.h:-56 > - void multiTransferList(const WebDOMString& first, const WebDOMArray& tx, const WebDOMString& second, const WebDOMArray& txx); Is it really improper to have some context for these arguments? How do we know what the first and second WebDOMStrings are supposed to represent? Maybe it's not always improper to have a label (although these labels are not very helpful!)
Andreas Kling
Comment 4 2014-02-05 11:23:29 PST
The C++ bindings have been removed.
Note You need to log in before you can comment on or make changes to this bug.