about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 2233 - basic checks for non-primitive recipesKartik K. Agaram2015-10-012-8/+14
| | | | This came last because we had to ensure all primitives are covered.
* 2232Kartik K. Agaram2015-10-0116-129/+435
|
* 2231Kartik K. Agaram2015-10-011-0/+1
|
* 2230Kartik K. Agaram2015-10-011-11/+17
|
* 2229Kartik K. Agaram2015-10-011-0/+6
|
* 2228 - index-checking for arraysKartik K. Agaram2015-10-011-23/+47
|
* 2227 - offset-checking for containersKartik K. Agaram2015-10-014-42/+88
|
* 2226 - standardize warning formatKartik K. Agaram2015-10-0133-175/+186
| | | | | | | | 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?
* 2225Kartik K. Agaram2015-10-014-63/+91
|
* 2224Kartik K. Agaram2015-09-301-3/+3
|
* 2223Kartik K. Agaram2015-09-302-20/+32
|
* 2222Kartik K. Agaram2015-09-303-14/+14
|
* 2221Kartik K. Agaram2015-09-304-19/+46
|
* 2220Kartik K. Agaram2015-09-303-34/+121
|
* 2219Kartik K. Agaram2015-09-301-12/+4
|
* 2218 - check types in instructions much earlierKartik K. Agaram2015-09-3013-132/+177
| | | | | | | | | Front-loads it a bit more than I'd like, but the payoff is that other recipes will now be able to describe the type checks right next to their operation. I'm also introducing a new use of /raw with literals to indicate unsafe typecasts.
* 2217Kartik K. Agaram2015-09-292-0/+0
|
* 2216Kartik K. Agaram2015-09-292-1/+13
|
* 2215Kartik K. Agaram2015-09-291-1/+1
|
* 2214Kartik K. Agaram2015-09-288-33/+39
|
* 2213 - start moving type checks out of 'run'Kartik K. Agaram2015-09-284-43/+88
| | | | | That way we only have to check each static instruction once, rather than every time it runs.
* 2212Kartik K. Agaram2015-09-281-6/+6
|
* 2211Kartik K. Agaram2015-09-281-0/+0
|
* 2209Kartik K. Agaram2015-09-261-4/+4
|
* 2208Kartik K. Agaram2015-09-261-0/+5
|
* 2207Kartik K. Agaram2015-09-261-1/+1
|
* 2206 - fix missing ingredientsKartik K. Agaram2015-09-263-5/+5
| | | | | How the heck was this working until now? There must be redundant moves. And was I clobbering test data?
* 2205 - warn on missing ingredientKartik K. Agaram2015-09-182-1/+13
| | | | ..unless you explicitly ignore the found? result.
* 2204Kartik K. Agaram2015-09-161-2/+8
|
* 2203 - show recipe warnings in 'mu sandbox'Kartik K. Agaram2015-09-152-9/+8
|
* 2202 - don't let editor die on syntax errorsKartik K. Agaram2015-09-153-35/+50
| | | | | Bugfix to 2186. I hadn't taken care of 'reload' as cleanly as I had 'run-interactive'.
* 2201Kartik K. Agaram2015-09-151-2/+4
|
* 2200Kartik K. Agaram2015-09-152-10/+14
|
* 2199 - stop printing numbers in scientific notationKartik K. Agaram2015-09-1413-33/+79
| | | | | | | | | | | Turns out the default format for printing floating point numbers is neither 'scientific' nor 'fixed' even though those are the only two options offered. Reading the C++ standard I found out that the default (modulo locale changes) is basically the same as the printf "%g" format. And "%g" is basically the shorter of: a) %f with trailing zeros trimmed b) %e So we'll just do %f and trim trailing zeros.
* 2197Kartik K. Agaram2015-09-141-1/+1
|
* 2196Kartik K. Agaram2015-09-142-3/+1
|
* 2195Kartik K. Agaram2015-09-141-2/+2
|
* 2194Kartik K. Agaram2015-09-141-2/+2
|
* 2193Kartik K. Agaram2015-09-141-2/+2
|
* 2192Kartik K. Agaram2015-09-141-0/+1
|
* 2191Kartik K. Agaram2015-09-131-28/+26
|
* 2190Kartik K. Agaram2015-09-121-2/+3
|
* 2189Kartik K. Agaram2015-09-121-1/+1
|
* 2188Kartik K. Agaram2015-09-121-2/+2
|
* 2187Kartik K. Agaram2015-09-122-1/+5
|
* 2186 - kill the current routine on first errorKartik K. Agaram2015-09-122-4/+35
| | | | | Exception: allow run-interactive to continue even if it encounters errors in parsing its ingredient as mu code.
* 2185Kartik K. Agaram2015-09-121-0/+1
|
* 2184 - bugfix in trace_countKartik K. Agaram2015-09-122-3/+12
| | | | | | | | | | | | | | | | It was reading lines like this in scenarios: -warn: f: error error as: -warn: f which was causing them to be silently ignored. Also found an insane preprocessor expansion from not parenthesizing preprocessor arguments. SIZE(end+delim) worked even when end was an integer, but it happily didn't ever get the wrong answer.
* 2183 - environment + external editor using tmuxKartik K. Agaram2015-09-1220-19/+8346
| | | | Thanks Jack and Caleb Couch for the idea.
* 2182Kartik K. Agaram2015-09-122-3/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-24 13:49:00 +0000