anyway whatever you do - it wont be tricky if you stick to
storing one specific object type on your stack..
If you want to mix n match - letting primitives like float
and int be stored alongside object pointers..things get a
little tricky - partially becuase return type is explicit, you might
need multiple return methods, one for each basic type..
and additionial information stored with every object pushed on to the stack - basically wrapper which can
contain each type of object, and information about what
type is actually being stored..a mask might be enough..
I dont know enough about what is, and what isnt possible
with bmax objects.. I cant actually see how a clean system
would be developed that can store all possible types under one simpler interface..a single stack that can mix n
match... lol, i guess i didnt think this through when i made
my initial post... ;)
id grab dreamora's work..save yourself a headache
storing one specific object type on your stack..
If you want to mix n match - letting primitives like float
and int be stored alongside object pointers..things get a
little tricky - partially becuase return type is explicit, you might
need multiple return methods, one for each basic type..
and additionial information stored with every object pushed on to the stack - basically wrapper which can
contain each type of object, and information about what
type is actually being stored..a mask might be enough..
I dont know enough about what is, and what isnt possible
with bmax objects.. I cant actually see how a clean system
would be developed that can store all possible types under one simpler interface..a single stack that can mix n
match... lol, i guess i didnt think this through when i made
my initial post... ;)
id grab dreamora's work..save yourself a headache