Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | 2765 | Kartik K. Agaram | 2016-03-12 | 3 | -14/+14 |
| | | | | | Get rid of a local variable that was only serving to render unreadable the code for reclaiming allocated memory. | ||||
* | 2764 | Kartik K. Agaram | 2016-03-12 | 1 | -2/+3 |
| | |||||
* | 2763 | Kartik K. Agaram | 2016-03-12 | 1 | -10/+11 |
| | |||||
* | 2762 | Kartik K. Agaram | 2016-03-12 | 4 | -5/+5 |
| | |||||
* | 2761 | Kartik K. Agaram | 2016-03-11 | 1 | -10/+8 |
| | |||||
* | 2760 | Kartik K. Agaram | 2016-03-11 | 2 | -0/+0 |
| | |||||
* | 2759 | Kartik K. Agaram | 2016-03-10 | 5 | -316/+19 |
| | | | | Clean up tangle/ helper. | ||||
* | 2758 | Kartik K. Agaram | 2016-03-10 | 1 | -4/+4 |
| | |||||
* | 2757 | Kartik K. Agaram | 2016-03-10 | 1 | -3/+3 |
| | |||||
* | 2756 | Kartik K. Agaram | 2016-03-10 | 1 | -6/+6 |
| | |||||
* | 2755 | Kartik K. Agaram | 2016-03-10 | 1 | -10/+1 |
| | |||||
* | 2754 | Kartik K. Agaram | 2016-03-10 | 1 | -2/+2 |
| | |||||
* | 2753 | Kartik K. Agaram | 2016-03-10 | 1 | -3/+3 |
| | |||||
* | 2752 | Kartik K. Agaram | 2016-03-10 | 1 | -1/+2 |
| | |||||
* | 2751 | Kartik K. Agaram | 2016-03-10 | 3 | -103/+49 |
| | |||||
* | 2750 - take out all philosophy from the Readme | Kartik K. Agaram | 2016-03-10 | 1 | -197/+61 |
| | |||||
* | 2749 | Kartik K. Agaram | 2016-03-09 | 2 | -36/+36 |
| | |||||
* | 2748 | Kartik K. Agaram | 2016-03-09 | 2 | -20/+20 |
| | |||||
* | 2747 | Kartik K. Agaram | 2016-03-09 | 1 | -0/+4 |
| | | | | Thanks Ben Trask for engaging with my arguments. | ||||
* | 2746 | Kartik K. Agaram | 2016-03-09 | 4 | -8/+6 |
| | |||||
* | 2745 | Kartik K. Agaram | 2016-03-09 | 79 | -78/+79 |
| | |||||
* | 2744 | Kartik K. Agaram | 2016-03-09 | 95 | -242/+245 |
| | | | | Tweak colors and font-sizes in generated html. | ||||
* | 2743 | Kartik K. Agaram | 2016-03-09 | 95 | -6019/+5666 |
| | | | | | Looks like "TOhtml | <other command>" doesn't work on Mac OS X for some reason.. | ||||
* | 2742 | Kartik K. Agaram | 2016-03-08 | 3 | -41/+2 |
| | |||||
* | 2741 | Kartik K. Agaram | 2016-03-08 | 1 | -0/+0 |
| | |||||
* | 2740 | Kartik K. Agaram | 2016-03-08 | 3 | -0/+9 |
| | |||||
* | 2739 | Kartik K. Agaram | 2016-03-08 | 3 | -1/+1 |
| | |||||
* | 2738 | Kartik K. Agaram | 2016-03-08 | 1 | -16/+16 |
| | |||||
* | 2737 | Kartik K. Agaram | 2016-03-08 | 1 | -1/+1 |
| | |||||
* | 2736 | Kartik K. Agaram | 2016-03-08 | 1 | -0/+8 |
| | |||||
* | 2735 - define recipes using 'def' | Kartik K. Agaram | 2016-03-08 | 98 | -1342/+1344 |
| | | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu. | ||||
* | 2734 | Kartik K. Agaram | 2016-03-08 | 1 | -7/+7 |
| | |||||
* | 2733 | Kartik K. Agaram | 2016-03-07 | 1 | -0/+2 |
| | |||||
* | 2732 | Kartik K. Agaram | 2016-03-07 | 1 | -1/+10 |
| | |||||
* | 2731 | Kartik K. Agaram | 2016-03-07 | 1 | -1/+1 |
| | |||||
* | 2730 | Kartik K. Agaram | 2016-03-07 | 1 | -43/+159 |
| | |||||
* | 2729 | Kartik K. Agaram | 2016-03-06 | 1 | -7/+12 |
| | |||||
* | 2728 - don't ignore /space: while checking types | Kartik K. Agaram | 2016-03-04 | 5 | -39/+53 |
| | |||||
* | 2727 - don't ignore /space: in immutability checks | Kartik K. Agaram | 2016-03-04 | 1 | -12/+50 |
| | | | | | | | | | | | | | | | Right now there's now way to tag variables from surrounding spaces (lexical scopes) as immutable. Should I assume they're immutable unless the surrounding space is passed out in addition to passed in? What if it comes from a global? Or should we explicitly specify modified variables in the header, even if they'll never be saved anywhere? We don't use these features much yet, wait until we need it. Mutability checks are an optional layer and can't cause memory corruption. Lack of type-checking in the global space, however, *can* cause memory corruption. That's the biggest open issue right now. | ||||
* | 2726 | Kartik K. Agaram | 2016-03-04 | 1 | -3/+4 |
| | |||||
* | 2725 - dev machine is now Mac | Kartik K. Agaram | 2016-03-02 | 1 | -0/+1 |
| | |||||
* | 2724 - document failures of /space:global | Kartik K. Agaram | 2016-03-01 | 2 | -7/+15 |
| | |||||
* | 2723 | Kartik K. Agaram | 2016-02-29 | 1 | -5/+2 |
| | |||||
* | 2722 - fix a crash; thanks Ella Couch! | Kartik K. Agaram | 2016-02-28 | 1 | -2/+24 |
| | |||||
* | 2721 | Kartik K. Agaram | 2016-02-28 | 2 | -11/+11 |
| | |||||
* | 2720 - hash table teetering but alive | Kartik K. Agaram | 2016-02-28 | 3 | -11/+86 |
| | | | | More bugs fixed in generics to make this work. | ||||
* | 2719 - improvements to generics | Kartik K. Agaram | 2016-02-28 | 1 | -17/+65 |
| | |||||
* | 2718 - stop crashing on unknown space | Kartik K. Agaram | 2016-02-26 | 3 | -4/+29 |
| | | | | | I'm going to stop wasting precious first-line characters on 'bugfix:'. It's going to be all bugfixes for a while I think. | ||||
* | 2717 - bugfix for dilated reagents | Kartik K. Agaram | 2016-02-26 | 2 | -0/+15 |
| | | | | Make sure static arrays can take compound types. | ||||
* | 2716 - more holes in immutability checks | Kartik K. Agaram | 2016-02-26 | 4 | -13/+104 |
| | | | | | We're still not done. Layer 60 doesn't yet handle variables in surrounding spaces. There's probably other issues.. |