WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
163179
Attribute getter binding generated code should use more references
https://bugs.webkit.org/show_bug.cgi?id=163179
Summary
Attribute getter binding generated code should use more references
youenn fablet
Reported
2016-10-09 04:37:07 PDT
We can use references for ExecState and thisObject.
Attachments
Patch
(191.50 KB, patch)
2016-10-09 04:42 PDT
,
youenn fablet
no flags
Details
Formatted Diff
Diff
Patch for landing
(189.49 KB, patch)
2016-10-10 01:28 PDT
,
youenn fablet
no flags
Details
Formatted Diff
Diff
Patch for landing
(189.61 KB, patch)
2016-10-10 01:30 PDT
,
youenn fablet
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
youenn fablet
Comment 1
2016-10-09 04:42:52 PDT
Created
attachment 291042
[details]
Patch
Darin Adler
Comment 2
2016-10-09 15:25:17 PDT
Comment on
attachment 291042
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=291042&action=review
Seems OK for now; makes things better in some ways, but worse in others with those extra conditions and variables.
> Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:3903 > + my $useReferences = shift;
This boolean is really ugly, all the mysterious "1", all the extra variables and cases. Is there some way to avoid this?
> Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:4938 > + my ($signature, $inFunctionCall, $interface, $value, $thisValue, $useReferences) = @_;
This boolean is really ugly, all the mysterious "1", all the extra variables and cases. Is there some way to avoid this?
> Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:4945 > + # FIXNE: We should move to using references only
FIXME misspelled here
youenn fablet
Comment 3
2016-10-10 00:38:19 PDT
Thanks for the review.
> > Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:3903 > > + my $useReferences = shift; > > This boolean is really ugly, all the mysterious "1", all the extra variables > and cases. Is there some way to avoid this?
This is temporary, since it should use references once attribute setters and methods are also moved to using references. That said, in the meantime, it might be best to introduce a NativeToJSValueWithReferences and NativeToJSValueWithPointers, that would call a sub NativeToJSValue routine.
> > Source/WebCore/bindings/scripts/CodeGeneratorJS.pm:4945 > > + # FIXNE: We should move to using references only > > FIXME misspelled here
OK
youenn fablet
Comment 4
2016-10-10 01:28:26 PDT
Created
attachment 291077
[details]
Patch for landing
youenn fablet
Comment 5
2016-10-10 01:30:37 PDT
Created
attachment 291078
[details]
Patch for landing
WebKit Commit Bot
Comment 6
2016-10-10 02:05:44 PDT
Comment on
attachment 291078
[details]
Patch for landing Clearing flags on attachment: 291078 Committed
r206992
: <
http://trac.webkit.org/changeset/206992
>
WebKit Commit Bot
Comment 7
2016-10-10 02:05:48 PDT
All reviewed patches have been landed. Closing bug.
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