added run method and 2 constants for FINAL_FP and FINAL_PC

[KeneePatel]

Run implementation

Time spent on this PR: 0.2 days

Pull request type

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Does not have a run method. Relies on runUntilPc for running program.

Resolves #5

What is the new behavior?

Have implemented a run method which executes steps until current PC becomes FINAL_PC i.e. when pc == FINAL_PC

Good things:

• It works

Bad things:

• Very basic
• hard coded starting pc value, and does not take into consideration the number of args. Works for functions with exactly one argument
• would need refactoring or change soon when extending other behaviour or features.

[KeneePatel]

Oh forgot to mention that the stop condition for run is both when pc == FINAL_PC or when pc == FINAL_FP because I noticed the last execution step makes pc <FINAL_FP> due to current implementation of step().

[ClementWalter]

check the Step function in the ui to start run from the current step plz