proj-oot-ootMainImplementation

compiler warning (or scripting level requirement) if anything is REdefined with a macro (esp. if it's a language-level or stdlib-level thing)

compiled Oot libraries can be linked to Oot programs which are under a different Oot version, even if the Oot version requirement to compile the library itself is incompatible with the Oot version required by the program

a soft crash (eg a bug in Oot code, not a segfault caused by a bug in oot, nor one caused by a bug in a C or other external library that was called by Oot code) does not crash anything more than the greenthread that it occurred in in

compilation is deterministic function from source code to object code; compiling the same Oot source code on the same compiler version will produce the same binary (eg macros like C's __DATE__ macro)