173 posts
Location
The hall of 1000 monkeys and only 1 typewriter
Posted 19 February 2016 - 12:26 PM
what is this? what does it actually mean?
yes that literally is my question… I did look! Just didn't find an adequet answer (is that how you spell adequet?)
12 posts
Posted 19 February 2016 - 04:44 PM
In terms of Lua's "though process" It's less to do with variables starting with numbers, and more do do with numbers with invalid symbols.
for example 4e34 and 0x3f are both valid numbers in Lua.
For input string: "something" just means you've written a number Lua can't make sense of.
173 posts
Location
The hall of 1000 monkeys and only 1 typewriter
Posted 22 February 2016 - 05:54 PM
ok thx, so it's just that lua doesn't like variables with numbers infront. I now realise my mistake of havign a variable called 1stcharpos. i shall change that
1080 posts
Location
In the Matrix
Posted 22 February 2016 - 06:34 PM
It's not just Lua, it's any language. Java, C, C++, C#. All of those languages, and more that I've not had the pleasure of using, do not allow a number to lead a variable name. They also don't allow most symbols, with _ at least being accepted.
local VarName
--#Valid
local 1VarName
--#Invalid
local VarName1
--#Valid
Edit: Heck the forums code tool recognized that it's invalid
Edited on 22 February 2016 - 05:34 PM
3057 posts
Location
United States of America
Posted 22 February 2016 - 07:19 PM
Edit: Heck the forums code tool recognized that it's invalid
Actually, it's trying to represent it as a number.
local 1VarName
local i = 1
local varname = 1VarName
Edited on 22 February 2016 - 06:19 PM
1080 posts
Location
In the Matrix
Posted 22 February 2016 - 10:32 PM
Actually, it's trying to represent it as a number.
Well yes, but that's also how the compiler/interpreter views it.
173 posts
Location
The hall of 1000 monkeys and only 1 typewriter
Posted 24 February 2016 - 06:31 PM
lol k got it! :)/> Thank you very much