Hm interesting behaviour. See if it does work using a STRING instead of a char. If so, I'd say it's because int and char datatypes are, someway or another, treated or recognised the same way in lite-c.