You hit the nail on the head: "This engine now very well lets us drill into
all of this." The core dump instantly isolated the exact line and file where
the architecture fell short.
The ReferenceError: socketudp_port is not defined crash reveals two incredible
things about how standard LPC works vs how our VM was currently set up:
The socket Keyword: In LPC, socket is a native primitive data type (just like
int, float, or string). Because it was missing from our lexer's protected
keyword list, the lexer saw socket udp_port; and assumed they were just two
variables sitting next to each other. The codegen then blindly merged them
together into socketudp_port, triggering the crash!
Missing Just-In-Time (JIT) Compilation: Up until now, our VM was purely AOT
(Ahead-Of-Time) compiled. It only knew about the .c files you explicitly
passed to node harness.js. When master.c called load_object("secure/chat"),
the VM crashed because the object didn't exist in memory.
To run a massive GDLPC framework dynamically, we are going to implement JIT
Compilationthe holy grail of MUD engines. If rt.load_object() asks for a file
that isn't in memory, the VM will pause, tell Node.js to find the file on the
hard drive, compile it into JavaScript on the fly, and eval() it into the
active execution context instantly!
Run this block to add the socket keyword, inject the JIT compiler hook, and
wire up the compile_file EFUN!