It's funny when people mistake questions about AngelScript syntax for questions about C++. [wink] (As a moderator I can see deleted posts.)

Single character literals are not implemented in the AngelScript syntax yet. I haven't decided if I will do so either.

Currently I suggest that you expose a function like 'uint8 ascii(string∈)' that returns the ascii code for the first character in the string, or use numeric constants.

I'm sorry about the confusion, I should have explained better. Just before my answer to your question someone else answered. That person mistook your question for being about C++, and answered it as such. However, he (or she) realized his own mistake and deleted the post before anyone could see it, except for those of us who are moderators. [wink]

Character literals wouldn't be difficult to implement, I just can't decide wether I want them or not. I've come to know that in C/C++ character literals are really interpreted by the preprocessor, so the underlying compiler really don't understand them. AngelScript could support them in the same way, and in fact, with Deyja's preprocessor it already does.

Indeed it does. I ran across this same problem some time back, and asked WL about it. After a bit of research, I discovered that in C++ the preprocessor handles it, so I added it to mine. It does it in the simplest way imaginable. When it detects a ' character, it assumes the next character is the one to encode, and the one after it is another '. It does absolutly no error checking, and if you do something like 'lotsofcharacters' you will get some rather hard to decode error in angelscript. It does support escapes, but only newline, carriage return, and tab.