aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenoit Giannangeli <giann008@gmail.com>2017-07-28 12:18:05 +0200
committerBenoit Giannangeli <giann008@gmail.com>2017-07-28 12:18:05 +0200
commit99223779c613f7c612d69bb9184164d8270b1a74 (patch)
treeddd13f94e9fd24bd17e8a51e81a7bd4edaf77718
parentf0db46947268e5ceacd1558cf74781fff0e782d1 (diff)
downloadfengari-99223779c613f7c612d69bb9184164d8270b1a74.tar.gz
fengari-99223779c613f7c612d69bb9184164d8270b1a74.tar.bz2
fengari-99223779c613f7c612d69bb9184164d8270b1a74.zip
README: added sentence about lua.to_luastring/lua.to_jsstring
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 30c02dd..7cb3ef6 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ Fengari implements Lua 5.3 semantics and will hopefully follow future Lua releas
Lua strings are 8-bits clean and can embed `\0`. Which means that invalid UTF-8/16 strings are valid Lua strings. Lua functions like `string.dump` even use strings as a way of storing binary data.
-To address that issue, Lua strings are represented by an array of bytes in Fengari. To push a JS string on the stack you can use `lua_pushliteral` which will convert it to an array of bytes before pushing it. To get a Lua string on the stack as a JS string you can use `lua_tojsstring` which will attempt to convert it to a UTF-16 JS string. The latter won't give you what you expect if the Lua string is not a valid UTF-16 sequence.
+To address that issue, Lua strings are represented by an array of bytes in Fengari. To push a JS string on the stack you can use `lua_pushliteral` which will convert it to an array of bytes before pushing it. To get a Lua string on the stack as a JS string you can use `lua_tojsstring` which will attempt to convert it to a UTF-16 JS string. The latter won't give you what you expect if the Lua string is not a valid UTF-16 sequence. You can also convert strings with `lua.to_luastring` and `lua.to_jsstring`.
### _Missing_ features