It was only meant to do one simple thing. There is no need to make it do more. It's something simple with a decent interface that you get the answer you're looking for and be done with it.

Whoopee, I'm getting close. Never read into this before. Thanks vid...

Would anyone know what is to be used that is equivalent to dwtoa or is there a dwtoa procedure around here somewhere. I did a search and only turned up one that had problems with neg-numbers and something somewhere else lead me here.

http://board.flatassembler.net/topic.php?t=1835

yup, there are "conv." functions ready just for you

I been reading your thread and Wow... That took some Great efforts and some wonderful team work. I can see daylight now. I can even understand how macros and a whole lot more works after reading that. It seems to help to put an end to my 1000's question list. I missed a lot while searching... the best of it all was on the first pages all along.

Thanks vid
and Team

Even thought I do not use standard libraries (even in C ), I must admit the code is inspiring

thanks grey beast, valued double from you.

vid:
is there any way to use fasmlib in my OOP way?

it would be interresting just to ry an unification.

i never use syscall or stack frames...

I think that at least following FASMLIB procedure design guidelines would be good - argument passing and returning. Always returning error status in CF makes it easier to automatically test return values, unless you want real SEH.

Also, for OOP you *need* some memory allocation, and FASMLIB provides Asm-friendly way for portable (win32, linux) memory allocation.