Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 3656 | Kartik K. Agaram | 2016-11-10 | 1 | -1/+1 |
| | | | | | | | | | | | | | | Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student. | ||||
* | 3537 | Kartik K. Agaram | 2016-10-20 | 1 | -0/+19 |
| | |||||
* | 3390 | Kartik K. Agaram | 2016-09-17 | 1 | -1/+1 |
| | |||||
* | 3389 | Kartik K. Agaram | 2016-09-17 | 1 | -4/+4 |
| | |||||
* | 3386 | Kartik K. Agaram | 2016-09-17 | 1 | -7/+7 |
| | |||||
* | 3385 | Kartik K. Agaram | 2016-09-17 | 1 | -11/+11 |
| | |||||
* | 3157 - more testable 'random' interface | Kartik K. Agaram | 2016-07-27 | 1 | -0/+55 |
Shouldn't break any existing programs using 'random'. |