| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our new heuristic is: all string literals are the same. If they contain
newline before non-whitespace, we scan for comments assuming there might
be code inside:
foofoofoo [
... # ']' inside comment ignored
]
If they contain non-whitespace first, then we ignore comments assuming
it's just a regular string:
foofoofoo [abc#def] # valid string literal
The big hole in this approach:
foofoofoo [ # what about comments here containing ']'?
... # abc
]
Currently this reads as a 'code comment' and terminates before the
newline or '?' and will probably trigger errors down the line.
Temporary workaround: don't start code strings with a comment on the
same line as the '['. Eventually we'll tighten up the logic.
We're still not using the new heuristic in scenarios, but that's up
next.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Make it possible to check multi-line string literals in the trace.
|
| |
|
|
| |
More concise traces for literal strings.
|
| | |
|
| |
|
|
| |
We also do this in regular C++ now.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Two columns: edit code on left and run code on right.
In both columns, the action is at the top of the screen, and stuff
gradually flows downward unless pulled back up.
Stuff you run on the right side will eventually become reproducible test
cases that runs constantly on every change.
We also have a tentative signature for the 'edit' routine: it'll take an
input string and return an output string when it finishes.
More columns expand to the right. Number of columns shown will remain
fixed at any time depending on screen width. But for now we support
exactly two columns.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Yet another repl bugfix.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I'd hoped finding that off-by-one error would fix the other intermittent
issues I've been seeing (commit 1512), but no they're still there.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Variable 'instruction_counter' was obfuscating more than it clarified.
|
| |
|
|
|
|
|
|
| |
Extracting a function for the prompt before starting to test it.
Still not clear how I should proceed. Need to express screen dependency
to 'run-interactive' somehow. Supporting generics might finally be on
the critical path.
|
| | |
|
| |
|
|
|
| |
But we really should test the top-level integration with
'run-interactive'.
|
| |
|
|
| |
Was missing a newline. More brittleness.
|
| |
|
|
|
|
| |
Just figured out why a first keystroke of backspace was sending me out
for a spin: run_interactive needs all early exits that don't actually
run anything to increment the current_step_index(). FML, this is lousy..
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
In the process we now support unicode in all mu strings!
|
| |
|
|
|
|
|
|
| |
I'm still having trouble with prematurely closed strings or strings
never being closed. Remember that when escaping brackets inside
scenarios you usually need two levels of escaping. The single-level is
a no-op and usually misleading. When brackets balance, don't bother
escaping. When they don't, escape twice.
|