| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 2232 | Kartik K. Agaram | 2015-10-01 | 16 | -129/+435 |
| | | |||||
| * | 2231 | Kartik K. Agaram | 2015-10-01 | 1 | -0/+1 |
| | | |||||
| * | 2230 | Kartik K. Agaram | 2015-10-01 | 1 | -11/+17 |
| | | |||||
| * | 2229 | Kartik K. Agaram | 2015-10-01 | 1 | -0/+6 |
| | | |||||
| * | 2228 - index-checking for arrays | Kartik K. Agaram | 2015-10-01 | 1 | -23/+47 |
| | | |||||
| * | 2227 - offset-checking for containers | Kartik K. Agaram | 2015-10-01 | 4 | -42/+88 |
| | | |||||
| * | 2226 - standardize warning format | Kartik K. Agaram | 2015-10-01 | 33 | -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? | ||||
| * | 2225 | Kartik K. Agaram | 2015-10-01 | 4 | -63/+91 |
| | | |||||
| * | 2224 | Kartik K. Agaram | 2015-09-30 | 1 | -3/+3 |
| | | |||||
| * | 2223 | Kartik K. Agaram | 2015-09-30 | 2 | -20/+32 |
| | | |||||
| * | 2222 | Kartik K. Agaram | 2015-09-30 | 3 | -14/+14 |
| | | |||||
| * | 2221 | Kartik K. Agaram | 2015-09-30 | 4 | -19/+46 |
| | | |||||
| * | 2220 | Kartik K. Agaram | 2015-09-30 | 3 | -34/+121 |
| | | |||||
| * | 2219 | Kartik K. Agaram | 2015-09-30 | 1 | -12/+4 |
| | | |||||
| * | 2218 - check types in instructions much earlier | Kartik K. Agaram | 2015-09-30 | 13 | -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. | ||||
| * | 2217 | Kartik K. Agaram | 2015-09-29 | 2 | -0/+0 |
| | | |||||
| * | 2216 | Kartik K. Agaram | 2015-09-29 | 2 | -1/+13 |
| | | |||||
| * | 2215 | Kartik K. Agaram | 2015-09-29 | 1 | -1/+1 |
| | | |||||
| * | 2214 | Kartik K. Agaram | 2015-09-28 | 8 | -33/+39 |
| | | |||||
| * | 2213 - start moving type checks out of 'run' | Kartik K. Agaram | 2015-09-28 | 4 | -43/+88 |
| | | | | | | That way we only have to check each static instruction once, rather than every time it runs. | ||||
| * | 2212 | Kartik K. Agaram | 2015-09-28 | 1 | -6/+6 |
| | | |||||
| * | 2211 | Kartik K. Agaram | 2015-09-28 | 1 | -0/+0 |
| | | |||||
| * | 2209 | Kartik K. Agaram | 2015-09-26 | 1 | -4/+4 |
| | | |||||
| * | 2208 | Kartik K. Agaram | 2015-09-26 | 1 | -0/+5 |
| | | |||||
| * | 2207 | Kartik K. Agaram | 2015-09-26 | 1 | -1/+1 |
| | | |||||
| * | 2206 - fix missing ingredients | Kartik K. Agaram | 2015-09-26 | 3 | -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 ingredient | Kartik K. Agaram | 2015-09-18 | 2 | -1/+13 |
| | | | | | ..unless you explicitly ignore the found? result. | ||||
| * | 2204 | Kartik K. Agaram | 2015-09-16 | 1 | -2/+8 |
| | | |||||
| * | 2203 - show recipe warnings in 'mu sandbox' | Kartik K. Agaram | 2015-09-15 | 2 | -9/+8 |
| | | |||||
| * | 2202 - don't let editor die on syntax errors | Kartik K. Agaram | 2015-09-15 | 3 | -35/+50 |
| | | | | | | Bugfix to 2186. I hadn't taken care of 'reload' as cleanly as I had 'run-interactive'. | ||||
| * | 2201 | Kartik K. Agaram | 2015-09-15 | 1 | -2/+4 |
| | | |||||
| * | 2200 | Kartik K. Agaram | 2015-09-15 | 2 | -10/+14 |
| | | |||||
| * | 2199 - stop printing numbers in scientific notation | Kartik K. Agaram | 2015-09-14 | 13 | -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. | ||||
| * | 2197 | Kartik K. Agaram | 2015-09-14 | 1 | -1/+1 |
| | | |||||
| * | 2196 | Kartik K. Agaram | 2015-09-14 | 2 | -3/+1 |
| | | |||||
| * | 2195 | Kartik K. Agaram | 2015-09-14 | 1 | -2/+2 |
| | | |||||
| * | 2194 | Kartik K. Agaram | 2015-09-14 | 1 | -2/+2 |
| | | |||||
| * | 2193 | Kartik K. Agaram | 2015-09-14 | 1 | -2/+2 |
| | | |||||
| * | 2192 | Kartik K. Agaram | 2015-09-14 | 1 | -0/+1 |
| | | |||||
| * | 2191 | Kartik K. Agaram | 2015-09-13 | 1 | -28/+26 |
| | | |||||
| * | 2190 | Kartik K. Agaram | 2015-09-12 | 1 | -2/+3 |
| | | |||||
| * | 2189 | Kartik K. Agaram | 2015-09-12 | 1 | -1/+1 |
| | | |||||
| * | 2188 | Kartik K. Agaram | 2015-09-12 | 1 | -2/+2 |
| | | |||||
| * | 2187 | Kartik K. Agaram | 2015-09-12 | 2 | -1/+5 |
| | | |||||
| * | 2186 - kill the current routine on first error | Kartik K. Agaram | 2015-09-12 | 2 | -4/+35 |
| | | | | | | Exception: allow run-interactive to continue even if it encounters errors in parsing its ingredient as mu code. | ||||
| * | 2185 | Kartik K. Agaram | 2015-09-12 | 1 | -0/+1 |
| | | |||||
| * | 2184 - bugfix in trace_count | Kartik K. Agaram | 2015-09-12 | 2 | -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 tmux | Kartik K. Agaram | 2015-09-12 | 20 | -19/+8346 |
| | | | | | Thanks Jack and Caleb Couch for the idea. | ||||
| * | 2182 | Kartik K. Agaram | 2015-09-12 | 2 | -3/+1 |
| | | |||||
| * | 2181 - detect shift-tab | Kartik K. Agaram | 2015-09-11 | 2 | -5/+10 |
| | | | | | Does nothing useful yet, though. | ||||