Suggested enhancements
- Dominant language
- Scala
- Stars
- 279
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I'm liking what I'm learning of Millfork so far, but there are a couple things that I've wished it had.
- It would be very nice to be able to define a struct that contained an array.
- I'd love to have a predefined constant for every variable such that "foo.$bank" or some such would resolve to the value of the bank attribute of the segment in which "foo" is defined.
- Computed variables; basically functions that set or get a value, but expressed syntactically as functions.
- A per-bank output mode to go with the one-file and per-segment output modes, where I could define a bank size, and Millfork would just stick all the segments with that bank id into that bank's file.
- Given that the 6502 supports BCD natively, the ability to tag an integer variable as being in BCD would be great.
- It honestly bugs me that segment.NAME.start gives the address of the first used byte in the segment and not the value I defined in segment_NAME_start in the .ini file.
Contributor guide
Assessment
This issue has not been assessed yet.