Octavio - you don't preserve the original value of ebp

varargs are ugly, passing an [array] [size] [static args] is the cleanest implementation but it also has a high overhead.


vid - you have to count the arguments anyways if your using some sort of format string you need to make sure it matches up with the number of args you push. But there's no reason not to use your idea for yoru implementation. Although a macro would be just as simple and still arguably pure asm ~ish.

r22: and don't forget i also support MASM, NASM and YASM, maybe more in future. nice !pure assembly usage! is my goal

Isn't something like this best done at compile time via macros? I believe all the assemblers mentioned have capable macro processors.

Kain: i don't want to force users to use macros, which they may be unfamiliar with. I am doing library for assembly language, not for assembly language customized with macros. It's matter of opinion.

i realized that in this specific case (printf-like), i don't need return value, so i can trash return value in EAX. So epiloque code simplified to something like this:



problem is just in case of error, in the middle of function, when you don't already know number if arguments. you have to find all non-escaped "%" in format string and skip appropriate number of dwords... but what wouldn't i do for FASMLIB users.


EDIT: realized this works only in case without error. when error is returned, EAX is used

also, it's pretty hard to return in some error case, i am doing my best, but if you mess up format string too much, then it's same as calling function with wrong number of arguments - unbalanced stack.