| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2258 - separate warnings from errors | Kartik K. Agaram | 2015-10-06 | 1 | -8/+8 |
| | | | | | | | | At the lowest level I'm reluctantly starting to see the need for errors that stop the program in its tracks. Only way to avoid memory corruption and security issues. But beyond that core I still want to be as lenient as possible at higher levels of abstraction. | ||||
| * | 2226 - standardize warning format | Kartik K. Agaram | 2015-10-01 | 1 | -8/+8 |
| | | | | | | | | | Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well? | ||||
| * | 2223 | Kartik K. Agaram | 2015-09-30 | 1 | -19/+31 |
| | | |||||
| * | 2214 | Kartik K. Agaram | 2015-09-28 | 1 | -0/+141 |