Improve Structure of Interpreter

Registered by Eike on 2009-12-10

The interpreter is currently scattered over various classes, and therefore hard to fully understand. Furthermore it is quite a lot of code (2000 lines) for few functionality.

Therefore the code's distribution into functions, and the calling mechanism should be reworked.

Blueprint information

Status:
Started
Approver:
Eike
Priority:
Medium
Drafter:
Eike
Direction:
Approved
Assignee:
Eike
Definition:
Drafting
Series goal:
Accepted for trunk
Implementation:
Started
Milestone target:
None
Started by
Eike on 2010-05-22

Related branches

Sprints

Whiteboard

Read some literature on the subject!

The interpreter now resides in one giant object.

The code became no shorter though.

Actions for Interpreter class:
- Split off code collection into own object
- Split off compile statement into own object
- split off built in library into own module.

Actions for interpreter module:
- Split into built in library and interpreter module.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.