Threads are great etc, but as I said before there are sections of code in Max that will *not* multithread nicely and need some kind of locking mechanism.
99.99% of the time there will be no apparent problems. It's only when a thread switch occurs at a precise point in the code that something will go wonky.
I am definitely interested in adding threading in the future, but I believe it will require some language additions to be efficient/practical.
Did you smack John over the head and steal his account? I swear his name was on this post for ages....I read Yavin's reply and......Umm..seriously confused now...another dirkduck? :)
Anyway, mark I'm not saying threads are going to work with every BRL module, as obviously any that use unreachable(I.e unlockable) resources will eventually mess up,
my point is whoever wants to use them, if they *don't* blindly walk into it with a big 'what's going on here then grin' look on there face, they can manage the downsides and come out on top. Like rambo...