diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-01-27 17:12:12 -0800 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-01-27 17:12:12 -0800 |
| commit | 50689bff2ed59814a67e74e90a33717552d69df0 (patch) | |
| tree | b241a7981c0e1bb5780e0e63832e45b7057c447a /sandbox/008-sandbox-test.mu | |
| parent | 95425355a01edf284a86d0873e63d88071221ed8 (diff) | |
| download | mu-50689bff2ed59814a67e74e90a33717552d69df0.tar.gz | |
2609 - reuse test-recipe variables in sandbox/ tests
I'd feared that the refcount errors in the previous commit meant there was a bug in my ref-counting, so I temporarily used new variables rather than reusing existing ones. But it turns out the one remaining place memory corruption can happen is when recipes don't use default-scope and so end up sharing memory. Don't I have a warning for this?
Diffstat (limited to 'sandbox/008-sandbox-test.mu')
| -rw-r--r-- | sandbox/008-sandbox-test.mu | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sandbox/008-sandbox-test.mu b/sandbox/008-sandbox-test.mu index a7344ba4..d08bb890 100644 --- a/sandbox/008-sandbox-test.mu +++ b/sandbox/008-sandbox-test.mu @@ -58,7 +58,7 @@ recipe foo [ . . ] # now change the result - 5:address:shared:array:character <- new [ + 1:address:shared:array:character <- new [ recipe foo [ reply 3 ]] @@ -67,7 +67,7 @@ recipe foo [ press F4 ] run [ - event-loop screen:address:shared:screen, console:address:shared:console, 3:address:shared:programming-environment-data, 5:address:shared:array:character/new-test-recipes + event-loop screen:address:shared:screen, console:address:shared:console, 3:address:shared:programming-environment-data, 1:address:shared:array:character/new-test-recipes ] # result turns red screen-should-contain-in-color 1/red, [ |