
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.
43 lines
1.1 KiB
C++
43 lines
1.1 KiB
C++
/*
|
|
* Copyright (c) 2021, Linus Groh <linusg@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <AK/Format.h>
|
|
#include <LibJS/Contrib/Test262/$262Object.h>
|
|
#include <LibJS/Contrib/Test262/AgentObject.h>
|
|
#include <LibJS/Contrib/Test262/GlobalObject.h>
|
|
#include <LibJS/Heap/Cell.h>
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
#include <LibJS/Runtime/VM.h>
|
|
|
|
namespace JS::Test262 {
|
|
|
|
void GlobalObject::initialize_global_object()
|
|
{
|
|
Base::initialize_global_object();
|
|
|
|
auto& realm = *associated_realm();
|
|
m_$262 = vm().heap().allocate<$262Object>(*this, realm);
|
|
|
|
// https://github.com/tc39/test262/blob/master/INTERPRETING.md#host-defined-functions
|
|
u8 attr = Attribute::Writable | Attribute::Configurable;
|
|
define_native_function("print", print, 1, attr);
|
|
define_direct_property("$262", m_$262, attr);
|
|
}
|
|
|
|
void GlobalObject::visit_edges(Cell::Visitor& visitor)
|
|
{
|
|
Base::visit_edges(visitor);
|
|
visitor.visit(m_$262);
|
|
}
|
|
|
|
JS_DEFINE_NATIVE_FUNCTION(GlobalObject::print)
|
|
{
|
|
auto string = TRY(vm.argument(0).to_string(global_object));
|
|
outln("{}", string);
|
|
return js_undefined();
|
|
}
|
|
|
|
}
|