@ jH...
although the Blitz entity system can be thought of as being object oriented... it is incapable of providing you with anything more than the basic hierarchical functionality that is already designed into it...
i think that to call this by itself OOP is stretching the term just short of its limits...
i would better look at it as being a hierarchical relationship structure that you can plug things into... but the structure is fixed... non polymorphic... and nom modifiable...
@ Alberto...
OOP is only as complicated as you the developer, and MS Visual series of compilers wanna make it...
the clean simplicity of OOP is apparent when you find yourself only coding what you need at the moment... and then weeks later when that rush of genius as eluded you, being able to leverage what you've already done by instantiating or building upon existing class functionality with only needing to acknowledge the interfaces...
nothing can be less complicated, and more natural than that :)
--Mike
although the Blitz entity system can be thought of as being object oriented... it is incapable of providing you with anything more than the basic hierarchical functionality that is already designed into it...
i think that to call this by itself OOP is stretching the term just short of its limits...
i would better look at it as being a hierarchical relationship structure that you can plug things into... but the structure is fixed... non polymorphic... and nom modifiable...
@ Alberto...
OOP is only as complicated as you the developer, and MS Visual series of compilers wanna make it...
the clean simplicity of OOP is apparent when you find yourself only coding what you need at the moment... and then weeks later when that rush of genius as eluded you, being able to leverage what you've already done by instantiating or building upon existing class functionality with only needing to acknowledge the interfaces...
nothing can be less complicated, and more natural than that :)
--Mike