Fix table formatting.

This commit is contained in:
David C W Brown 2016-07-14 09:44:52 +01:00 committed by GitHub
parent 240c29c6dd
commit 9903c9c435

View file

@ -52,15 +52,15 @@ There are three strategies that clients may wish to use:
we fix Oberon type sizes across platforms, and introduce a new LONG64 type we fix Oberon type sizes across platforms, and introduce a new LONG64 type
as follows: as follows:
| Oberon type | Size | | Oberon type | Size |
| ----------- | ---------------- | | ----------- | ---------------- |
| BOOLEAN | 8 bits | | BOOLEAN | 8 bits |
| BYTE | 8 bits unsigned | | BYTE | 8 bits unsigned |
| SHORTINT | 8 bits signed | | SHORTINT | 8 bits signed |
| INTEGER | 16 bits signed | | INTEGER | 16 bits signed |
| LONGINT | 32 bits signed | | LONGINT | 32 bits signed |
| SET | 32 flag bits | | SET | 32 flag bits |
| LONG64 | 64 bits signed | | LONG64 | 64 bits signed |
This gives a set of sizes that are available on all platforms (even SDCC This gives a set of sizes that are available on all platforms (even SDCC
supports 64 bit ints), and which have fixed characteristics (e.g. the size of supports 64 bit ints), and which have fixed characteristics (e.g. the size of
@ -72,11 +72,11 @@ There are three strategies that clients may wish to use:
efficient size available. On x86 we stick with the sizes as above, but for efficient size available. On x86 we stick with the sizes as above, but for
x64 we make changes to INTEGER, LONGINT and SET as follows: x64 we make changes to INTEGER, LONGINT and SET as follows:
| Oberon type | Size on x64 | | Oberon type | Size on x64 |
| ----------- | ---------------- | | ----------- | ---------------- |
| INTEGER | 32 bits signed | | INTEGER | 32 bits signed |
| LONGINT | 64 bits signed | | LONGINT | 64 bits signed |
| SET | 64 flag bits | | SET | 64 flag bits |
3) Supporting system code, especially memory management. 3) Supporting system code, especially memory management.