about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 3165Kartik K. Agaram2016-08-101-1/+1
|
* 3164Kartik K. Agaram2016-08-091-0/+1
| | | | | Have $print in console mode rotate through the screen rather than simply block at the bottom.
* 3163Kartik K. Agaram2016-08-092-3/+20
| | | | | | | | | | | | | | | | | | | | | | | | Experimental: kinda support $print in console mode. It's not perfect and probably will never be, because 'cout' buffers differently from termbox primitives, which can cause console-aware newlines to show up before other (console-oblivious) prints, like in this example program: def main [ open-console $print [abc], 10/newline $print [def], 10/newline wait-for-some-interaction close-console ] And then there's the problem that there's no way for cout to update Display_column. So mixing $print and print will be confusing. Perhaps we should just not mess with Display_* variables inside $print? But then we'll only ever be able to see a single line of $print at a time.
* 3162Kartik K. Agaram2016-08-091-3/+5
|
* 3161Kartik K. Agaram2016-08-091-5/+0
| | | | | | | | | Toss out Scenario_names. It's only checking if we load duplicate scenarios, and we have independent checks for *running* duplicate scenarios. This has the salubrious effect of also allowing lessons to contain regular text scenarios interspersed with their recipes.
* 3160Kartik K. Agaram2016-08-091-9/+1
| | | | Thanks Ella Couch for running into this source of crashes.
* 3159 - pause the lambda->mu translator for a bitKartik K. Agaram2016-08-071-0/+18
| | | | | | | | I'm going to focus on two projects for a while: a) the testable interface for file system and network b) a compiler translating some language to x86 b) might require first gaining some experience programming in Assembly.
* 3158Kartik K. Agaram2016-07-2746-319/+1162
|
* 3157 - more testable 'random' interfaceKartik K. Agaram2016-07-272-4/+59
| | | | Shouldn't break any existing programs using 'random'.
* 3156Kartik K. Agaram2016-07-272-19/+30
| | | | Make 'stream' generic.
* 3155Kartik K. Agaram2016-07-272-4/+4
|
* 3154 - reorg before making 'random' more testableKartik K. Agaram2016-07-2710-0/+0
|
* 3153Kartik K. Agaram2016-07-241-2/+4
|
* 3152Kartik K. Agaram2016-07-241-16/+32
|
* 3151Kartik K. Agaram2016-07-241-1/+3
|
* 3150 - done with parser for s-expressionsKartik K. Agaram2016-07-241-3/+78
|
* 3149Kartik K. Agaram2016-07-241-3/+3
|
* 3148Kartik K. Agaram2016-07-241-0/+17
|
* 3147Kartik K. Agaram2016-07-241-18/+18
|
* 3146Kartik K. Agaram2016-07-241-11/+72
|
* 3145Kartik K. Agaram2016-07-241-4/+48
|
* 3144Kartik K. Agaram2016-07-242-6/+58
| | | | | Fix a bug in phase ordering discovered while trying to stash cells in the lambda compiler.
* 3143Kartik K. Agaram2016-07-241-2/+2
| | | | Fix CI.
* 3142Kartik K. Agaram2016-07-241-24/+43
| | | | | Rewrite ingredients for 'trace' instructions just like 'stash' instructions.
* 3141Kartik K. Agaram2016-07-241-5/+9
| | | | | | | | | Thanks Stephen Malina for helping run into this hole in support for compound types. When I created that assert (commit 2381, Nov 2015) I was thinking only of type ingredients, and didn't realize that compound types could have internal nodes with zero values.
* 3140Kartik K. Agaram2016-07-232-10/+37
| | | | | Manual tests for parse errors because scenarios can't handle assertion failures yet.
* 3139Kartik K. Agaram2016-07-231-2/+6
|
* 3138Kartik K. Agaram2016-07-231-12/+90
|
* 3137Kartik K. Agaram2016-07-224-2/+38
| | | | | | | | | | | | | | | | | | Complicated logic to not run core tests. I only want to disable core tests if: a) I'm changing CFLAGS on the commandline (usually to disable optimizations, causing tests to run slower in a debug cycle) b) I'm not printing a help message (either with just 'mu' or 'mu --help') c) I'm loading other files besides just the core. Under these circumstances I only want to run tests in the files explicitly loaded at the commandline. This is all pretty hairy, in spite of my attempts to document it in four different places. I might end up taking it all out the first time I need to run core tests under all these conditions.
* 3136Kartik K. Agaram2016-07-221-2/+0
|
* 3135Kartik K. Agaram2016-07-221-5/+14
| | | | Parsing pairs of atoms.
* 3134Kartik K. Agaram2016-07-221-1/+1
|
* 3133Kartik K. Agaram2016-07-221-1/+1
| | | | Don't die if an instruction accidentally has too many products.
* 3132Kartik K. Agaram2016-07-221-21/+19
|
* 3131Kartik K. Agaram2016-07-222-4/+55
| | | | | Reorganize parser to make room for parsing pairs. But first test for pairs is still failing.
* 3130Kartik K. Agaram2016-07-221-3/+20
| | | | Handle multi-character atoms.
* 3129Kartik K. Agaram2016-07-222-0/+39
| | | | Degenerate 'parser' that handles just atoms of one character.
* 3128Kartik K. Agaram2016-07-221-1/+2
|
* 3127Kartik K. Agaram2016-07-221-0/+43
|
* 3126Kartik K. Agaram2016-07-224-16/+3
|
* 3125Kartik K. Agaram2016-07-221-3/+19
|
* 3124Kartik K. Agaram2016-07-222-22/+28
| | | | | Reorganize data structure for lambda cells. Create our first real unit test for the compiler in the process.
* 3123Kartik K. Agaram2016-07-221-5/+16
| | | | | | Bugfix: permit dummy product when trying to convert exclusive containers. The 'status' product is still required, however. Without it there's no point to calling 'maybe-convert'.
* 3122Kartik K. Agaram2016-07-221-16/+4
| | | | More accurate count of failing tests.
* 3121 - very preliminary spike on a compilerKartik K. Agaram2016-07-221-0/+60
| | | | | Nothing runs yet. Just spewing out code at this point, as a kind of sketching.
* 3120Kartik K. Agaram2016-07-2132-125/+130
| | | | | | | | Always show instruction before any transforms in error messages. This is likely going to make some errors unclear because they *need* to show the original instruction. But if we don't have tests for those situations did they ever really work?
* 3119Kartik K. Agaram2016-07-213-2/+50
| | | | | | | Warn if 'put' or 'put-index' has a mismatch in the type of the product, not just the name. It won't do any harm, but could be misleading to a later reader. In both instructions, the product is just for documentation.
* 3118Kartik K. Agaram2016-07-211-2/+2
| | | | | Failures in scenarios should consistently trigger the summary message showing number of failed tests.
* 3117Kartik K. Agaram2016-07-2020-37/+199
|
* 3116Kartik K. Agaram2016-07-201-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 14:11:32 +0000