I don't think it's necessary though because the GBA/NDS doesn't work like a ticalc.  Everything is done in a synchronized fashion as opposed to the code procedurally moving down a list of instructions.

If you had functions, they'd be too general to run efficiently in your game, and they'd eat up time because they have to sync w/ the code.  PAlib on the NDS is a nice place to start.  But for the most part, it's better in the long run to learn C concepts and code.  It's almost entirely data manipulation really.  You just use C/ASM to set bits/bytes and write data to certain memory locations/registers to change mode and what's being used as variables and stuff.

xlibman: it's really not that hard imho.  I think if you put your mind to it, you'll get it.  I think the hard part is finding standard memory equates, because a lot of people just look up memory locations in the no$gba emu and write their own equates.

basically:

0xFFFFFFFF is some memory location
so in the library/include file
#define mem1 0xFFFFFFFF

that means anywhere you use "mem1", the compiler replaces with 0xFFFFFFFF, which is really a #, and you don't have to remember the # when you need it.

having a standard allows everyone programming for the platform to know what#/thing/memory location your talking about when you use something like "VMEM" or other kinds of equates.

i see, i was thinking about trying to learn asm again someday but I may need ppl help for it, especially getting to understand the basic concepts, i just wish i could concentrate easier, not easy with all other stuff happening

Maybe reuben will make its way to commercial stores  >;B