Quote from Winnie:-
3. When the overly complex and complicated language C++ is more intuitive to you than the simple and minimalist BlitzMax, then you cannot have seriously looked at BlitzMax in the first place.
Section of Marks worklog:-
I've returned to c++ to do this. As much as I love the idea of using BlitzMax, there's just no getting around the fact that c++ is *faster* and considerably easier to use when it comes to talking to the OS and gfx/misc APIs.
Which means Mark hasnt seriously looked at BlitzMax too! :P
3. When the overly complex and complicated language C++ is more intuitive to you than the simple and minimalist BlitzMax, then you cannot have seriously looked at BlitzMax in the first place.
Section of Marks worklog:-
I've returned to c++ to do this. As much as I love the idea of using BlitzMax, there's just no getting around the fact that c++ is *faster* and considerably easier to use when it comes to talking to the OS and gfx/misc APIs.
Which means Mark hasnt seriously looked at BlitzMax too! :P