Following on https://bugs.webkit.org/show_bug.cgi?id=149759, we should further refactor AddIncludesForJSBuiltinMethods, since returning 1 is no longer needed. We should also handle JSBuiltin attributes similarly to JSBuiltin functions.
(In reply to comment #0) > Following on https://bugs.webkit.org/show_bug.cgi?id=149759, we should > further refactor AddIncludesForJSBuiltinMethods, since returning 1 is no > longer needed. > We should also handle JSBuiltin attributes similarly to JSBuiltin functions. Returning 1 is needed to break the loop.
Created attachment 262509 [details] Patch
(In reply to comment #1) > (In reply to comment #0) > > Following on https://bugs.webkit.org/show_bug.cgi?id=149759, we should > > further refactor AddIncludesForJSBuiltinMethods, since returning 1 is no > > longer needed. > > We should also handle JSBuiltin attributes similarly to JSBuiltin functions. > > Returning 1 is needed to break the loop. Not breaking the loop has the slight benefit of being able to handle different Conditionals. I updated TestObj.idl to show this in the binding tests.
(In reply to comment #3) > (In reply to comment #1) > > (In reply to comment #0) > > > Following on https://bugs.webkit.org/show_bug.cgi?id=149759, we should > > > further refactor AddIncludesForJSBuiltinMethods, since returning 1 is no > > > longer needed. > > > We should also handle JSBuiltin attributes similarly to JSBuiltin functions. > > > > Returning 1 is needed to break the loop. > > Not breaking the loop has the slight benefit of being able to handle > different Conditionals. > I updated TestObj.idl to show this in the binding tests. Understood.
Comment on attachment 262509 [details] Patch Clearing flags on attachment: 262509 Committed r190620: <http://trac.webkit.org/changeset/190620>
All reviewed patches have been landed. Closing bug.