Hang-on, dont you use a list to keep track of objects in B3d.
why would you when for a.type=each type is available... i guess you could if you realy wanted to... I dont care what Vb.net does.
you should... not only does a large part of the programming world do, but VB.Net is as close BMax as your likely to see in another programming language...
and what about c or c++... do ya care about what it does...
ahhh probably not... that may be why you find it so easy to accept that a global is really not a global in one context, and a global is not really a global in a second context as well in BMax...
could ya either answer my last question or let someone who knows, answer it before we start playing piss ass with each other :)
it would seem that in some one context, a global is actually a static var... and in another, a global is actually a shared or protected var...
that's what i'm trying to find out...
--Mike