In problems with source_modifier: no_main, if the header of the function is wrong the report is useless

[pauek]

As a problem author, I made a problem which contained a little mistake (the problem is X12675, password 42424242). I changed the header of the solution function from

int punto_verde(queue<int>& c, int num_emp);

to

int punto_verde(int num_emp, queue<int>& c);

but I forgot to update the problem statement in one of the languages. So students reading the problem in that language sent the problem with a function with a wrong header, swapping both parameters.

The issue is that Jutge returned a veredict of CE (Compilation Error) but the message was Unreported error.. This was very confusing to students since they thought that they had a compilation error even if locally their program could work fine. Since Jutge has a low track record of mistakes, when one occurs, makes students doubt and it is bad for their confidence.

We should change the PRO2 compilation process so that if the header of the function is wrong, either just returns the text of the compiler (hoping that that is enough) or specifically tells you that the header is wrong, comparing both.