Resolve Unimplemented Instructions

The Befunge-98 spec says that if an instruction is hit that is "not understood", it should act like "r" (Reverse) (and also report this as a warning in the "dumper"). Implement this.

Id #8064 | Release: None | Updated: Feb 1, 2013 at 11:40 PM by jasonrbock | Created: Jul 21, 2009 at 5:28 AM by jasonrbock

Add "Dumper"

It would be nice to have some insight into the execution of a Befunge program - i.e. a list of all the instructions run, the state of the stack at those times, if an "unimplemented" was encountered...

Id #8063 | Release: None | Updated: Feb 1, 2013 at 11:40 PM by jasonrbock | Created: Jul 21, 2009 at 5:22 AM by jasonrbock

Optimize Move()

Right now the Move() method in ExecutionContext is horrible. It goes through the FungeSpace one cell at a time, so if the next instruction is 1000 points away ... well, that sucks. Need to come up ...

Id #8061 | Release: None | Updated: Feb 1, 2013 at 11:40 PM by jasonrbock | Created: Jul 21, 2009 at 5:16 AM by jasonrbock

  • 1-3 of 3 Work Items
    • Previous
    • 1
    • Next
    • Showing
    • All
    • Work Items