From 0a8f99583281ec086be923eb7906014d91c79754 Mon Sep 17 00:00:00 2001 From: Michael Specht Date: Fri, 16 Feb 2018 16:10:23 +0100 Subject: [PATCH] documentation --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dd6e510..f4ef712 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ By default, all champ values get recorded before the operation has been executed ### Global variables -In addition to watching individual registers, you can also watch global variables (([example02.yaml](example02.yaml) / [example02.s](example02.s))): +In addition to watching individual registers, you can also watch global variables ([example02.yaml](example02.yaml) / [example02.s](example02.s)): ``` DSK test @@ -103,7 +103,7 @@ TEST LDA #0 RTS ``` -Here, we declare the type of the global variable in the same place the variable itself is declared, using @u8@, @s8@, @u16@, or @s16@. Later, we can just watch the variable by issuing a champ directive like `@FOO@`. In this example, we use the `(post)` option to see the variable contents after the `STA` operation. +Here, we declare the type of the global variable in the same place the variable itself is declared, using `u8`, `s8`, `u16`, or `s16`. Later, we can just watch the variable by issuing a champ directive like `@FOO@`. In this example, we use the `(post)` option to see the variable contents after the `STA` operation. ![FOO at PC 0x600b](doc/example02_1.gif?raw=true)