[Oberon] Negative integer literals in Oberon

August Karlstrom fusionfile at gmail.com
Sat May 2 18:54:30 CEST 2020

On 2020-05-02 13:43, Joerg wrote:
> If the compiler does not generate a runtime range check for b := i,
> then b := 300; should not generate a compile time error neither.
Why not? For a byte variable b, the statement b := 300 is invalid 
according to the language report, so I think the compiler should reject it.

-- August

More information about the Oberon mailing list