AD: I have a Dual core system, any current gen PC is dual core.
If you explain me why I should waste hundreds of lines to fake threading in a "modern language" although I have true multithreading, I perhaps start seeing any sense for it. But for now, its just a joke.
Not only BM does not support threading, the GC is not even thread safe so you could use callbacks and threaded libraries because it will bomb this damned thing. But I'm sure as this topic is all time returning, Mark will accept at some point that BM users did not pay to switch to BM to stay on 1998 tech, even if he insists that anything can be done by faking threading through slicing.(which for most things might be true but it is still much harder and tends to create more problems than true threads, especially as current gen computers are fast enough for several threads side a side even on single core machines)
Until then, I will simply use the same languages to do this kind of stuff I'm using now. PureBasic, C++, C# even thought I would prefer working with BM. But it is just not possible at the moment.
No interest in time slicing AI stuff and the like. The topic is complex enough without adding another layer of complexity with a large bug potential that is not needed nor desired.
If you explain me why I should waste hundreds of lines to fake threading in a "modern language" although I have true multithreading, I perhaps start seeing any sense for it. But for now, its just a joke.
Not only BM does not support threading, the GC is not even thread safe so you could use callbacks and threaded libraries because it will bomb this damned thing. But I'm sure as this topic is all time returning, Mark will accept at some point that BM users did not pay to switch to BM to stay on 1998 tech, even if he insists that anything can be done by faking threading through slicing.(which for most things might be true but it is still much harder and tends to create more problems than true threads, especially as current gen computers are fast enough for several threads side a side even on single core machines)
Until then, I will simply use the same languages to do this kind of stuff I'm using now. PureBasic, C++, C# even thought I would prefer working with BM. But it is just not possible at the moment.
No interest in time slicing AI stuff and the like. The topic is complex enough without adding another layer of complexity with a large bug potential that is not needed nor desired.