MiranDMC

Yes, but whole code is compiled, no matter what branching is used inside it. So all "ASM" blocks will be compiled then. Maybe ASM block should then contain preferred compiler/platform/settings...

This very risky. The distinction between gosub's and CLEO's return should be obvious. Worst debugging sessions I had was caused by muscle memory and using return instead of cleo_return. Scripts...

Hm, ok. Will it work with functions having multiple exit points?

Already done.

Are all these new (positive indexed) variables considered as local scoped? I think there is need for 'global' variables as people keep using real globals despite warned many times to...

Good. cleo_calls provide local scope, then the @34+ will provide lacking 'global' scope of the current script. I think I saw somewhere opcodes for 'cleo shared' values. Anyway, you can...

That would be useful feature. BTW I think array definitions should support not providing array size just by not providing the number, like ```2@(0@,i)```

Introducing any kind of global variables leads to exactly same problem we have with current global variables. You never know who is going to use them.

It quickly turns into "return whatever". My concern is how these variables will be named? Will there be aliases by default, so you can use on_mission instead of '-1@'? We...

> It might be helpful to include as much class/struct and field information as possible. For example: CTheScripts::OnAMissionFlag ==> CTheScripts__OnAMissionFlag Seems like unnecessary introducing backstage CPP implementation details for users...