Sign in to follow this  
Followers 0
pekster

ASCII verses Unicode

1 post in this topic

#1 ·  Posted (edited)

If you run the included example AutoIt code below, you can see that the @CRLF macro is 1 byte per character, and the equivilent using the Asc function is 2 bytes per character. Why are we combining strict ASCII and unicode characters in these results? Shouldn't they be equivalent commands? If not, you could run into some very odd problems by assuming the output from these commands will be in the same format. This could be rather dangerous for some filetypes.

Code illustrating the problem:

<code removed>

Okay, I was stupid and mixed up my Chr and Asc commands :ph34r:

It is all strict ASCII. Sorry for the bother.

Edited by pekster

[font="Optima"]"Standing in the rain, twisted and insane, we are holding onto nothing.Feeling every breath, holding no regrets, we're still looking out for something."[/font]Note: my projects are off-line until I can spend more time to make them compatable with syntax changes.

Share this post


Link to post
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0