6502/millfork
1
0
Fork 0
mirror of https://github.com/KarolS/millfork.git synced 2025-04-05 13:37:25 +00:00
Code Issues Projects Releases Wiki Activity

Add more compatibility warnings to documentation

Browse Source
This commit is contained in:
Karol Stasiak 2019-06-28 17:53:00 +02:00
parent 39b07a8bae
commit b0df56c8c0
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
CHANGELOG.md
View File

@ -20,6 +20,9 @@
* Added `init_rw_memory` module for cartridge targets.
* **Breaking change!** Preinitialized writable arrays on cartridge targets
can no longer be read before an explicit call to `init_rw_memory`, either add the call or make the arrays const.
* Added `ensure_mixedcase` function and `oldpet` and `origpet` text encodings.
* Added `MILLFORK_VERSION` preprocessor parameter.

6
docs/lang/syntax.md
View File

@ -116,7 +116,11 @@ Syntax:
then defaults to `default_code_segment` as defined for the platform if the array has initial values,
or to `default` if it doesn't.
* if `const` is present, the array is read-only. Read-only arrays have to have a fixed address and/or defined contents.
* if `const` is present, the array is read-only. Read-only arrays have to have a fixed address and/or defined contents.
**COMPATIBILITY WARNING!** In Millfork 0.3.2 and earlier, arrays couldn't be declared const and on cartridge-based targets,
preinitialized arrays were assumed to be immutable and were allocated to ROM.
Since 0.3.4, only const arrays can be allocated to ROM, non-const arrays are allocated to RAM
and their contents are uninitialized before a call to `init_rw_memory`. See [the ROM vs RAM guide](../api/rom-vs-ram.md).
* `<element type>`: type of the elements of the array.
It must be of size 1 byte.