Code Collection Improvements
The code collection process is currently very simplistic, ideas for improvements should be put here.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Compile time exceptions
- Already emitted code has to be removed. When a function raises a compile time exception
the code it has emitted becomes invalid.
- Idea: each function has it own list of statements on the code stack.
- When the function returns successfully this list is appended to the list of the currently executing function.
- When a compile time exception is caught, potentially multiple levels of the code stack have to be popped.
- Consider emitted code to be part of the function's return value.
- But how are "if" statements handled then? (Currently the code statck exists only for the "if" statements.)
