Summary: | Assertion failure under -[JSObjCClassInfo allocateConstructorAndPrototypeWithSuperClassInfo:] if no classes conform to JSExport | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | mitz | ||||
Component: | JavaScriptCore | Assignee: | mitz | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, darin, mhahnenberg | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
mitz
2013-09-30 14:34:53 PDT
Created attachment 213038 [details]
Define a class that conforms to the JSExport protocol in JavaScriptCore.
Is there a similar problem with the NSBlock class? If not, why not? (In reply to comment #2) > Is there a similar problem with the NSBlock class? If not, why not? No. the NSBlock class is defined in Core Foundation, which JavaScriptCore links against. The only reason getNSBlockClass() doesn’t use [NSBlock self] is that the class is not declared in a public header. Comment on attachment 213038 [details] Define a class that conforms to the JSExport protocol in JavaScriptCore. Clearing flags on attachment: 213038 Committed r156684: <http://trac.webkit.org/changeset/156684> All reviewed patches have been landed. Closing bug. |