about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1404 - undefined-behavior checks using clangKartik K. Agaram2015-05-182-2/+10
| | | | | | | | While I'm at it I also explored turning on optimization. With optimization compile+test of the chessboard app takes 10+3s, while without optimization it takes 3+8s. So we're still better off without optimizations in a tight debug loop. (Since we stopped tracing the big chessboard test.)
* 1403Kartik K. Agaram2015-05-181-7/+6
|
* 1402Kartik K. Agaram2015-05-181-4/+6
|
* 1401 - shave 80% off chessboard test timeKartik K. Agaram2015-05-183-1/+15
| | | | It was all going to laboriously writing out 300+ MB to disk.
* 1400Kartik K. Agaram2015-05-181-5/+5
|
* 1399 - better 'unknown type' warningsKartik K. Agaram2015-05-185-14/+100
| | | | | | | | 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).
* 1398Kartik K. Agaram2015-05-181-2/+23
|
* 1397 - support unicode in screen checksKartik K. Agaram2015-05-182-31/+103
|
* 1396Kartik K. Agaram2015-05-171-16/+40
|
* 1395Kartik K. Agaram2015-05-171-3/+2
|
* 1394Kartik K. Agaram2015-05-171-2/+2
|
* 1393Kartik K. Agaram2015-05-171-0/+18
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-1737-331/+365
|
* 1390 - support non-integer literalsKartik K. Agaram2015-05-175-24/+60
| | | | | | | | | | | | | | | | | | | | 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.)
* 1389Kartik K. Agaram2015-05-162-3/+3
|
* 1388Kartik K. Agaram2015-05-161-0/+1
|
* 1387Kartik K. Agaram2015-05-168-15/+15
|
* 1385Kartik K. Agaram2015-05-163-1/+4
|
* 1384Kartik K. Agaram2015-05-161-0/+6
|
* 1383 - warn on unknown typeKartik K. Agaram2015-05-165-2/+21
| | | | | | | | | | | | | 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.
* 1382 - implement continuationsKartik K. Agaram2015-05-161-0/+76
|
* 1381Kartik K. Agaram2015-05-151-1/+14
|
* 1380 - list data structureKartik K. Agaram2015-05-151-0/+55
|
* 1379 - avoid all uninitialized-memory issuesKartik K. Agaram2015-05-151-1/+13
|
* 1378Kartik K. Agaram2015-05-151-0/+1
|
* 1377 - handle github errorsKartik K. Agaram2015-05-141-1/+1
|
* 1376 - update github docsKartik K. Agaram2015-05-1448-1849/+3641
|
* 1375 - cleanupKartik K. Agaram2015-05-141-4/+3
|
* 1374 - chessboard end-to-end test passes!Kartik K. Agaram2015-05-145-19/+91
| | | | | | | | | | After like 40 seconds (because of the 120-column screen), but whatever. The final bug was that clear-screen wasn't actually working right for fake screens. (The trace is too large for github, so I'm going to leave it out for now.)
* 1373Kartik K. Agaram2015-05-141-1/+4
|
* 1372 - new chessboard test no longer hangingKartik K. Agaram2015-05-145-27/+37
| | | | Still failing, though.
* 1371Kartik K. Agaram2015-05-141-16/+0
|
* 1370Kartik K. Agaram2015-05-141-1/+1
|
* 1369Kartik K. Agaram2015-05-144-25/+25
| | | | | Delete comment-out marker from inside mu strings. Have to do this manually for now.
* 1368 - alias carriage-return and newlineKartik K. Agaram2015-05-146-12/+79
| | | | | | | CRLF still shows as two newlines, though. Cross that bridge when we get to it. The new chessboard test is still hanging, though.
* 1367Kartik K. Agaram2015-05-144-101/+106
|
* 1366Kartik K. Agaram2015-05-141-3/+3
|
* 1365Kartik K. Agaram2015-05-131-11/+4
|
* 1364 - trace call-stack when switching routinesKartik K. Agaram2015-05-138-28/+43
| | | | Drop the #$%# 'encapsulated' stack ADT.
* 1363 - rename 'integer' to 'number'Kartik K. Agaram2015-05-1341-918/+922
| | | | ..now that we support non-integers.
* 1362Kartik K. Agaram2015-05-135-15/+15
| | | | | | | | Mu allows us to use multiple ingredients/products without commas, but make sure we don't. $ grep "<- [^ ]\+ [^#\[,]* [^#\[,]*$" * $ grep "^[ ]*[^ #,][^#,]* [^#,]* <- " *
* 1361Kartik K. Agaram2015-05-121-2/+2
| | | | | This one layer had grown a dependency on a later layer. I could swear I ran all the tests when I fixed the test harness in 1358..
* 1360 - store doubles in memoryKartik K. Agaram2015-05-129-24/+31
| | | | | | | | | | | | | 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.
* 1359Kartik K. Agaram2015-05-121-1/+3
|
* 1358 - inform shell of test failureKartik K. Agaram2015-05-121-1/+3
|
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-1230-388/+127
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-1229-193/+316
| | | | | | | | | | | | | | | 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.
* 1355Kartik K. Agaram2015-05-121-0/+11
|
* 1354Kartik K. Agaram2015-05-122-6/+6
|
* 1353Kartik K. Agaram2015-05-121-1/+4
|