From: riwu
But how did an Unicode character end up in my script? All i did was:
1. Upload a (successfully compiled) script to googlecode
2. Wanted to double check nothing went wrong with the upload so i went to googlecode and use the edit so that i can just select all and copy paste the script to simba.
3. I tried to compile it which was how i discovered the dot (which caused compiling error)
4. I went back to googlecode and checked the line, but there is no dot on the line (apparently the dot is seen as just a blank space in web browsers), but when i copied and pasted the whole line to simba the dot appeared.
5. But if i were to copy and paste the line on googlecode without using the EDIT feature there will not be any dot!
Is it an intentionally/accidentally imposed dot on the EDIT version due to some coding errors/limitations on googlecode's part? That dot is recognized as blank space on notepad/microsoft word too, only simba managed to detect it as unicode.
The reason why other editors leaves it as a blank space is because it is a blank space in UTF-32 Editors. Anything else is going to show it as a weird character. Github sometimes does this too (For code edited in DevC++) Whereas if edited in codeblocks, it will replace it with a space or a tab.
It's the minor differences that screw us over. Think of it like this: I draw out the blue prints for a rocket and I measured everything in Inches because I like the British Standard. Mind you I did not write the standard measurement beside it. Instead I wrote 32 with no Measurement syntax at the end.
You on the other hand got these same blue prints through the mail but since you live in Iunno, the US, you assume it to be Metric instead of Imperial. You build the rocket and everything seems fine, you launch and everyone is dead and you wanna know why.
Well it's because we both had different standards and it's my fault for not putting the Standard declaration at the end; such as: 32" would signify 32 inches/imperial whereas 32mm or cm would signify metric standard.
Unicode works the same way except it's usually signified by a range of characters such as 1 - 256 vs. 1 - 110k. Sometimes even UTF-8/16/32 will signify it's support. Code editors have the job of deciphering what format your code is and you as a programmer should support portable code by using a standard format.
ANSI is old so it can be used on very old machines whereas Unicode can be used on anything Win98+ but at the same time ANSI supports less characters than Unicode of a specific Bit type.
BTW, my little rocket example happened in real life. ~ NASA ~ -__-. Also screwed me over once! when I did Mech Engineering.
TLDR: Simba needs to update it's code editor OR change all string types to wchars and wstr/wstrings.