b99cc7d050
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.
36 lines
955 B
C++
36 lines
955 B
C++
/*
|
|
* Copyright (c) 2021, Idan Horowitz <idan.horowitz@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Runtime/ArrayBuffer.h>
|
|
#include <LibJS/Runtime/GlobalObject.h>
|
|
#include <LibJS/Runtime/Object.h>
|
|
|
|
namespace JS {
|
|
|
|
class DataView : public Object {
|
|
JS_OBJECT(DataView, Object);
|
|
|
|
public:
|
|
static DataView* create(Realm&, ArrayBuffer*, size_t byte_length, size_t byte_offset);
|
|
|
|
explicit DataView(ArrayBuffer*, size_t byte_length, size_t byte_offset, Object& prototype);
|
|
virtual ~DataView() override = default;
|
|
|
|
ArrayBuffer* viewed_array_buffer() const { return m_viewed_array_buffer; }
|
|
size_t byte_length() const { return m_byte_length; }
|
|
size_t byte_offset() const { return m_byte_offset; }
|
|
|
|
private:
|
|
virtual void visit_edges(Visitor& visitor) override;
|
|
|
|
ArrayBuffer* m_viewed_array_buffer { nullptr };
|
|
size_t m_byte_length { 0 };
|
|
size_t m_byte_offset { 0 };
|
|
};
|
|
|
|
}
|