2e3a85d94b
Still lots to do, but the eventual hope is that this will make this project's code easier to reuse from other LÖVE projects. One gotcha: even as we start putting code more aggressively into nested tables, tests must remain at the top-level. Otherwise they won't run.
1.5 KiB
I care a lot about being able to automatically check any property about my program before it ever runs. However, some things don't have tests yet, either because I don't know how to test them or because I've been lazy. I'll at least record those here.
Compromises
Lua is dynamically typed. Tests can't patch over lack of type-checking.
-
All strings are UTF-8. Bytes within them are not characters. I try to label byte offsets with the suffix
_offset, and character positions as_pos. For example,string.subshould never use a_posto substring, only an_offset. -
Some ADT/interface support would be helpful in keeping per-line state in sync. Any change to line data should clear line
fragmentsandscreen_line_starting_pos. -
Some inputs get processed in love.textinput and some in love.keypressed. Several bugs have arisen due to destructive interference between the two for some key chord. I wish I could guarantee that the two sets are disjoint. But perhaps I'm not thinking about this right.
-
Like any high-level language, it's easy to accidentally alias two non-scalar variables. I wish there was a way to require copy when assigning.
-
My test harness automatically runs
test_*methods -- but only at the top-level. I wish there was a way to raise warnings if someone defines such a function inside a dict somewhere.
Todo list
- Initializing settings:
- from previous session
- Filename as absolute path
- Filename as relative path
- from defaults
- from previous session