Having a C compiler around is a requirement of BlitzMax - installing Xcode means nothing else than also installing GCC, so the C compiler will be there anyway.
As for the GetNextProcess() question: This is systems programming, and therefor the natural domain of C and Assembler. In my opinion, writing C-wrappers for stuff like that is the only proper solution - on any system and any host programming language.
I only took a very short glimpse at the documentation of GetNextProcess, but it seems that this function and its relatives accept a long list of parameters, of which many might not be directly translatable to BlitzMax's set of native datatypes. However that might really be, I definitely would only use it via a nice wrapper.
As for the GetNextProcess() question: This is systems programming, and therefor the natural domain of C and Assembler. In my opinion, writing C-wrappers for stuff like that is the only proper solution - on any system and any host programming language.
I only took a very short glimpse at the documentation of GetNextProcess, but it seems that this function and its relatives accept a long list of parameters, of which many might not be directly translatable to BlitzMax's set of native datatypes. However that might really be, I definitely would only use it via a nice wrapper.