Priority 1) - I think he means; writing a "3d lib" a new engine & sdk, with a "b3d-like design" (eg. syntax, "entities" etc..), this doesn't nessecarily mean a product release with its own internal compiler, IDE etc. as he categorically states "There will NOT be a new language comming". (& he then goes on to say that writing another "b3d" is made redundant by max+3d)
Priority 2) - the blitzmax wrap naturally comming as the next step (as an unwrapped lib is not much fun on its own, except in c++).
Priority 3) - Wraps for other languages (& a "b3d2" perhaps?, as he did say "maybe").
At least, thats how i am interpreting it :/
Either way its all good. As long as i end up with a Cross platform BlitzMax3D, i dont really care. I dont mind using lists myself, but a type default list in bmax like John Pickford suggested would be useful sometimes.
Priority 2) - the blitzmax wrap naturally comming as the next step (as an unwrapped lib is not much fun on its own, except in c++).
Priority 3) - Wraps for other languages (& a "b3d2" perhaps?, as he did say "maybe").
At least, thats how i am interpreting it :/
Either way its all good. As long as i end up with a Cross platform BlitzMax3D, i dont really care. I dont mind using lists myself, but a type default list in bmax like John Pickford suggested would be useful sometimes.