I have to agree with Dreamora here. BMax seems to be a true multi-purpose language (at least, I know I'm treating it as such) and there's just no reason that multi-threading shouldn't be incorporated. I'm not saying that Mark needs to drop everything he's doing to implement it. I know that won't happen, and I understand and respect that. Introducing MT probably won't earn him any extra money...well, yet that is.
After Max3D is out though, I think it'll become even more of a necessity. Max3D should draw some new customers to Blitz, and after it's completion Mark will hopefully continue to make BMax the great language it's on it's way to becoming. I mean, you toss MT into the mix, along with perhaps a more full-featured audio module, a bit more OO robustness, and there's little reason for any programmer working on a non-AAA title to choose C/C++ over BMax.
After Max3D is out though, I think it'll become even more of a necessity. Max3D should draw some new customers to Blitz, and after it's completion Mark will hopefully continue to make BMax the great language it's on it's way to becoming. I mean, you toss MT into the mix, along with perhaps a more full-featured audio module, a bit more OO robustness, and there's little reason for any programmer working on a non-AAA title to choose C/C++ over BMax.