about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* 1352Kartik K. Agaram2015-05-121-1/+1
|
* 1351Kartik K. Agaram2015-05-121-3/+2
|
* 1350Kartik K. Agaram2015-05-111-1/+0
|
* 1349 - snapshot: floating-point supportKartik K. Agaram2015-05-111-0/+139
|
* 1348Kartik K. Agaram2015-05-111-1/+1
|
* 1346Kartik K. Agaram2015-05-111-0/+3
| | | | | | On my ubuntu 14.04.1 + gcc 4.8.2 machine, ifstream doesn't actually raise an error on trying to open a non-existent file until you try to do something with it. Garbage!
* 1345Kartik K. Agaram2015-05-119-19/+44
|
* 1344Kartik K. Agaram2015-05-111-0/+10
|
* 1343Kartik K. Agaram2015-05-116-7/+7
|
* 1342Kartik K. Agaram2015-05-111-8/+8
|
* 1341Kartik K. Agaram2015-05-112-8/+19
|
* 1340Kartik K. Agaram2015-05-111-1/+4
|
* 1339Kartik K. Agaram2015-05-102-45/+49
|
* 1338Kartik K. Agaram2015-05-101-2/+2
|
* 1337Kartik K. Agaram2015-05-101-0/+2
|
* 1336Kartik K. Agaram2015-05-101-6/+18
|
* 1335Kartik K. Agaram2015-05-101-28/+2
|
* 1334Kartik K. Agaram2015-05-101-16/+18
|
* 1333Kartik K. Agaram2015-05-101-3/+11
|
* 1331Kartik K. Agaram2015-05-102-3/+5
|
* 1330Kartik K. Agaram2015-05-103-1/+8
|
* 1329Kartik K. Agaram2015-05-102-0/+12
|
* 1328 - another error messageKartik K. Agaram2015-05-101-0/+36
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-02 21:21:14 +0000