about summary refs log tree commit diff stats
path: root/010vm.cc
Commit message (Collapse)AuthorAgeFilesLines
* 2095Kartik K. Agaram2015-08-281-2/+0
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 2043Kartik K. Agaram2015-08-201-0/+1
| | | | | Traces were changing based on whether I was loading a .mu file with 'main' or not.
* 1994 - new primitive: 'create-array'Kartik K. Agaram2015-08-141-1/+3
| | | | | Not strictly necessary, but it might help me stage the introduction of arrays and 'new'.
* 1945Kartik K. Agaram2015-08-061-1/+4
| | | | | | Turns out it is indeed useful to insert code at multiple duplicate labels within a single (long) recipe. Like handle-keyboard-event in edit.mu.
* 1876Kartik K. Agaram2015-07-281-0/+2
|
* 1842 - get layers building again after 2 weeksKartik K. Agaram2015-07-241-0/+15
| | | | | Also, turns out I haven't been building 999spaces.cc in my default build. Now fixed.
* 1814 - save code in editorKartik K. Agaram2015-07-181-2/+2
| | | | | | | Very rudimentary ability to read/write from file+version control. No control over name. Recipes now saved. But what to do about sandboxes?
* 1783 - stable if sluggish on caleb's 512MB serverKartik K. Agaram2015-07-141-2/+0
| | | | | Profiling shows the bulk of time is spent in read_memory, canonize, absolutize. But I'm not sure how to optimize those places.
* 1762 - numbers without types = literalsKartik K. Agaram2015-07-111-0/+4
| | | | Quick hack for demo at balisp meetup today.
* 1703Kartik K. Agaram2015-07-041-6/+13
|
* 1702 - experiment: start using 'ordinal' in namesKartik K. Agaram2015-07-041-30/+30
| | | | | | | 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!
* 1560Kartik K. Agaram2015-06-131-17/+0
|
* 1559Kartik K. Agaram2015-06-131-0/+2
|
* 1558Kartik K. Agaram2015-06-131-0/+10
| | | | Make it possible to check multi-line string literals in the trace.
* 1557Kartik K. Agaram2015-06-131-0/+8
| | | | More concise traces for literal strings.
* 1416Kartik K. Agaram2015-05-211-0/+2
|
* 1414 - traces now robust to new recipes/typesKartik K. Agaram2015-05-211-9/+6
|
* 1407Kartik K. Agaram2015-05-191-1/+1
|
* 1399 - better 'unknown type' warningsKartik K. Agaram2015-05-181-2/+4
| | | | | | | | Implement warnings for types without definitions without constraining where type definitions must appear. We also eliminate the anti-pattern where a change in layer 10 had its test in layer 11 (commit 1383).
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-14/+14
|
* 1390 - support non-integer literalsKartik K. Agaram2015-05-171-2/+2
| | | | | | | | | | | | | | | | | | | | Since '3.14159:literal' looks ugly, we'll just say '3.14159'. It's not like non-integers can be confused for anything but literals. Once I tried to turn reagent values into doubles, I uncovered a bug: arithmetic using signed integers is busted; if either operand of subtraction is unsigned the result is unsigned as well. If it needs to be negative: ka-boom. It was only masked because I was eventually storing the result in a long long int, where it was out of range, and so overflowing into the correct signed value. Once I switched to doubles the unsigned value would indeed fit without overflowing. Ka-boom. Yet another reminder that unsigned integers suck. I started using them mostly to avoid warnings in loops when comparing with .size(), which is usually a size_t. Who knows what other crap lurks here. Just use signed integers everywhere. (And avoid bitwise operators.)
* 1383 - warn on unknown typeKartik K. Agaram2015-05-161-1/+4
| | | | | | | | | | | | | This bit me in the last commit for the first time. Layer 010vm.cc is starting to look weird. It has references to stuff that gets implemented much later, like containers and exclusive containers. Its helpers are getting an increasing amount of logic. And it has no tests. I'm still inclined to think it's useful to have major data structures in one place, even if they aren't used for a bit. But those helpers should perhaps move out somehow or get some tests in the same layer.
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-131-5/+5
| | | | ..now that we support non-integers.
* 1360 - store doubles in memoryKartik K. Agaram2015-05-121-2/+2
| | | | | | | | | | | | | 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-1/+1
|
* 1351Kartik K. Agaram2015-05-121-3/+2
|
* 1299 - stop using [] in any vectorKartik K. Agaram2015-05-071-11/+11
| | | | | | | | | 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 '[^ ]\['
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+259
I've tried to update the Readme, but there are at least a couple of issues.