4a943d4ed3
I've been saying for a while[1][2][3] that adding extra abstractions makes things harder for newcomers, and adding new notations doubly so. And then I notice this DSL in my own backyard. Makes me feel like a hypocrite. [1] https://news.ycombinator.com/item?id=13565743#13570092 [2] https://lobste.rs/s/to8wpr/configuration_files_are_canary_warning [3] https://lobste.rs/s/mdmcdi/little_languages_by_jon_bentley_1986#c_3miuf2 The implementation of the DSL was also highly hacky: a) It was happening in the tangle/ tool, but was utterly unrelated to tangling layers. b) There were several persnickety constraints on the different kinds of lines and the specific order they were expected in. I kept finding bugs where the translator would silently do the wrong thing. Or the error messages sucked, and readers may be stuck looking at the generated code to figure out what happened. Fixing error messages would require a lot more code, which is one of my arguments against DSLs in the first place: they may be easy to implement, but they're hard to design to go with the grain of the underlying platform. They require lots of iteration. Is that effort worth prioritizing in this project? On the other hand, the DSL did make at least some readers' life easier, the ones who weren't immediately put off by having to learn a strange syntax. There were fewer quotes to parse, fewer backslash escapes. Anyway, since there are also people who dislike having to put up with strange syntaxes, we'll call that consideration a wash and tear this DSL out. --- This commit was sheer drudgery. Hopefully it won't need to be redone with a new DSL because I grow sick of backslashes. |
||
|---|---|---|
| .. | ||
| Readme | ||
| build | ||
| build_and_test_until | ||
| clean | ||
| compiler2 | ||
| compiler3 | ||
| compiler4 | ||
| compiler5 | ||
| compiler6 | ||
| compiler7 | ||
| compiler8 | ||
| compiler9 | ||
| compiler10 | ||
| ex3.k2 | ||
| ex4.k2 | ||
| ex5.k2 | ||
| ex6.k2 | ||
| ex7.k2 | ||
| ex8.k2 | ||
| factorial.k2 | ||
| vimrc.vim | ||
Readme
Abortive series of attempts at building a bootstrappable low-level language. Type-checked, but feasible to implement in some sort of notation for machine code (like SubX). The latest version is in compiler10. But it doesn't account for checking how programs allocate registers.