| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | 1475 | Kartik K. Agaram | 2015-05-26 | 1 | -5/+16 | |
| | | ||||||
| * | 1474 - another warning | Kartik K. Agaram | 2015-05-26 | 6 | -17/+47 | |
| | | ||||||
| * | 1473 | Kartik K. Agaram | 2015-05-26 | 4 | -30/+60 | |
| | | ||||||
| * | 1471 | Kartik K. Agaram | 2015-05-26 | 9 | -9/+9 | |
| | | ||||||
| * | 1470 | Kartik K. Agaram | 2015-05-26 | 2 | -10/+10 | |
| | | ||||||
| * | 1469 | Kartik K. Agaram | 2015-05-26 | 2 | -8/+8 | |
| | | ||||||
| * | 1468 | Kartik K. Agaram | 2015-05-26 | 1 | -3/+3 | |
| | | ||||||
| * | 1467 | Kartik K. Agaram | 2015-05-26 | 1 | -1/+1 | |
| | | ||||||
| * | 1466 | Kartik K. Agaram | 2015-05-26 | 1 | -4/+4 | |
| | | ||||||
| * | 1465 | Kartik K. Agaram | 2015-05-26 | 1 | -5/+24 | |
| | | ||||||
| * | 1464 | Kartik K. Agaram | 2015-05-26 | 1 | -0/+13 | |
| | | ||||||
| * | 1463 | Kartik K. Agaram | 2015-05-26 | 1 | -4/+5 | |
| | | ||||||
| * | 1462 - blurbs for example programs | Kartik K. Agaram | 2015-05-26 | 1 | -1/+28 | |
| | | ||||||
| * | 1461 - descriptions/table of contents for the layers | Kartik K. Agaram | 2015-05-26 | 55 | -127/+196 | |
| | | ||||||
| * | 1460 | Kartik K. Agaram | 2015-05-25 | 1 | -1/+8 | |
| | | ||||||
| * | 1459 | Kartik K. Agaram | 2015-05-25 | 64 | -1355/+2940 | |
| | | ||||||
| * | 1458 | Kartik K. Agaram | 2015-05-25 | 3 | -6/+19 | |
| | | | | | | | | | | | | | | | | | While pushing out color support in fake screens I realized I've been complecting the special-case of a special-case to transform literal-string arguments for 'new'. As a result I hadn't been catching bad habits like giving its arg the wrong type. Now we have cleaner separation of the two variants of 'new', a few more checks, and better error messages when we mis-call it. Aside: I've added a third goto target. Sliding into spaghetti? Keep an eye on it. This goto might become a common pattern: a layer hooking into a previous one to prevent it from happening. In this case new on literal-strings prevents the transform for new from triggering. | |||||
| * | 1457 - print to display in color | Kartik K. Agaram | 2015-05-25 | 2 | -2/+7 | |
| | | | | | Just foreground color for now. | |||||
| * | 1456 | Kartik K. Agaram | 2015-05-25 | 1 | -2/+2 | |
| | | ||||||
| * | 1455 | Kartik K. Agaram | 2015-05-24 | 2 | -3/+3 | |
| | | ||||||
| * | 1454 | Kartik K. Agaram | 2015-05-24 | 1 | -20/+17 | |
| | | ||||||
| * | 1453 | Kartik K. Agaram | 2015-05-24 | 1 | -1/+1 | |
| | | ||||||
| * | 1452 | Kartik K. Agaram | 2015-05-24 | 1 | -13/+32 | |
| | | | | | bugfix | |||||
| * | 1451 - share post-processing between all call instructions | Kartik K. Agaram | 2015-05-24 | 4 | -27/+10 | |
| | | ||||||
| * | 1450 | Kartik K. Agaram | 2015-05-24 | 1 | -1/+1 | |
| | | ||||||
| * | 1449 - use prompt/abort for delimited continuations | Kartik K. Agaram | 2015-05-24 | 1 | -44/+53 | |
| | | | | | This is *much* more nice-looking scenario. | |||||
| * | 1448 | Kartik K. Agaram | 2015-05-24 | 1 | -0/+1 | |
| | | ||||||
| * | 1447 | Kartik K. Agaram | 2015-05-24 | 2 | -20/+55 | |
| | | ||||||
| * | 1446 - delimited continuations | Kartik K. Agaram | 2015-05-23 | 1 | -0/+145 | |
| | | | | | This is probably going to be embarrassing. | |||||
| * | 1445 | Kartik K. Agaram | 2015-05-23 | 1 | -2/+1 | |
| | | ||||||
| * | 1444 | Kartik K. Agaram | 2015-05-23 | 3 | -5/+9 | |
| | | ||||||
| * | 1443 - bugfix in continuation support | Kartik K. Agaram | 2015-05-23 | 1 | -0/+6 | |
| | | | | | Thanks Anthony Di Franco (http://dfko.net) | |||||
| * | 1442 | Kartik K. Agaram | 2015-05-23 | 1 | -1/+1 | |
| | | ||||||
| * | 1441 - give up on unit tests for 'random' | Kartik K. Agaram | 2015-05-23 | 1 | -1/+2 | |
| | | | | | | | | | | | I'd been hoping that I could simply pass in the previously-returned number to srand() to generate the next one in the series. But looks like rand() is more stateful than that. Another weirdness: I put in 'round' in the same layer because of the vague idea that it would help generate random integers. But that's all we get anyway. | |||||
| * | 1440 | Kartik K. Agaram | 2015-05-23 | 1 | -0/+1 | |
| | | ||||||
| * | 1439 - support clang in addition to gcc | Kartik K. Agaram | 2015-05-23 | 3 | -3/+3 | |
| | | ||||||
| * | 1438 | Kartik K. Agaram | 2015-05-23 | 1 | -0/+42 | |
| | | ||||||
| * | 1437 | Kartik K. Agaram | 2015-05-23 | 1 | -1/+1 | |
| | | ||||||
| * | 1436 | Kartik K. Agaram | 2015-05-23 | 3 | -3/+8 | |
| | | ||||||
| * | 1435 | Kartik K. Agaram | 2015-05-23 | 1 | -3/+7 | |
| | | ||||||
| * | 1434 - support all unicode spaces | Kartik K. Agaram | 2015-05-23 | 7 | -21/+128 | |
| | | ||||||
| * | 1433 - 'trim' strings | Kartik K. Agaram | 2015-05-23 | 1 | -0/+96 | |
| | | ||||||
| * | 1432 - contrast scenarios and recipes | Kartik K. Agaram | 2015-05-23 | 1 | -2/+3 | |
| | | ||||||
| * | 1431 | Kartik K. Agaram | 2015-05-23 | 1 | -3/+3 | |
| | | ||||||
| * | 1430 | Kartik K. Agaram | 2015-05-22 | 1 | -1/+9 | |
| | | ||||||
| * | 1429 - third, possibly successful impl of collapse | Kartik K. Agaram | 2015-05-22 | 1 | -10/+5 | |
| | | ||||||
| * | 1428 - second attempt | Kartik K. Agaram | 2015-05-22 | 1 | -4/+1 | |
| | | | | | | This doesn't work either; some children are collapsed but not others (after the first expanded child). | |||||
| * | 1427 - first attempt at collapsing lines | Kartik K. Agaram | 2015-05-22 | 1 | -0/+27 | |
| | | | | | | | Collapsing is harder than expanding. This approach doesn't work because I end up sometimes with visible lines whose parents aren't visible anymore. | |||||
| * | 1426 | Kartik K. Agaram | 2015-05-22 | 1 | -4/+0 | |
| | | | | | | | As often happens, the asserts I come up with fail to survive contact with reality. In this case because the current line may not have anything left to expand. | |||||
| * | 1425 | Kartik K. Agaram | 2015-05-22 | 1 | -0/+1 | |
| | | ||||||