I think rather unlikely, i certainly found the structure pretty obvious... the only 'unknown' was the types and encoding scheme... (most programmers these days have a pretty good understanding of things like xml/json etc)
really, the #1 suggestion is simple ... go look at some objects that you already know what they do, what parameters/inlet/outlets they take, then go look at the axo file.... then go look at a few more.
you will soon start to recognise the types etc... and after a while see how they get encoded/decoded.
but frankly, thats the pretty obvious way to understand any new system, and this stuff is not rocket science
Funny, thats the area I think many coders might have a lot to learn... also the difference between coding on a 'computer' vs micro-controller. but, as you say there are plenty of books out there on this.
the one thing i didn't recognise initially were the ARM instructions, SMUL etc, but if you google those the info is pretty good.
I agree with you on that, just saying the direction @johannes was going.
(its also good for looking at existing objects, as its quicker than finding the axo file in the filesystem )
however, now doing the push stuff, I've noticed actually i wouldn't mind, since all i do in the axo file is call a function, Im not writing any code in the axo file itself, all the code is in a C file ( i guess i might if i was writing trivial objects)
it may also be worth pointing out, don't edit the 'factory' axo files... even if you want to contribute code changes. the reason is, they are generated from java, so the changes need to be made there.