oraqlle / crank

An Infinite State Machine

oraqlle

Just a dude who loves writing (and talking about) software.

Info

• CEO of Monash DeepNeuron for 2023/2024
• Third year student at Monash University
• Interested in language design, compilers/interpreters and game dev.
• Current work:
  • clox: Bytecode Interpreter for Lox written in C
• Noteworthy work:
  • Base64 Decoder in Zig
  • Sorting Algorithm Visualizer
  • Terminal based 2048 (in a few languages)
  • Co-author of MDN's HPC Training Book
  • C++ Standard Container Benchmarker
  • jlox: Tree-Walking Interpreter for Lox Written in Java

crank's Issues

State object used after the end of their lifetime

Details

The current implementation of Crank generates a new state object when a new state is pushed to the state-stack of the engine. This state object is owned by the stack an as such if the state is popped from the stack the object is cleaned up however, if the state itself requested for itself to be popped off the state-stack the subsequent return to the method of the state that called for its own 'popping' will create a segmentation fault as the object now longer exist.

Potential Fixes

• Reuse static object 'instances' and remove factories
• use std::shared_ptr of states that are owned by main and the state-stack.