1
0
mirror of https://github.com/catseye/SixtyPical.git synced 2024-11-22 17:32:01 +00:00
A 6502-oriented low-level programming language supporting advanced static analysis
Go to file
2015-10-18 16:22:36 +01:00
bin Compile repeat loops. 2015-10-18 13:55:40 +01:00
doc Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
eg Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
src/sixtypical Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
tests Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
.gitignore
.hgignore
.hgtags
HISTORY.markdown Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
LICENSE
loadngo.sh
README.markdown Add explicitly-addressed memory locations. 2015-10-18 16:22:36 +01:00
test.sh

SixtyPical

SixtyPical is a very low-level programming language, similar to 6502 assembly, with static analysis through abstract interpretation.

In practice, this means it catches things like

  • you forgot to clear carry before adding something to the accumulator
  • a subroutine that you call trashes a register you thought was preserved

and suchlike.

It is a work in progress, currently at the proof-of-concept stage.

The current released version of SixtyPical is 0.3. The current development version of SixtyPical, unreleased as of this writing, is 0.4-PRE.

Documentation

  • Design Goals — coming soon.
  • SixtyPical specification
  • SixtyPical history
  • [Literate test suite for SixtyPical syntax](tests/SixtyPical Syntax.md)
  • [Literate test suite for SixtyPical execution](tests/SixtyPical Execution.md)
  • [Literate test suite for SixtyPical analysis](tests/SixtyPical Analysis.md)
  • [Literate test suite for SixtyPical compilation](tests/SixtyPical Compilation.md)
  • [6502 Opcodes used/not used in SixtyPical](doc/6502 Opcodes.md)

TODO

For 0.5:

  • table type constructor and indirect addressing.

For 0.6:

  • hexadecimal literals.
  • source code comments.

For 0.7:

  • word type.

For 0.8:

  • vector type.

For 0.9:

  • add line number (or at least routine name) to error messages.
  • 6502-mnemonic aliases (sec, clc)
  • other handy aliases (eq for z, etc.)