Ignore:
Timestamp:
May 9, 2007, 3:16:41 PM (18 years ago)
Author:
ggaren
Message:

Reviewed by Darin Adler.


Fixed #includes of JSStringRefCF.h and use of CF datatypes. I think I
misunderstood this issue before.

  • API/JavaScriptCore.h: #include JSStringRefCF.h. Platforms that don't want this behavior can just #include individual headers, instead of the umbrella framework header. But we definitely want Mac OS X clients to get the #include of JSStringRefCF.h "for free."
  • API/minidom.c: Don't #include JSStringRefCF.h. (Don't need to #include JavaScriptCore.h, either.)
  • API/testapi.c: Don't #include JSStringRefCF.h. Do use CF datatypes regardless of whether APPLE is defined. Platforms that don't support CF just shouldn't compile this file. (main):
File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/JavaScriptCore/API/JavaScriptCore.h

    r15400 r21342  
    3131#include <JavaScriptCore/JSContextRef.h>
    3232#include <JavaScriptCore/JSStringRef.h>
     33#include <JavaScriptCore/JSStringRefCF.h>
    3334#include <JavaScriptCore/JSObjectRef.h>
    3435#include <JavaScriptCore/JSValueRef.h>
Note: See TracChangeset for help on using the changeset viewer.