about summary refs log tree commit diff stats
path: root/032array.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2581 - make space for the refcount in address:sharedKartik K. Agaram2016-01-201-1/+2
| | | | | | | | | | | We don't yet actually maintain the refcount. That's next. Hardest part of this was debugging the assume-console scenarios in layer 85. That took some detailed manual diffing of traces (because the output of diff was no good). New tracing added in this commit add 8% to .traces LoC. Commented out trace() calls (used during debugging) make that 45%.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-3/+5
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2555Kartik K. Agaram2016-01-111-2/+2
|
* 2475 - allow addresses to be converted to numbersKartik K. Agaram2015-11-271-2/+2
| | | | It's just the other direction we want to avoid.
* 2473 - bad idea to use /raw with multiple intentionsKartik K. Agaram2015-11-221-6/+6
| | | | | /raw is to express absolute addresses /unsafe is to sidestep type-checking in test setup
* 2459Kartik K. Agaram2015-11-181-0/+12
|
* 2450 - another pesky bugKartik K. Agaram2015-11-151-0/+12
|
* 2399 - consistent debug_string vocabularyKartik K. Agaram2015-11-081-2/+2
|
* 2377 - stop using operator[] in mapKartik K. Agaram2015-11-061-26/+26
| | | | | | | | | | | | | | | | I'm still seeing all sorts of failures in turning on layer 11 of edit/, so I'm backing away and nailing down every culprit I run into. First up: stop accidentally inserting empty objects into maps during lookups. Commands run: $ sed -i 's/\(Recipe_ordinal\|Recipe\|Type_ordinal\|Type\|Memory\)\[\([^]]*\)\] = \(.*\);/put(\1, \2, \3);/' 0[1-9]* $ vi 075scenario_console.cc # manually fix up Memory[Memory[CONSOLE]] $ sed -i 's/\(Memory\)\[\([^]]*\)\]/get_or_insert(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe_ordinal\|Type_ordinal\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* $ sed -i 's/\(Recipe\|Type\)\[\([^]]*\)\]/get(\1, \2)/' 0[1-9]* Now mu dies pretty quickly because of all the places I try to lookup a missing value.
* 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
|