0 Members and 1 Guest are viewing this topic.
Hmm... I'm looking into this and it appears it might be an Axe bug when compiling to an app and not a bug in the program. If they were designed for version 0.4.4 and I find that is indeed a bug in Axe itself, I will try to recompile the identical source code with a fixed version of the parser so that the entries are not penalized. But then again, how would that have gone unnoticed by the contestant? Perhaps they were meant to be compiled to MirageOS instead of to an application...
Oddly enough, the other version you sent afterward didn't do that