[Webkit-unassigned] [Bug 16029] New: JavaScriptCore API is not portable

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Nov 17 12:09:00 PST 2007


           Summary: JavaScriptCore API is not portable
           Product: WebKit
           Version: 525+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: alp at atoker.com
                CC: darin at apple.com

r21342 introduced JSStringRefCF.h to JavaScriptCore.h:


This breaks sources that include JavaScriptCore.h on platforms without CF.

<rdar://problem/4885130> mentions that the plan was to have applications
include JSStringRefCF.h as needed, which sounds like the right thing to do, but
r21342 goes against that.

I'm investigating switching a couple of bindings from the C++ API to the new C
API. This is the only issue that's come up so far.

It seems the most elegant solution would actually be to create a new top-level
header, JavaScriptCoreCF.h, which includes CF-specific headers in addition to
the portable JavaScriptCore.h. This does not represent an ABI break so I
suspect it can be implemented right now with minimal disruption.

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list