A most recent snap-shot
What do you want say?
I just want to show what am I doing. I haven't said any other one's design was bad. Your design was interesting, and worth a good study so as the Nan's. I thought we should have a talk in chinese, Maybe the language prevented me from saying the true idea.
I just want to show what am I doing. I haven't said any other one's design was bad. Your design was interesting, and worth a good study so as the Nan's. I thought we should have a talk in chinese, Maybe the language prevented me from saying the true idea.
My work is not only worth for studying but also valuable for practice. In fact, I've written a lot of code base on my TOM and they work nice.
OOP is not the main approach in asm world, only very few asm fans/gurus are interesting in it.
Speaking for the older generation of coders if I may, I'd have to say that there's quite a lot of interest in high level asm - we want to see asm grow and develop, but we don't want to lose our grip on the cpu !!
Some of us might deride languages based on text based sources with lots of high level directives and wrappers for this and that, but how different are they really from something like MASM? When you think about it, you will probably agree that there's a LOT of masm coders who would rather use .IF/.ELSE/.ENDIF than CMP and JZ.
Speaking just for myself, I personally spend much effort wrapping my code in procedures and macros in order to save time on my NEXT project(s) by avoiding reinventing the wheel, or chasing my own tail.
Some of us might deride languages based on text based sources with lots of high level directives and wrappers for this and that, but how different are they really from something like MASM? When you think about it, you will probably agree that there's a LOT of masm coders who would rather use .IF/.ELSE/.ENDIF than CMP and JZ.
Speaking just for myself, I personally spend much effort wrapping my code in procedures and macros in order to save time on my NEXT project(s) by avoiding reinventing the wheel, or chasing my own tail.
Since I posted that last comment, I have become even more strongly attached to object-oriented assembly language.
Sticking our common code in relevant OBJ files is the next logical step and I can not see other alternatives anymore.
Sticking our common code in relevant OBJ files is the next logical step and I can not see other alternatives anymore.