| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2778 - fix all layers | Kartik K. Agaram | 2016-03-14 | 1 | -62/+0 |
| | | |||||
| * | 2735 - define recipes using 'def' | Kartik K. Agaram | 2016-03-08 | 1 | -1/+1 |
| | | | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu. | ||||
| * | 2712 | Kartik K. Agaram | 2016-02-26 | 1 | -2/+2 |
| | | |||||
| * | 2685 | Kartik K. Agaram | 2016-02-19 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | Stack of plans for cleaning up replace_type_ingredients() and a couple of other things, from main problem to subproblems: include type names in the type_tree rather than in the separate properties vector make type_tree and string_tree real cons cells, with separate leaf nodes redo the vocabulary for dumping various objects: do we really need to_string and debug_string? can we have a version with *all* information? can we have to_string not call debug_string? This commit nibbles at the edges of the final task, switching from member method syntax to global function like almost everything else. I'm mostly using methods just for STL in this project. | ||||
| * | 2430 - make room for more transforms | Kartik K. Agaram | 2015-11-13 | 1 | -0/+62 |