about summary refs log tree commit diff stats
path: root/tangle
Commit message (Collapse)AuthorAgeFilesLines
* 5801 - move `tangle` to `tools/` dirKartik Agaram2019-12-078-1192/+0
|
* 5001 - drop the :(scenario) DSLKartik Agaram2019-03-124-583/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 4980Kartik Agaram2019-02-181-8/+8
|
* 4979Kartik Agaram2019-02-182-1/+112
|
* 4406Kartik Agaram2018-07-252-2/+29
| | | | Fix CI.
* 4405Kartik Agaram2018-07-252-25/+69
|
* 4404 - clean up generated code for scenariosKartik Agaram2018-07-252-23/+65
| | | | Thanks Max Bernstein for the feedback.
* 4403Kartik Agaram2018-07-252-1/+7
| | | | | | Couple of improvements for the tangle/ directory: a) Start running tangle unit tests at build time again. b) Option to print out test names as they run, just like in top-level.
* 4402Kartik Agaram2018-07-251-19/+99
|
* 4401 - make unit tests for tangle a little more readableKartik Agaram2018-07-251-41/+200
| | | | Thanks Max Bernstein for surfacing this idea to my memory.
* 4000Kartik K. Agaram2017-09-151-0/+1
|
* 3839Kartik K. Agaram2017-04-202-3/+20
| | | | | | Fix CI. In the process I also fixed a bug in the tangle/ utility.
* 3726Kartik K. Agaram2016-12-301-0/+1
|
* 3711Kartik K. Agaram2016-12-265-13/+3
| | | | | Delete '^L' characters now that I'm trying to switch from Vim to Kakoune. Pages aren't text objects in Kakoune.
* 3550Kartik K. Agaram2016-10-222-2/+2
|
* 3450Kartik K. Agaram2016-10-061-25/+0
| | | | Purge remaining `makefile`s, without breaking CI.
* 3448Kartik K. Agaram2016-10-061-5/+5
| | | | Drop perl dependency everywhere.
* 3363 - bugfix in tangleKartik K. Agaram2016-09-152-1/+12
|
* 3361Kartik K. Agaram2016-09-151-7/+7
|
* 3278Kartik K. Agaram2016-08-291-5/+2
|
* 3218Kartik K. Agaram2016-08-172-0/+14
| | | | | | Fix CI. Scenario size_of_shape_shifting_exclusive_container was triggering undefined behavior in tangle/ and causing things to break in some compilers but not others.
* 3217Kartik K. Agaram2016-08-171-2/+2
| | | | Fix a new warning from Perl.
* 3101 - purge .traces/ dir from repo historyKartik K. Agaram2016-07-052-13/+0
| | | | | | | | | | | | | | | | | | | | | I'd been toying with this idea for some time now given how large the repo had been growing. The final straw was noticing that people cloning the repo were having to wait *5 minutes*! That's not good, particularly for a project with 'tiny' in its description. After purging .traces/ clone time drops to 7 seconds in my tests. Major issue: some commits refer to .traces/ but don't really change anything there. That could get confusing :/ Minor issues: a) I've linked inside commits on GitHub like a half-dozen times online or over email. Those links are now liable to eventually break. (I seem to recall GitHub keeps them around as long as they get used at least once every 60 days, or something like that.) b) Numbering of commits is messed up because some commits only had changes to the .traces/ sub-directory.
* 3063Kartik K. Agaram2016-06-193-6/+5
|
* 2768 - get working in Linux againKartik K. Agaram2016-03-131-0/+2
| | | | Need to start testing every commit on Linux in addition to Mac.
* 2760Kartik K. Agaram2016-03-112-0/+0
|
* 2759Kartik K. Agaram2016-03-105-316/+19
| | | | Clean up tangle/ helper.
* 2575 - better messages on trace count failuresKartik K. Agaram2016-01-192-3/+3
|
* 1746 - load file and run a single testKartik K. Agaram2015-07-101-1/+1
| | | | $ ./mu test run-instruction-and-print-warnings
* 1676Kartik K. Agaram2015-06-281-1/+1
|
* 1501Kartik K. Agaram2015-05-282-14/+28
|
* 1500Kartik K. Agaram2015-05-281-0/+5
|
* 1483 - *really* check color screens in scenariosKartik K. Agaram2015-05-272-17/+12
| | | | | | | | | | | | | | | | | Required fixing two levels of bugs: a) The hack in tangle to drop initial comments a '%' directive.. b) ..was masking a bug where run_mu_scenario wasn't robust to initial comments. Mildly concerned that neither of the sub-issues have their own tests, but I'm just removing hacks, and writing tests for that throwaway function like run_mu_scenario seems pointless. Instead I've solved the problem by disallowing comments before '%' directives. I've also taken this opportunity to at least try to document the 'scenarios' and '%' directives at the first layer where they appear.
* 1439 - support clang in addition to gccKartik K. Agaram2015-05-231-1/+1
|
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-058-0/+1488
I've tried to update the Readme, but there are at least a couple of issues.