I lately am getting the following Error message (1.38 ) :
**Error**:'return' statement required for exit from non 'void' functions

with earlier versions there was not such a message, and I don't think this is intended...?

This the code:

With regular C compilers this is working -
how should I add an extra return here? and why?

Ford,

I tried your code (also on 1.38 Beta) and don't seem to be seeing the same problem as you.

In any case, it's pretty easy to guess what might be going on. Generally, compilers try to be smart and help you avoid things that are unintended. In this case, it appears that the compiler is not figuring out that the code will always return something, because all of the return statements are inside of conditional branches.

An easy way to fix this would be to remove the 'else' clause and just leave the last return statement outside of the 'if' altogether. That way, the compiler will have an easy time seeing that, no matter what, a value will always be returned:



By the way, are you sure that this is the only function in the code that could be causing the problem? As I mentioned earlier, your unmodified code appears to compile just fine for me (no errors).

ok, fine, thx, this will work.

no, there suddenly are more functions than just this one causing errors (with earlier RobotC version it has been working fine), but all error messages are due to the same "return error".
I really would appreciate "The Compiler" not always to break "his" head about my code optimization and not always to give an error message where there is no error!

Ford,

I, as the compiler expect you to be smarter than I am. Even if I try to figure out most frequent mistakes my users might have made, I am simply an algorithm, not even a complex one. Keep in mind that users of a software, just because of having outnumbered its creators, are *always* more inventive.

I, as the compiler generate pure clean and understandable bytecode from the character mess what you are typing just because you are far from fluent in raw machine code. Please be patient if I am unable to follow each and every branch of your thinking. The aforementioned example tries to affront my abilities. However, this error message is aimed to help those users who write more complex multi-branch conditional statements in which case it would require improportional efforts from me to evaluate the semantics whether the branches cover all possible input data or not.

Thanks for your understanding.

But, anyway, you are one of the thoughest beta tester I've ever seen

I tried it again, in other source codes, and the faulty error messages remain.

this is another case, where I NOW get the same error message, whereas with the 1.10 -1.22 I didn't:

**Error**:'return' statement required for exit from non 'void' functions

There should be a way to switch off those foolish error messages.

I reported this to the bug tracker.