mirror of
https://github.com/catseye/SixtyPical.git
synced 2026-04-27 02:18:14 +00:00
Spec and tests for initial values of locations.
This commit is contained in:
1 parent
2a86793246
commit
6cf8b5fe1e
3 files changed
+28
-4
No files matched your search
+8
-2
@@ -1,7 +1,7 @@
|
||||
SixtyPical
|
||||
==========
|
||||
|
||||
This document describes the SixtyPical programming language version 0.6,
|
||||
This document describes the SixtyPical programming language version 0.7-PRE,
|
||||
both its execution aspect and its static analysis aspect (even though
|
||||
these are, technically speaking, separate concepts.)
|
||||
|
||||
@@ -79,10 +79,16 @@ name.
|
||||
|
||||
byte pos
|
||||
|
||||
A location in memory may be given explicitly on a user-defined memory location.
|
||||
An address in memory may be given explicitly on a user-defined memory location.
|
||||
|
||||
byte table screen @ 1024
|
||||
|
||||
Or, a user-defined memory location may be given an initial value. But in this
|
||||
case, an explicit address in memory cannot be given.
|
||||
|
||||
byte pos = 0
|
||||
byte table scores = [1, 3, 8, 17, 26, 100]
|
||||
|
||||
A user-defined vector memory location is decorated with READS and WRITES lists
|
||||
like a routine (see below), and it may only hold addresses of routines which
|
||||
are compatible. (Meaning, the routine's inputs (resp. outputs, trashes)
|
||||
|
||||
Reference in new issue
Block a user