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-17 18:29:37 +01:00
bin Get serialization of relative labels correct. 2015-10-17 18:11:23 +01:00
doc Bump version number for release of version 0.3. 2015-10-17 18:29:33 +01:00
eg Get serialization of relative labels correct. 2015-10-17 18:11:23 +01:00
src/sixtypical Don't generate code for empty else blocks. 2015-10-17 18:25:54 +01:00
tests Don't generate code for empty else blocks. 2015-10-17 18:25:54 +01:00
.gitignore Refactor to replace some sketchy code with code actually in use. 2015-10-16 10:40:38 +01:00
.hgignore Refactor to replace some sketchy code with code actually in use. 2015-10-16 10:40:38 +01:00
.hgtags Added tag 0.3 for changeset 5d95f1d75a32 2015-10-17 18:29:37 +01:00
LICENSE Add TODO to README, update license information. 2015-10-16 10:00:51 +01:00
loadngo.sh Call defined routines. 2015-10-17 15:23:00 +01:00
README.markdown Bump version number for release of version 0.3. 2015-10-17 18:29:33 +01:00
test.sh Add syntax for extern routines, add syntax tests. 2015-10-17 13:50:21 +01:00

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.

Documentation

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

TODO

For 0.4:

  • while loops.
  • repeat loops.
  • explicitly-addressed memory locations

For 0.5:

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

For 0.6:

  • word type.
  • table type constructor and indirect addressing.