Ignore:
Timestamp:
Aug 30, 2012, 4:36:41 PM (13 years ago)
Author:
[email protected]
Message:

Try to fix the Qt build: Remove the inline keyword at the declaration
site.

The Qt compiler seems to be confused, complaining about these functions
not being defined in a translation unit, even though no generated code
in the unit calls these functions. Maybe removing the keyword at the
declaration site will change its mind.

This shouldn't change the inlining decision at all: the definition is
still inline.

  • interpreter/CallFrame.h:

(ExecState):

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/interpreter/CallFrame.h

    r127202 r127211  
    5454        // Global object in which the currently executing code was defined.
    5555        // Differs from dynamicGlobalObject() during function calls across web browser frames.
    56         inline JSGlobalObject* lexicalGlobalObject() const;
     56        JSGlobalObject* lexicalGlobalObject() const;
    5757
    5858        // Differs from lexicalGlobalObject because this will have DOM window shell rather than
    5959        // the actual DOM window, which can't be "this" for security reasons.
    60         inline JSObject* globalThisValue() const;
    61 
    62         inline JSGlobalData& globalData() const;
     60        JSObject* globalThisValue() const;
     61
     62        JSGlobalData& globalData() const;
    6363
    6464        // Convenience functions for access to global data.
     
    184184
    185185        // Read a register from the codeframe (or constant from the CodeBlock).
    186         inline Register& r(int);
     186        Register& r(int);
    187187        // Read a register for a non-constant
    188         inline Register& uncheckedR(int);
     188        Register& uncheckedR(int);
    189189
    190190        // Access to arguments.
Note: See TracChangeset for help on using the changeset viewer.