ecd163bdf1
No functional changes - we can still very easily get to the global object via `Realm::global_object()`. This is in preparation of moving the intrinsics to the realm and no longer having to pass a global object when allocating any object. In a few (now, and many more in subsequent commits) places we get a realm using `GlobalObject::associated_realm()`, this is intended to be temporary. For example, create() functions will later receive the same treatment and are passed a realm instead of a global object.
27 lines
551 B
C++
27 lines
551 B
C++
/*
|
|
* Copyright (c) 2021, Linus Groh <linusg@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
#include <LibJS/Runtime/Object.h>
|
|
|
|
namespace JS::Test262 {
|
|
|
|
class AgentObject final : public Object {
|
|
JS_OBJECT(AgentObject, Object);
|
|
|
|
public:
|
|
explicit AgentObject(Realm&);
|
|
virtual void initialize(JS::GlobalObject&) override;
|
|
virtual ~AgentObject() override = default;
|
|
|
|
private:
|
|
JS_DECLARE_NATIVE_FUNCTION(monotonic_now);
|
|
JS_DECLARE_NATIVE_FUNCTION(sleep);
|
|
};
|
|
|
|
}
|