WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
149759
JSBuiltinConstructor must always add builtin header
https://bugs.webkit.org/show_bug.cgi?id=149759
Summary
JSBuiltinConstructor must always add builtin header
Xabier Rodríguez Calvar
Reported
2015-10-02 12:30:43 PDT
JSBuiltinConstructor must always add builtin header
Attachments
Patch
(2.23 KB, patch)
2015-10-02 12:32 PDT
,
Xabier Rodríguez Calvar
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Xabier Rodríguez Calvar
Comment 1
2015-10-02 12:32:53 PDT
Created
attachment 262345
[details]
Patch If you compile the previously generated file with the initialization function ready in the .js file, compilation was failing because the header file couldn't be found. It is actually needed because the builtins include already the initialization function.
youenn fablet
Comment 2
2015-10-04 23:40:07 PDT
LGTM
youenn fablet
Comment 3
2015-10-05 01:02:27 PDT
Comment on
attachment 262345
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=262345&action=review
> Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:5120 > + return 1;
Just for style, returning 1 is not needed anymore. It might be better to refactor the whole routine accordingly.
Xabier Rodríguez Calvar
Comment 4
2015-10-05 01:24:36 PDT
(In reply to
comment #3
)
> Comment on
attachment 262345
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=262345&action=review
> > > Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:5120 > > + return 1; > > Just for style, returning 1 is not needed anymore. > It might be better to refactor the whole routine accordingly.
I could rewrite to have a if-then and avoid that. I did it like this to pullute the patch less though it is not big deal, of course. What I can't avoid is the return inside the loop because it is supposed to bail out the first time it adds the header.
Xabier Rodríguez Calvar
Comment 5
2015-10-05 10:19:44 PDT
(In reply to
comment #4
)
> > > Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:5120 > > > + return 1; > > > > Just for style, returning 1 is not needed anymore. > > It might be better to refactor the whole routine accordingly. > > I could rewrite to have a if-then and avoid that. I did it like this to > pollute the patch less though it is not big deal, of course. What I can't > avoid is the return inside the loop because it is supposed to bail out the > first time it adds the header.
Darin, wdyt about this? Should I change this when landing or do you like it as it is now?
youenn fablet
Comment 6
2015-10-05 14:24:46 PDT
One possibility for the refactoring would be to transform AddIncludesForJSBuiltinMethods into something like NeedsJSBuiltinsInclude. If you prefer to land this one directly, I can handle it in a follow-up patch.
Xabier Rodríguez Calvar
Comment 7
2015-10-06 00:16:27 PDT
Comment on
attachment 262345
[details]
Patch (In reply to
comment #6
)
> One possibility for the refactoring would be to transform > AddIncludesForJSBuiltinMethods into something like NeedsJSBuiltinsInclude. > > If you prefer to land this one directly, I can handle it in a follow-up > patch.
I can't do anything else than landing this since I'd need Darin's blessing for any other thing.
WebKit Commit Bot
Comment 8
2015-10-06 01:02:31 PDT
Comment on
attachment 262345
[details]
Patch Clearing flags on attachment: 262345 Committed
r190610
: <
http://trac.webkit.org/changeset/190610
>
WebKit Commit Bot
Comment 9
2015-10-06 01:02:38 PDT
All reviewed patches have been landed. Closing bug.
youenn fablet
Comment 10
2015-10-06 03:17:20 PDT
Filed
https://bugs.webkit.org/show_bug.cgi?id=149837
as a follow-up
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug