about summary refs log tree commit diff stats
path: root/032array.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2313Kartik K. Agaram2015-10-291-2/+2
|
* 2311Kartik K. Agaram2015-10-291-1/+1
|
* 2293Kartik K. Agaram2015-10-271-1/+1
|
* 2283 - represent each /property as a treeKartik K. Agaram2015-10-261-4/+4
|
* 2280Kartik K. Agaram2015-10-261-1/+1
|
* 2277 - reagents now have a tree of typesKartik K. Agaram2015-10-251-21/+27
|
* 2270Kartik K. Agaram2015-10-121-1/+1
| | | | Thanks Caleb Couch.
* 2258 - separate warnings from errorsKartik K. Agaram2015-10-061-31/+31
| | | | | | | At the lowest level I'm reluctantly starting to see the need for errors that stop the program in its tracks. Only way to avoid memory corruption and security issues. But beyond that core I still want to be as lenient as possible at higher levels of abstraction.
* 2242Kartik K. Agaram2015-10-051-3/+52
|
* 2228 - index-checking for arraysKartik K. Agaram2015-10-011-23/+47
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-011-9/+9
| | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well?
* 2218 - check types in instructions much earlierKartik K. Agaram2015-09-301-2/+2
| | | | | | | | | Front-loads it a bit more than I'd like, but the payoff is that other recipes will now be able to describe the type checks right next to their operation. I'm also introducing a new use of /raw with literals to indicate unsafe typecasts.
* 2214Kartik K. Agaram2015-09-281-28/+0
|
* 2213 - start moving type checks out of 'run'Kartik K. Agaram2015-09-281-0/+28
| | | | | That way we only have to check each static instruction once, rather than every time it runs.
* 2199 - stop printing numbers in scientific notationKartik K. Agaram2015-09-141-2/+2
| | | | | | | | | | | Turns out the default format for printing floating point numbers is neither 'scientific' nor 'fixed' even though those are the only two options offered. Reading the C++ standard I found out that the default (modulo locale changes) is basically the same as the printf "%g" format. And "%g" is basically the shorter of: a) %f with trailing zeros trimmed b) %e So we'll just do %f and trim trailing zeros.
* 2064Kartik K. Agaram2015-08-241-1/+1
| | | | Adjust spaces in 'stash'.
* 2003Kartik K. Agaram2015-08-141-5/+0
| | | | Minor issue in building until just layer 32.
* 2000 - stop constantly copying large arrays aroundKartik K. Agaram2015-08-141-3/+10
|
* 1994 - new primitive: 'create-array'Kartik K. Agaram2015-08-141-24/+78
| | | | | Not strictly necessary, but it might help me stage the introduction of arrays and 'new'.
* 1988 - handle reagents without typesKartik K. Agaram2015-08-131-3/+3
| | | | | | This can happen if 'canonize' fails. Make sure it doesn't kill mu. Thanks Caleb Couch.
* 1975 - let's start using traces in lessonsKartik K. Agaram2015-08-101-0/+10
| | | | | More friendly way to 'stash' stuff in the trace so that you can toggle lines of code to see their stashed traces.
* 1962Kartik K. Agaram2015-08-091-2/+2
| | | | Standardize test names.
* 1950Kartik K. Agaram2015-08-071-7/+7
|
* 1923Kartik K. Agaram2015-08-021-4/+3
| | | | | | | | | | Still iterating on the right way to handle incorrect number of ingredients. My first idea of creating null results doesn't really work once they're used in later instructions. Just add a warning at one place in the run loop, but otherwise only add products when there's something to save in them. Undoes some work around commit 1886.
* 1909 - clean up all null pointers of that ilkKartik K. Agaram2015-07-311-6/+16
|
* 1886 - gracefully handle malformed ingredientsKartik K. Agaram2015-07-291-3/+4
| | | | | | | | For example: x:number <- index y:address:array:number, 3 (forgetting to do a lookup) Thanks Caleb Couch.
* 1882Kartik K. Agaram2015-07-291-6/+6
|
* 1879 - types required at first mention of a nameKartik K. Agaram2015-07-281-1/+1
| | | | That should avoid many issues with typos in names.
* 1869 - rename the /deref property to /lookupKartik K. Agaram2015-07-281-6/+6
| | | | Should be a little bit more mnemonic.
* 1868 - start using naked literals everywhereKartik K. Agaram2015-07-281-70/+70
| | | | First step to reducing typing burden. Next step: inferring types.
* 1848 - core instructions now check for ingredientsKartik K. Agaram2015-07-251-6/+13
| | | | Also standardized warnings.
* 1844 - explicitly end each trace lineKartik K. Agaram2015-07-251-12/+12
| | | | | | | | | More verbose, but it saves trouble when debugging; there's never something you thought should be traced but just never came out the other end. Also got rid of fatal errors entirely. Everything's a warning now, and code after a warning isn't guaranteed to run.
* 1835Kartik K. Agaram2015-07-241-3/+12
|
* 1830Kartik K. Agaram2015-07-231-1/+1
|
* 1800 - ah, found the bounds-checking bugKartik K. Agaram2015-07-171-11/+77
| | | | I was counting locations when I should have been counting elements.
* 1744 - support just two editors rather than a listKartik K. Agaram2015-07-091-0/+4
| | | | | Current model: you click on something to put it on the editor at the top of the column. Worth a shot.
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-12/+12
| | | | | | | It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
* 1611 - switch to keyboard+mouse eventsKartik K. Agaram2015-06-201-2/+2
|
* 1586Kartik K. Agaram2015-06-171-1/+1
|
* 1474 - another warningKartik K. Agaram2015-05-261-5/+8
|
* 1473Kartik K. Agaram2015-05-261-0/+28
|
* 1417 - draft zoom levels in tracesKartik K. Agaram2015-05-211-6/+6
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-24/+0
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-8/+8
|
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-34/+34
| | | | ..now that we support non-integers.
* 1360 - store doubles in memoryKartik K. Agaram2015-05-121-3/+3
| | | | | | | | | | | | | This is a far cleaner way to provide *some* floating-point support. We can only represent signed integers up to 2^51 rather than 2^63. But in exchange we don't have to worry about it elsewhere, and it's probably faster than checking tag bits in every operation. Hmm, yeah, surprised how easy this was. I think I'll give up on the other approach. I still don't have non-integer literals. But we won't bother with those until we need them. `3.14159:literal` seems ugly.
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-12/+9
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-9/+12
| | | | | | | | | | | | | | | I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily *persuade others* that I've gotten it right.
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-1/+1
| | | | | | | | | Useful check: $ grep "[^ '\"]\[[^\"]" *.cc \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |perl -pwe 's/\Wargv\[|\WTests\[|\Wframe\[|\WMemory\[|\WName\[|\WSurrounding_space\[|\WRecipe\[|\WType\[|\WRecipe_number\[|\WType_number\[|\WBefore_fragments\[|\WAfter_fragments\[//g' \ |grep '[^ ]\['
* 1298 - better ingredient/product handlingKartik K. Agaram2015-05-071-31/+16
| | | | | | | | | | | | | | | | | | | All primitives now always write to all their products. If a product is not used that's fine, but if an instruction seems to expect too many products mu will complain. In the process, many primitives can operate on more than two ingredients where it seems intuitive. You can add or divide more than two numbers together, copy or negate multiple corresponding locations, etc. There's one remaining bit of ugliness. Some instructions like get/get-address, index/index-address, wait-for-location, these can unnecessarily load values from memory when they don't need to. Useful vim commands: %s/ingredients\[\([^\]]*\)\]/ingredients.at(\1)/gc %s/products\[\([^\]]*\)\]/products.at(\1)/gc .,$s/\[\(.\)]/.at(\1)/gc