No, you only have 8 bits numbers in each location.  Using int() just allows those numbers to be between -128 and 127 instead of 0 to 255.  Anything outside those ranges will give inaccurate numbers.  More technically, it will instead be the number modulo 256, but I doubt you will ever need to exploit this detail.

Yes, I'm happy to finally see program naming ^^ no more need to abuse the MirageOS 1.1 ungroup glitch (see calc news and discussion)!

I think people probably just ask if it's gonna be in Axe because of what it can do alerady at the moment, and until this post, they probably were not aware that everything would change so much in later versions, especially that we got told a few times before that the changes in the syntax would be minor in overall. Most projects are also quite small, so they won't be that hard to modify for newer Axe versions (unless the entire format in which sprite data is stored will change). People probably just didn,t want to wait and probably either don't mind changes in future versions or were not aware they would be that drastic. Plus, projects that will be almost completly done before Axe is finished can be released, since they are compiled and doesn,t require the latest axe version to run, once compiled. I don't think it's funny that ppl asks if it's gonna be made with Axe. The language may not be finished but it can alerady do entire games, so that's an expected reaction you would not get with much other languages.

Yeah Idk, just making sure that not too many ppl take it the wrong way. Maybe it could make some projects authors feel badmouthed and less motivated from working on their projects

I definitively think it gets so much attention because it is what z80 BASIC programmers have been looking for years and like BBC Basic, your project was done the right way. Believe me, I've been browsing calc sites for years and saw so many alternatives to BASIC and ASM before. Regardless of what language it was (C, Java, hybrid, RPL or totally new ones like MLC), either their authors were too ambitious or the line at which they find something easy to learn was way too high (causing the new language to not even be easy to learn as it was advertised). The big plus is that within the first month you came out with a set of commands that allows people to make entire games. I mean, look at many of the sample programs released by members: all they need to add is title screens and the game is finished. Of course, in later versions people who are patient will be able to do even more, though, but what I mean is that your project may be at version 0.1.x, but it's alerady amazing now. I can,t wait for what new features it will have in next versions, though.

Glad to hear the changes will not be that huge, too.

New update!  I can't believe I added so much, I guess most of it was simple.  Anyway, you can name your programs now and I think the most useful added feature is the double byte reading and writing.  So if you have a number larger than 255 you want to store, like a score for instance, you can store it to memory using S->{L1}^r.  That means it writes the first part of the number to {L1} and the second part of the number to {L1+1} so the entire 2 byte number is saved.  Same goes for reading, you can read the entire byte.  Be careful though, because when you have arrays and things make sure you step by 2 instead of 1 since each number takes up 2 bytes.

Also, I reworded almost the entire commands list to make it less technical.  If you have a specific low level question about a command I can answer it here because I intentionally left out a lot of those details to make it as simple a definition as possible for those used to higher level languages.

Yes it will.  It won't cause any crashes, and the calc will fix itself eventually once it needs to change the flags again, but its not a desirable effect.

Epic update. I'll definitely be trying some new programs out once I get back from work.