about summary refs log tree commit diff stats
path: root/038new_text.cc
Commit message (Collapse)AuthorAgeFilesLines
* 3799Kartik K. Agaram2017-03-181-1/+1
|
* 3694Kartik K. Agaram2016-11-261-1/+44
| | | | Fix CI, broken by commit 3691.
* 3678 - complain about string labelsKartik K. Agaram2016-11-151-0/+9
| | | | Thanks Jack Couch for running into this.
* 3671 - support text in '$print'Kartik K. Agaram2016-11-121-0/+5
|
* 3669Kartik K. Agaram2016-11-111-1/+1
|
* 3668 - $read a word, stopping at whitespaceKartik K. Agaram2016-11-111-0/+30
| | | | | | | | | | | | Useful for programming contests like https://halite.io Doesn't suffer from C++'s usual buffered gotchas: it'll skip leading whitespace. Slow, though. Can be speeded up, though. - 20 minutes later But what's the point? Typewriter mode is actually harder to test than 'raw' console mode. Writing Mu programs in typewriter mode is just going to encourage us all to slack off on writing tests.
* 3561Kartik K. Agaram2016-10-221-1/+1
|
* 3522Kartik K. Agaram2016-10-191-2/+2
|
* 3393Kartik K. Agaram2016-09-171-1/+1
|
* 3380Kartik K. Agaram2016-09-171-2/+2
| | | | | One more place we were missing expanding type abbreviations: inside container definitions.
* 3379Kartik K. Agaram2016-09-171-3/+3
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3376 - start maximally using all type abbreviationsKartik K. Agaram2016-09-171-14/+14
| | | | | | It might be too much, particularly if students start peeking inside .mu files early. But worth a shot for not just to iron out the kinks in the abbreviation system.
* 3375Kartik K. Agaram2016-09-171-1/+5
|
* 3374Kartik K. Agaram2016-09-161-9/+9
|
* 3260Kartik K. Agaram2016-08-261-2/+2
| | | | | array length = number of elements array size = in locations
* 3259Kartik K. Agaram2016-08-261-2/+2
| | | | | | | | | | | Prefer preincrement operators wherever possible. Old versions of compilers used to be better at optimizing them. Even if we don't care about performance it's useful to make unary operators look like unary operators wherever possible, and to distinguish the 'statement form' which doesn't care about the value of the expression from the postincrement which usually increments as a side-effect in some larger computation (and so is worth avoiding except for some common idioms, or perhaps even there).
* 3257Kartik K. Agaram2016-08-261-16/+14
|
* 3256Kartik K. Agaram2016-08-261-0/+3
| | | | | Bugfix in filesystem creation. I'm sure there are other fake-filesystem bugs.
* 3079Kartik K. Agaram2016-06-291-1/+1
|
* 3074Kartik K. Agaram2016-06-291-0/+11
| | | | Thanks Ella Couch for finding this bug.
* 2998Kartik K. Agaram2016-05-241-1/+1
|
* 2932Kartik K. Agaram2016-05-061-1/+1
| | | | | | | More consistent labeling of waypoints. Use types only when you need to distinguish between function overloadings. Otherwise just use variable names unless it's truly not apparent what they are (like that the result is a recipe in "End Rewrite Instruction").
* 2895Kartik K. Agaram2016-05-031-0/+123
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-13 17:58:37 +0000