ladybird/Userland/Libraries/LibJS/Runtime/BooleanObject.cpp

/*
 * Copyright (c) 2020, Jack Karamanian <karamanian.jack@gmail.com>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibJS/Runtime/BooleanObject.h>
#include <LibJS/Runtime/GlobalObject.h>

namespace JS {

BooleanObject* BooleanObject::create(Realm& realm, bool value)
{
    return realm.heap().allocate<BooleanObject>(realm, value, *realm.intrinsics().boolean_prototype());
}

BooleanObject::BooleanObject(bool value, Object& prototype)
    : Object(prototype)
    , m_value(value)
{
}

}
LibJS: Add Boolean constructor object 2020-04-06 22:51:16 -05:00			`/*`
			`* Copyright (c) 2020, Jack Karamanian <karamanian.jack@gmail.com>`
			`*`
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt * 2021-04-22 01:24:48 -07:00			`* SPDX-License-Identifier: BSD-2-Clause`
LibJS: Add Boolean constructor object 2020-04-06 22:51:16 -05:00			`*/`

			`#include <LibJS/Runtime/BooleanObject.h>`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 19:03:52 +02:00			`#include <LibJS/Runtime/GlobalObject.h>`
LibJS: Add Boolean constructor object 2020-04-06 22:51:16 -05:00
			`namespace JS {`
LibJS: Boolean, Number and String prototypes should have values too It appears that calling .valueOf() on an objectified primitive's prototype should return a value after all. This matches what other engines are doing. 2020-04-10 13:04:12 +02:00
LibJS+LibWeb: Replace GlobalObject with Realm in create() functions This is a continuation of the previous two commits. As allocating a JS cell already primarily involves a realm instead of a global object, and we'll need to pass one to the allocate() function itself eventually (it's bridged via the global object right now), the create() functions need to receive a realm as well. The plan is for this to be the highest-level function that actually receives a realm and passes it around, AOs on an even higher level will use the "current realm" concept via VM::current_realm() as that's what the spec assumes; passing around realms (or global objects, for that matter) on higher AO levels is pointless and unlike for allocating individual objects, which may happen outside of regular JS execution, we don't need control over the specific realm that is being used there. 2022-08-16 00:20:49 +01:00			`BooleanObject* BooleanObject::create(Realm& realm, bool value)`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 19:03:52 +02:00			`{`
LibJS: Move intrinsics to the realm Intrinsics, i.e. mostly constructor and prototype objects, but also things like empty and new object shape now live on a new heap-allocated JS::Intrinsics object, thus completing the long journey of taking all the magic away from the global object. This represents the Realm's [[Intrinsics]] slot in the spec and matches its existing [[GlobalObject]] / [[GlobalEnv]] slots in terms of architecture. In the majority of cases it should now be possibly to fully allocate a regular object without the global object existing, and in fact that's what we do now - the realm is allocated before the global object, and the intrinsics between both :^) 2022-08-27 00:54:55 +01:00			`return realm.heap().allocate<BooleanObject>(realm, value, *realm.intrinsics().boolean_prototype());`
LibJS: Pass prototype to BooleanObject constructor 2020-04-17 19:03:52 +02:00			`}`

			`BooleanObject::BooleanObject(bool value, Object& prototype)`
LibJS: Clarify Object (base class) construction somewhat Divide the Object constructor into three variants: - The regular one (takes an Object& prototype) - One for use by GlobalObject - One for use by objects without a prototype (e.g ObjectPrototype) 2020-06-23 17:21:53 +02:00			`: Object(prototype)`
LibJS+LibWeb: Pass prototype to Object constructor Everyone who constructs an Object must now pass a prototype object when applicable. There's still a fair amount of code that passes something fetched from the Interpreter, but this brings us closer to being able to detach prototypes from Interpreter eventually. 2020-04-18 10:27:57 +02:00			`, m_value(value)`
LibJS: Add Boolean constructor object 2020-04-06 22:51:16 -05:00			`{`
			`}`
LibJS: Add missing whitespace around namespace curly braces 2022-04-17 22:59:52 +02:00
LibJS: Add Boolean constructor object 2020-04-06 22:51:16 -05:00			`}`