Re: [fpc-devel] Evaluation order in expressions

On Tue, 30 Jul 2019, Ondrej Pokorny wrote: On 30.07.2019 08:33, Michael Van Canneyt wrote: The documentation has already been fixed in this regard, there was a bugreport about it not so long ago. Great, thank you. Is there some online version of the latest documentation trunk (nightly buil

Re: [fpc-devel] Evaluation order in expressions

On 30.07.2019 08:33, Michael Van Canneyt wrote: The documentation has already been fixed in this regard, there was a bugreport about it not so long ago. Great, thank you. Is there some online version of the latest documentation trunk (nightly build)? Ondrej _

Re: [fpc-devel] Evaluation order in expressions

On Tue, 30 Jul 2019, Ondrej Pokorny wrote: On 30.07.2019 08:23, Ondrej Pokorny wrote: /Remark: The order in which expressions of the same precedence are evaluated is not guaranteed to be left-to-right./ Is this valid for boolean expressions, too? I use the following construct with {$BOOLEV

Re: [fpc-devel] Evaluation order in expressions

On 30.07.2019 08:23, Ondrej Pokorny wrote: /Remark: The order in which expressions of the same precedence are evaluated is not guaranteed to be left-to-right./ Is this valid for boolean expressions, too? I use the following construct with {$BOOLEVAL OFF}: Result := Assigned(MyObject) and (MyO

[fpc-devel] Evaluation order in expressions

Hello, can somebody comment on the Remark from https://www.freepascal.org/docs-html/ref/refch12.html ? /Remark: The order in which expressions of the same precedence are evaluated is not guaranteed to be left-to-right./ Is this valid for boolean expressions, too? I use the following construc

Re: [fpc-devel] Minor debate with ISO standard on case blocks

As someone on the issue pointed out... on page 2, section 3.1: 3.1 Error A violation by a program of the requirements of this International Standard that a processor is permitted to leave undetected. NOTES 1. If it is possible to construct a program in which the violation or non-violation o

[fpc-devel] Minor debate with ISO standard on case blocks

Hi everyone, So there's been an issue raised in regards to ISO compliance with case blocks (when under $mode iso).  Currently, a compiler error is raised if a case block does not have exhaustive coverage for the input type (it's a warning on oth