LibJS: Remove {Bytecode::,}Interpreter::global_object()

The basic idea is that a global object cannot just come out of nowhere,
it must be associated to a realm - so get it from there, if needed.

This is to enforce the changes from all the previous commits by not
handing out global objects unless you actually have an initialized
realm (either stored somewhere, or the VM's current realm).

1 files changed, 1 insertions, 1 deletions

diff --git a/Userland/Applications/Spreadsheet/Spreadsheet.cpp b/Userland/Applications/Spreadsheet/Spreadsheet.cpp
index e5da87ac9b..c8e3c4ab4a 100644
--- a/Userland/Applications/Spreadsheet/Spreadsheet.cpp
+++ b/Userland/Applications/Spreadsheet/Spreadsheet.cpp
@@ -43,7 +43,7 @@ Sheet::Sheet(Workbook& workbook)
     , m_interpreter(JS::Interpreter::create<SheetGlobalObject>(m_workbook.vm(), *this))
 {
     JS::DeferGC defer_gc(m_workbook.vm().heap());
-    m_global_object = static_cast<SheetGlobalObject*>(&m_interpreter->global_object());
+    m_global_object = static_cast<SheetGlobalObject*>(&m_interpreter->realm().global_object());
     global_object().define_direct_property("workbook", m_workbook.workbook_object(), JS::default_attributes);
     global_object().define_direct_property("thisSheet", &global_object(), JS::default_attributes); // Self-reference is unfortunate, but required.