WebCore/bridge/jni/v8 does not compile

• Component: WebCore JavaScript
• Status: RESOLVED FIXED

[Iain Merrick]

Some API changes were made to JavaScriptCore/runtime/UString.h in http://trac.webkit.org/changeset/65305. The JSC string implementation (in WebCore/bridge/jni/jsc) was updated, but the v8 string implementation was not updated and no longer compiles.

The UTF8String() method needs to be renamed to utf8().

[Iain Merrick]

Created attachment 65111 [details]
Patch to make V8 strings compile

[Steve Block]

Comment on attachment 65111 [details]
Patch to make V8 strings compile

If you'd like the patch to be reviewed, you should set the r? flag. This will make the patch show up in the review queue and trigger the EWS bots.

As a non-committer, you probably want to set cq? too, to request the reviewer to add the patch to the commit-queue once reviewed.

[Steve Block]

Comment on attachment 65111 [details]
Patch to make V8 strings compile

WebCore/ChangeLog:5
 +          Make V8 string wrappers compatible with JavaScriptCore/runtime/UString.h
I think this title is a little confusing. We're fixing the JNI bridge for V8. The problem is that the declaration of JavaString has been changed but the V8 implementation was not updated. Maybe 'Update JNI bridge for V8 after renaming of JavaString::utf8()'

[Iain Merrick]

Created attachment 65118 [details]
Patch to make V8 strings compile

Modified ChangeLog per steveblock's comment

[Steve Block]

Comment on attachment 65118 [details]
Patch to make V8 strings compile

r=me

[WebKit Commit Bot]

Comment on attachment 65118 [details]
Patch to make V8 strings compile

Clearing flags on attachment: 65118

Committed r65833: <http://trac.webkit.org/changeset/65833>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.