adding bytes about millfork HOT 4 CLOSED

I'll close it when I make the error message nicer. Right now the compiler simply throws an exception and immediately exits. It is ugly. I want it to report the error, point to the correct line and continue compiling to search for more errors.

from millfork.

Yes, this is the expected behaviour.

The type of the left side doesn't matter. The type check goes as follows:

• 246 fits in a byte, therefore it's a byte
• 18 fits in a byte, therefore it's a byte
• + has two bytes on its sides, therefore the result of 246+18 is a byte
• the constant evaluator sees the overflow and informs you that something is wrong

You can get the same issue in C/C++, but the compiler won't warn you. For example, most 32- and 64-bit compilers will compile the following without any warning:

long long sum = 0x8000'0000u + 0x8000'0000u;

to long long sum = 0;, even thought 0x1'0000'0000u would fit in a long long just fine.

The difference is that Millfork does this at every integer size (there are no privileged "default" integer types like int in C) and doesn't let obvious overflows compile.

from millfork.

Ok! thanks. So you can close this issue.

from millfork.

Error reporting has been improved as of 0.3.12, closing.

from millfork.