6502/SixtyPical
1
0
Fork 0
mirror of https://github.com/catseye/SixtyPical.git synced 2024-11-26 14:49:15 +00:00
Code Issues Projects Releases Wiki Activity

Clearing up a little mystery I had here.

Browse Source
This commit is contained in:
Chris Pressey 2017-12-12 10:10:58 +00:00
parent e46c6f6c6e
commit b3d2d0bfcf
2 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
eg/proto-game.60p
View File

@ -123,6 +123,10 @@ routine clear_screen
// Game States // Game States
// ---------------------------------------------------------------- // ----------------------------------------------------------------
//
// Because these all `goto save_cinv` at the end, they must have the same signature as that routine.
//
routine game_state_play routine game_state_play
inputs joy2, pos inputs joy2, pos
outputs delta, pos, dispatch_game_state, screen, screen1 outputs delta, pos, dispatch_game_state, screen, screen1

24
tests/SixtyPical Analysis.md
View File

@ -1513,6 +1513,30 @@ But not if the vector is declared inappropriately.
| } | }
? IncompatibleConstraintsError ? IncompatibleConstraintsError
"Appropriately" means, if the routine affects no more than what is named
in the input/output sets of the vector.
| vector vec
| inputs a, x
| outputs x
| trashes a, z, n
|
| routine foo
| inputs x
| outputs x
| trashes z, n
| {
| inc x
| }
|
| routine main
| outputs vec
| trashes a, z, n
| {
| copy foo, vec
| }
= ok
Routines are read-only. Routines are read-only.
| vector vec | vector vec