IronBefunge Issue Tracker Rss Feed

Closed Feature: Do Work Outside of Ctors

jasonrbock — Tue, 21 Jul 2009 14:41:55 GMT

CodeAnalysis keeps "bugging" me when I do something like "new Interpreter(...)" ... and that's it. IOW I'm creating an object that seems to do nothing. Look at having Interpreter, Executor, Parser have Interpret(), Execute() and Parse(), respectively. If needed, have them use read-only copies of ctor data for multiple calls that yield same results.
Comments:

Fixed in changeset 34571

Created Issue: Resolve Unimplemented Instructions

jasonrbock — Tue, 21 Jul 2009 04:28:26 GMT

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.

Created Feature: Add "Dumper"

jasonrbock — Tue, 21 Jul 2009 04:22:46 GMT

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, etc. Come up with a scheme to yield this kind of "insight".

Created Feature: Do Work Outside of Ctors

jasonrbock — Tue, 21 Jul 2009 04:18:23 GMT

Created Feature: Optimize Move()

jasonrbock — Tue, 21 Jul 2009 04:16:12 GMT

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 with a way to not only find out the next valid cell in the current direction, but also cache those values as cell references to remove the need for more lookups.