summaryrefslogtreecommitdiff
path: root/docs/dev
diff options
context:
space:
mode:
authorJordan Wiens <jordan@psifertex.com>2024-03-20 19:48:24 -0400
committerJordan Wiens <jordan@psifertex.com>2024-03-20 19:48:24 -0400
commit637084ff9d8b386810d61f3c082a8897e4275436 (patch)
tree7503069a81388cb54f071c83950ba6ef4700090e /docs/dev
parent31c8eb2c5a298797422b467d060d575af0ca77d1 (diff)
add examples of wide string rendering to working with strings docs
Diffstat (limited to 'docs/dev')
-rw-r--r--docs/dev/concepts.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/dev/concepts.md b/docs/dev/concepts.md
index 85e81da4..788caf81 100644
--- a/docs/dev/concepts.md
+++ b/docs/dev/concepts.md
@@ -189,6 +189,11 @@ Many Windows applications use wide (UTF-16 or UTF-32) strings. By default these
However, you can always change a variable to a `wchar_t` with `[SHIFT] a` and to a `wchar32_t` with `[CTRL-SHIFT] a` in the UI.
+Wide strings will be rendered in the UI as:
+
+ - `u"String"`: 16-bit wide string
+ - `U"String"`: 32-bit wide string
+
### "Strings" versus Strings
The strings view in Binary Ninja are based on all identified strings found in a manner similar to the command-line "strings" tool (with `-a` if you're using a GPL Binutils version). However, this is not the same as a string having a string type in Binary Ninja!