Blocks and Bricks: A light OOP System

[HSE]

Global OOP optimizer could remove useless code and zero unused methods.

Fantastic 

How you do that in assembly?

[TimoVJL]

Only those people, who develops assemblers, compilers and linkers knows that.
Linker have to be OOP aware.
Have been known for long time, those who had read Dr Dobbs long time ago, knows that.

[HSE]

Have been known for long time

Naturally 

Thanks.

[jj2007]

could remove useless code and zero unused methods.

Unused methods should not generate code in Assembly. If they do, something is wrong with your system.

[HSE]

could remove useless code and zero unused methods.

I don't say that.

Unused methods should not generate code in Assembly.

Why not?

[daydreamer]

could remove useless code and zero unused methods.

Unused methods should not generate code in Assembly. If they do, something is wrong with your system.

Isn't it heresy in asm with a system that creates bloat?
There was lightweight oop many years ago I tried

Only those people, who develops assemblers, compilers and linkers knows that.
Linker have to be OOP aware.
Have been known for long time, those who had read Dr Dobbs long time ago, knows that.

Show link if you have it
I only managed to try simplest conditional assembly in source file
I think it was a SSE source code for a math functions, to turn off assembling for unused proc

[jj2007]

could remove useless code and zero unused methods.

I don't say that.

Correct, it was Timo. I had selected these words to use the SMF feature Quote selected text, but apparently SMF can't trace back the quote to its real owner. My apologies

Unused methods should not generate code in Assembly.

Why not?

A OOP "method" is nothing else than an entry in a structure. You may or may not use it, but the mere existence of the entry does not create code.

[Rockphorr]

How do you implement the heap of objects ?? Is it a list or a tree or a array or something else ?

Can be implemented how you want.

It is interesting for me how it should be implemended.

Something i found here:

https://www.youtube.com/watch?v=Bym7UMqpVEY&list=PL3BR09unfgciJ1_K_E914nohpiOiHnpsK

(russian)

[HSE]

apparently SMF can't trace back the quote to its real owner

That was strange 

, but the mere existence of the entry does not create code.

So far I understand, the linker don't know if a procedure is used or not, only know if there is a reference to the procedure address. In standard OOP there are references to all methods, then linker include all of them.

[TimoVJL]

Didn't find proper links, but something for masm 
Object-Oriented Programming in Assembly Language

Using smart linking

[jj2007]

Didn't find proper links, but something for masm 
Object-Oriented Programming in Assembly Language

Randy at work, over 33 years ago

[HSE]

It is interesting for me how it should be implemended.

There is no unique solution, it depend on Object cycle of live and processes, etc.

Also personal preferences play a role. Biterider use collections a lot. I use perhaps more SDLL.

https://www.youtube.com/watch?v=Bym7UMqpVEY&list=PL3BR09unfgciJ1_K_E914nohpiOiHnpsK

Probably interesting in more advanced lessons, but hard to understand 

[Biterider]

Hi
In the OOP world, there are basically two ways of dealing with methods (also known as procedures). If they are resolved via stored addresses, usually in virtual tables, the linker has no chance of removing code, as the execution path is determined at runtime. 
Static methods, on the other hand, behave like regular procedures. In this case, if e.g. a C compiler is instructed to perform "function-level linking" (/Gy switch - MS), each procedure is stored in its own COMDAT. In this way, the linker is able to remove the dead code.
Unfortunately, to my knowledge, none of the current assemblers are able to do this yet. The only alternative currently known to me would be to compile the individual static methods into a library, so that the linker can take over this task.

Regards, Biterider

[TimoVJL]

Microsoft (R) Macro Assembler Version 12.00.40629.0

/Gy[-] separate functions for linker

[Biterider]

Thanks Timo
Good to know. Then that is the way to go.

Biterider