diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-10-06 22:15:45 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-10-06 22:15:45 -0700 |
| commit | 5f98a10cc78829a03c9fa5a137392e7d5e9030ac (patch) | |
| tree | b88536e28f6d507c4b68b337423c0b6a4e28306c /075scenario_console.cc | |
| parent | 75aa3a98e2b9311d65df91523ec754d5a2770456 (diff) | |
| download | mu-5f98a10cc78829a03c9fa5a137392e7d5e9030ac.tar.gz | |
2258 - separate warnings from errors
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.
Diffstat (limited to '075scenario_console.cc')
| -rw-r--r-- | 075scenario_console.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/075scenario_console.cc b/075scenario_console.cc index 44bed831..ab6aba94 100644 --- a/075scenario_console.cc +++ b/075scenario_console.cc @@ -74,7 +74,7 @@ case ASSUME_CONSOLE: { else if (Key.find(key) != Key.end()) Memory[Current_routine->alloc+1] = Key[key]; else - raise << "assume-console: can't press " << key << '\n' << end(); + raise_error << "assume-console: can't press " << key << '\n' << end(); if (Memory[Current_routine->alloc+1] < 256) // these keys are in ascii Memory[Current_routine->alloc] = /*tag for 'text' variant of 'event' exclusive-container*/0; @@ -235,7 +235,7 @@ case REPLACE_IN_CONSOLE: { case REPLACE_IN_CONSOLE: { assert(scalar(ingredients.at(0))); if (!Memory[CONSOLE]) { - raise << "console not initialized\n" << end(); + raise_error << "console not initialized\n" << end(); break; } long long int console_data = Memory[Memory[CONSOLE]+1]; |