Nice to see a new update out!

However, I do not understand most of the new features are about. Someone will really need to make a screenshot showing them in actions with the results and show some source code or something, cuz it is getting beyond my learning capacities (too low level)

mhmm ok, I understand this one now. However, I think you migth want to specify this into more details in the doc because I alerady saw this:

int(EXP)   Returns a sign extention for the expression. Converts a signed byte in the range -128 to 127 into a 16 bit number in the same range.

And it was really cryptic. I totally couldn,t understand what you meant by that. "Returns a sign" to me sounds like it returns 1 if the sign is negative and 0 if it isn't, and stuff like that.

And I cannot understand this at all either:

Fill(PTR1,SIZE)   Whatever byte is already at the location Ptr1 is copied to Size more consecutive bytes. Zero is not a valid Size.
conj(PTR1,PTR2,SIZE)   Size bytes starting from the location Ptr1 are copied to the location at Ptr2. Zero is not a valid Size.
expr(PTR1,PTR2,SIZE)   Size bytes starting from the location Ptr1 are exchanged with the bytes starting at the location Ptr2. Zero is not a valid Size.

Plus another thing I don't get: what is Size for? I know Ptr seems to involve pointers, but I just don't get it... all I get is that conj is for Copy and expr is for exchange, since it's in the new features list

And what are Hexadecimal constants and ASCII constants for? And what are they at all? I ran a CTRL+F in the command list, and both these things returned no results. To me it seems like it's more the documentation that is getting more and more in the style of low level programmers (explained in a way that can only be understood by tech savy people, specifically low-level language programmers). You did a very good job at writing the command list so far, though. I could understand a lot of stuff and thank you for explaining all this stuff and even the tutorials and examples. It,s just that I just can't understand any of this and it is starting to discourage me, as I though Axe was meant to remain a language easy to understand . If even after you explain in more details I don't get it, I hope you promise these commands will not be essential in future Axe versions to have decently optimized Axe games, right? Else I am starting to fear I might have to give up on the whole language or team up with someone else for optimizing. Sorry

I'll give some examples of these commands in use. For example, instead of doing this to fill the 6 bytes at L1 with zeros:
:For(X,0,5
:0->{L1+X
:EndYou can do this:
0->{L1}
Fill(L1,6
The conj( command is just used to copy a number of bytes from one location to another, like if you want to copy 10 bytes from L1 to L2. Here is the old way:
:For(X,0,9
:{L1+X}->{L2+X
:EndAnd here is the new way:
:conj(L1,L2,10
expr( does a similar thing, but it exchanges, or swaps, the data at the two locations.

Mhmm ok, because the way it is explained in the doc seems like something totally different. I think it may be best to clarify in the doc that fill does the same thing as the BASIC command, but for pointers instead of lists. Also if I read Builderboy way, I still doN,t get it. To me it seems like he's saying Fill just copy one list element to the next one, not fill the entire list with an element.

About Conj, what if we want to do For(X,9,12:{L1+X}->{L2+X:End?

Also are lists defined the same way as other stuff? Like at the beginning of a program I just do {2,34,5,23,0->L1?

For that example, you would want conj(L1+9,L2+9,4

And remember that L1-L6 are just areas of RAM. So, you will need to initialize data just like for a sprite (you will have to convert the values to hex), and store to a String or Pic or something. Then, you should copy your String/Pic to one of the defined RAM areas. (I suppose technically, you could modify the data while it's in the program, but that only works correctly for no-stub)

Edit: Example code
:[0222051700->Pic1
:conj(Pic1,L1,5
Edit2:
Also, remember that Quigibo is planning for real array support later. So it should get easier.

Or better yet, ask Quigibo to implement a traditional looking List format for axe source

Sorry about the doc.  You're right, I didn't have time. I added the documentation the last minute because I was on my laptop in the library and I realized my battery was running low so I scrambled to put it together as fast as I could.  Still don't have internet yet, probably won't for a while, but I don't mind since I'm trying not to be too distracted from my school work and I'm at school almost every day anyway so I just use it there.  I'll try to make it more clear in the next version.

Also you mentioned that you didn't see the hex and ascii constants?  Those are just alternative ways to write numbers.  Its in the middle of the doc somewhere.

Instead of 11->A it is sometimes more convenient to write E000B->A as hexadecimal, especially when you want to access certain locations in the RAM since they are defined in hex, not base 10.  Its a pretty low lew command though, you generally won't need it, but it was requested so I figured I might as well since at the same time I was doing ASCII constants.

You might be familiar with ASCII already, but each character is represented by a number.  So if you need to display a single character, than instead of Disp "A" you can do Disp 'A'>Frac which saves some bytes.  But you'll most often use this when reading from a string and comparing the characters to another character.  Also, this makes it easy to store data using strings instead of hex since they are easier to read.  Entire maps can be made with a string since you can make statements now like If {Str1+X}='A'

Just search for "ASCII" and you should find it, I think

'CHAR' is new.  So is EHEX.