[Oberon] Negative integer literals in Oberon
Jörg
joerg.straube at iaeth.ch
Sun Apr 26 16:05:42 CEST 2020
The subtle semantical refinement that hex values do not follow the „normal“ INTEGER rules is unfortunately not written in the report but his intention can be found in NW‘s compiler: not compared to „maxint“ and if you wrote more than 8 hex digits, only the 32 LSB are stored.
IF ch = "H" THEN (*hex*)
REPEAT h := d[i];
IF h >= 10 THEN h := h-7 END; (* assumes ASCII coding *)
k := k*10H + h; INC(i) (*no overflow check*)
UNTIL i = n;
ELSE (*decimal integer*)
REPEAT
IF d[i] < 10 THEN
IF k <= (maxint - d[i]) DIV 10 THEN k := k*10 + d[i] ELSE Mark("too large"); k := 0 END
ELSE Mark("bad integer")
END ;
INC(i)
UNTIL i = n;
END;
sym := int; ival := k
Gruss, Jörg
> Am 26.04.2020 um 14:47 schrieb Jörg <joerg.straube at iaeth.ch>:
>
> This propsal is based on the assumption that negative literals do exist.
> I don‘t think so.
>
> If you write 0FFFFH you define 16 bits, not -1. if you want to define -1 write -1 or -1H.
>
> br
> Jörg
>
>>> Am 26.04.2020 um 13:34 schrieb Chris Burrows <chris at cfbsoftware.com>:
>>>
>>
>> FYI Oberon microsystems tackled this problem in the following way when 64-bit integers were introduced in their Component Pascal language:
>>
>> “Hexadecimal integer constants now can be specified either as 4 byte (e.g., 0FFFFFFFFH) or 8 byte
>> constants (e.g., 0FFFFFFFFFFFFFFFFL). This allows to distinguish negative INTEGER hex
>> constants from positive LONGINT hex constants. For example, 0FFFFFFFF denotes -1 when
>> interpreted as INTEGER, but 4294967295 when interpreted as a LONGINT.
>> Integer constants are always INTEGER (4 byte) values. Assignment of an integer constant to a
>> smaller type (e.g., BYTE) is legal if the constant lies within the range of the target type. Integer
>> constants of other types can only be constructed using SHORT or LONG, except that sufficiently
>> large constants automatically have type LONGINT.”
>>
>> Ref: What’s New in Component Pascal, Cuno Pfister, Oberon microsystems, Inc. March 2001
>>
>> Regards,
>> Chris Burrows
>> https://www.astrobe.com
>>
>>
>> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of dave at brownsmeet.com
>> Sent: Sunday, 26 April 2020 8:12 PM
>> To: ETH Oberon and related systems
>> Subject: Re: [Oberon] Negative integer literals in Oberon
>>
>>
>>
>> To be clear - I would like VOC to allow myint32 := 90909090H, but VOC's support of 64 bit literals gets in the way.
>>
>> My advice therefore is that if you never plan to support integers of more than 32 bits, go ahead and allow myint := 90909090H.
>>
>> If you plan to add support for 64 bit integers later, you will need to work around the problems I described below. I cannot see how to do that, but I would love a solution.
>>
>> -- Dave.
>>
>> On 2020-04-26 10:14, Joerg wrote:
>>
>> In earlier Oberon versions, variable integer size was supported: INTEGER and LONGINT. LONGINT is not officially supported in Oberon-07 but the compiler internally declares TYPE LONGINT = INTEGER.
>> The concept of variable integer size is not supported in Oberon-07 anymore. Every INTEGER has one (implementation dependent) size, be it 16 or 32 or 64 or ...
>>
>> Syntactically and conceptionally, negative literals do not exist. Only results of calculations can be negative as they are done signed per report.
>> CONST neg = -1; is conceptionally the result of subtracting the literal 1 from 0, and NOT the literal -1.
>>
>> If you use the hex suffix H to fill up the bits of the underlying INTEGER, you need to know the INTEGER size and are per definition in the grey, non-portable, implementation-dependent area of coding
>>
>> If you use the hex suffix H to specify a (unsigned) 32 bit value for low level modules that work with 32 bits (on disc or memory or so) the size of the INTEGER does not matter (as long as it's 32 bits or larger of course) as your low level module have to treat the passed values MOD 100000000H anyhow.
>>
>> br
>> Jörg
>>
>>
>> Am 26.04.2020 um 10:25 schrieb Joerg <joerg.straube at iaeth.ch>:
>>
>> Chris
>>
>> 1) b := i; is allowed, right?
>> 2) b := i; does not generate a range check, right?
>> 3) i := 511; b := i;
>>
>> If 3) doesn't generate a range check, but you want to be compliant to the report, you implement the assignment as b := i MOD 256;
>> as any value MOD 256 is between 0..255.
>>
>> br
>> Jörg
>>
>>
>> Am 26.04.2020 um 09:28 schrieb dave at brownsmeet.com:
>>
>> ((Lapsed) VOC maintainer here.)
>>
>> In both VOC and Oberon 2013, integer literals are parsed in the symbol parser (VOC :OPS.Mod or 2013:ORS.MOD) and stored in the symbol table as signed integer values.
>>
>> Later, during expression compilation, their size is determined by the magnitude of their signed integer value.
>>
>> The difference between Oberon 2013 and VOC is the largest integer type, which is 32 bit on Oberon 2013 and 64 bit in VOC.
>>
>> The special handling that allows a hex literal with top bit set to be treated as a signed value happens at the time the literal is parsed as a symbol independent of what context it is being used in. (Consider e.g. 'CONST mask = 90909090H' - CONST parsing does not know whether this constant will be used in a 64 bit, 32 bit, 16bit or other context.)
>>
>> VOC and Oberon 2013 do both allow the hex special case top bit set parsing behaviour, the difference being the integer literal size.
>>
>> Thus VOC accepts myint64 := 9090909090909090H because 9090909090909090H is parsed as a negative 64 bit signed integer.
>>
>> But VOC does not accept myint32 := 90909090H because 90909090H is parsed as a positive 64 bit signed integer.
>>
>> VOC has no way to parse 90909090H as a negative 32 bit signed integer.
>>
>> - I did wonder about adding a further suffix letter to indicate the intended size, but I couldn't satisfy myself that any solution was simple enough to be easy to understand.
>>
>> - Note that this is independent of VOC's -Ox compatibility setting: that sets the default INTEGER size, not integer literal size - integer literals always support the largest available integer size which is SYSTEM.INT64 aka HUGEINT.)
>>
>> -- Dave
>>
>>
>>
>> On 2020-04-25 22:52, Chris Burrows wrote:
>>
>> It all depends on what size (i.e. number of bits) INTEGER is defined as on the system you are using as to what range of numbers are valid INTEGERs. Since 2011, the range of INTEGER values is no longer defined in the Language Report; it is implementation-dependent.
>>
>> In the Project Oberon (2013) RISC5 compiler, INTEGER is 32 bit so 90909090H is a valid INTEGER. Maybe you used the default (-O2) option in VOC? If so, INTEGER is 16 bit so 90909090H would be too large. Make sure you are compiling with the VOC –OC option instead if you want INTEGER to be treated as a 32 bit quantity.
>>
>> Note that 9090H would be a negative number on a 16-bit INTEGER system but a positive number on a 32-bit INTEGER system.
>>
>> Regards,
>> Chris Burrows
>> CFB Software
>> https://www.astrobe.com
>>
>> From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of Arthur Yefimov
>> Sent: Sunday, 26 April 2020 12:38 AM
>> To: oberon at lists.inf.ethz.ch
>> Subject: [Oberon] Negative integer literals in Oberon
>>
>> While developing the compiler[1], we got a question
>> whether it is possible to write the following:
>>
>> PROCEDURE DWord(n: INTEGER);
>> ...
>> DWord (90909090H)
>>
>> (where INTEGER is 32-bit).
>>
>> Some compilers give an error (i.e. VOC), while this works in the
>> Project Oberon (2013) compiler. This would turn out to be quite convenient,
>> because the purpose of DWord in our code was to write 4 bytes to the file
>> given as INTEGER (using little-endian byte order).
>>
>> DWord has the following implementation (module Generator[2]):
>>
>> PROCEDURE DWord (n: INTEGER);
>> BEGIN
>> Files.Write (r, CHR (n MOD 100H));
>> Files.Write (r, CHR (n DIV 100H MOD 100H));
>> Files.Write (r, CHR (n DIV 10000H MOD 100H));
>> Files.Write (r, CHR (n DIV 1000000H))
>> END DWord;
>>
>> The Oberon language report does not indicate that literal 90909090H
>> should be considered an error if INTEGER has 32 bits.
>>
>> In this experiment, an online RISC emulator[3] was used.
>>
>> References:
>> [1] https://github.com/kekcleader/oberon
>> [2] https://github.com/kekcleader/oberon/blob/master/Mod/Generator.Mod
>> [3] http://schierlm.github.io/OberonEmulator/emu-wasm.html?image=FullDiskImage&width=1024&height=768
>>
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>>
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20200426/f901067e/attachment.html>
More information about the Oberon
mailing list