Decide on label/section/data formats #2

Open
opened 2025-04-25 18:10:19 -04:00 by lambdabeta · 0 comments
Owner

Current naive implementation allows labels to mark data or code in different sections. Allows almost 100 sections. Alternatively could have no sections, but have modes, all data would be pushed onto the stack (as pointers to memory likely) and labels would only mark code.

Current thought is that the naive implementation is probably fine. Plus it leaves more options for future expansion. It does mean keeping track of label types though.

Current naive implementation allows labels to mark data or code in different sections. Allows almost 100 sections. Alternatively could have no sections, but have modes, all data would be pushed onto the stack (as pointers to memory likely) and labels would only mark code. Current thought is that the naive implementation is probably fine. Plus it leaves more options for future expansion. It does mean keeping track of label types though.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ARCTIC/arctic#2
No description provided.