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

Small documentation updates.

Browse Source
This commit is contained in:
Chris Pressey 2018-09-14 13:14:32 +01:00
parent 7680f09850
commit 6e9b15e017
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
HISTORY.md
View File

@ -10,6 +10,7 @@ History of SixtyPical
references in _all_ operations will be resolved after parsing. references in _all_ operations will be resolved after parsing.
* As a consequence, trying to call or goto a non-routine-typed symbol * As a consequence, trying to call or goto a non-routine-typed symbol
is now an analysis error, not a syntax error. is now an analysis error, not a syntax error.
* Deprecated `routine foo ...` syntax has been removed.
* Split TODO off into own file. * Split TODO off into own file.
* `sixtypical` no longer writes the compiled binary to standard * `sixtypical` no longer writes the compiled binary to standard
output. The `--output` command-line argument should be given output. The `--output` command-line argument should be given

16
README.md
View File

@ -6,16 +6,16 @@ _Version 0.17. Work-in-progress, everything is subject to change._
**SixtyPical** is a low-level programming language with advanced **SixtyPical** is a low-level programming language with advanced
static analysis. Many of its primitive instructions resemble static analysis. Many of its primitive instructions resemble
those of the 6502 CPU — in fact it is intended to be compiled to those of the 6502 CPU — in fact it is intended to be compiled to
6502 machine code — but along with these are constructs which 6502 machine code — but along with these instructions are
ease structuring and analysizing the code. constructs which ease structuring and analyzing the code. The
language aims to fill this niche:
SixtyPical aims to fill this niche:
* You'd use assembly, but you don't want to spend hours * You'd use assembly, but you don't want to spend hours
debugging (say) a memory overrun that happened because of a debugging (say) a memory overrun that happened because of a
ridiculous silly error. ridiculous silly error.
* You'd use C, but you don't want the overhead of compiler-added * You'd use C or some other "high-level" language, but you don't
code to manage the stack and registers. want the extra overhead added by the compiler to manage the
stack and registers.
SixtyPical gives the programmer a coding regimen on par with assembly SixtyPical gives the programmer a coding regimen on par with assembly
language in terms of size and hands-on-ness, but also able to catch language in terms of size and hands-on-ness, but also able to catch
@ -43,8 +43,8 @@ machine-language programming idioms, such as
SixtyPical is defined by a specification document, a set of test cases, SixtyPical is defined by a specification document, a set of test cases,
and a reference implementation written in Python 2. The reference and a reference implementation written in Python 2. The reference
implementation can analyze and compile SixtyPical programs to 6502 machine code, implementation can analyze and compile SixtyPical programs to 6502 machine
which can be run on several 6502-based 8-bit architectures: code, which can be run on several 6502-based 8-bit architectures:
* Commodore 64 * Commodore 64
* Commodore VIC-20 * Commodore VIC-20