Am 06.10.2021 um 11:14 schrieb Sven Schreiber:
Am 06.10.2021 um 10:08 schrieb Riccardo (Jack) Lucchetti:
>
> Uhm. We do catch that special case: it's the "else" branch in
> undefined_symbol_error() from lib/src/genlex.c, where we store the
> appropriate message string into the parser struct. The trouble is, it
> doesn't get printed, for some reason.
Hm, my guess would rather be that undefined_symbol_error() isn't reached
in this post-incrementation case?
The only evidence I have, though, is that in other cases I get the
message "symbol foo is undefined" alright.
BTW, the informative error message is also there when doing "eval b++"
or "print b++".
-s