Hello, every one, I'm glad to see here are some TASM gurus, so I decide to share my TASM Object model here. I've post following two messages in Borland TASM newsgroup, but no one reply.

I'm glad to share my TASM Object Model.
This is a practical object model for TASM OOP. It supports RTTI, interface,
dynamic method and other interesting feature. Now OOP becomes more useful
and valuable in TASM under this model. It's always under constructor. I will
feel glad if it's useful for you.
I'd like to accept advice and bug reports on it.

You can download it from my homepage,
http://www.mujweb.cz/www/komsbomb/dev/tom/tom.htm


VTable macros are here http://www.mujweb.cz/www/komsbomb/dev/tom/vtable.zip
They can build VTable, just like what 'TABLE' directive in TASM does.
By using them, now it's possible to write true OOP code in other assemblers
that don't support 'TABLE' like MASM, NASM, etc.
They are not well test.


These code is really free, you can use them as your willing and you MUST following GPL license.
Posted on 2003-05-06 21:06:56 by KomsBomb
I am working on a OOP model in MASM. Maybe we can have a talk about it. Do you have a QQ?
Posted on 2003-05-07 10:25:25 by taowen2002

I am working on a OOP model in MASM. Maybe we can have a talk about it. Do you have a QQ?

I have. But my work is too busy and I almost can't chat on it.
You can mail me or post message here or in my tiny forum(in my homepage).
Posted on 2003-05-07 20:45:03 by KomsBomb
I believe my ojbect model can be transplant to MASM by using my VTable macros.
What you should do is only to rewrite the code in MASM mode.
Do you think each one should have his own object model?
Posted on 2003-05-07 20:57:22 by KomsBomb
Our purpose is almost the same, but the principle of the design was not identical. I try to ease the work by OOP, not bring new complexity
Posted on 2003-05-07 21:39:39 by taowen2002
the ease of one = the complexity of another :)
Posted on 2003-05-07 21:41:46 by bitRAKE

Our purpose is almost the same, but the principle of the design was not identical. I try to ease the work by OOP, not bring new complexity

What's your easy way? Not bring new complexity? OOP is really more complex than procedural program. In complex OOP program, it's very hard to understand the code because of the complex polymorphism. To understand it, the programmer must trace the program rather than read the code statically.
Assembly is not for the man who want simple. Delphi is much more useful and simple than assembly, try it.
Posted on 2003-05-07 21:54:19 by KomsBomb
I mean the complexity in coding not in thinking. The syntax can be easy. Thinking in OOP is hard, but we can let the syntax to express idea easier.
I have used delphi for a long time, but I have been using C++ for a more long time.
Posted on 2003-05-07 23:12:38 by taowen2002
I've beening watching TV every time for very very long time, but I don't know how the Television works.
Posted on 2003-05-07 23:57:49 by KomsBomb
Yes, I know a little, But everyone have the right to try
Posted on 2003-05-08 01:51:57 by taowen2002