Tree @0.2 (Download .tar.gz)
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.2. It is a complete reboot of SixtyPical 0.1. The reference implementation is written in Python instead of Haskell. The language is much simpler — we're going to try to get the analysis completely right before adding more sophisticated and useful features in future versions.
Documentation
- Design Goals — coming soon.
- SixtyPical specification
- Literate test suite for SixtyPical execution
- Literate test suite for SixtyPical analysis
- 6502 Opcodes used/not used in SixtyPical
TODO
For 0.3:
- extern routines.
- generate 6502 code (either Ophis assembler or machine code
PRG
files.) while
loops.- a little demo that actually compiles and runs on a C64 emulator.
For 0.4 and/or beyond:
- explicitly-addressed memory locations
repeat
loops.- add line number (or at least routine name) to error messages.
- hexadecimal literals.
word
type.table
type constructor and indirect addressing.if not
.- 6502-mnemonic aliases (
sec
,clc
) - other handy aliases (
eq
forz
, etc.)
Commit History
@0.2
git clone https://git.catseye.tc/SixtyPical/
- Prep for release of version 0.2. Chris Pressey 8 years ago
- Improve evaluator internals. Finish test suite for analysis. Chris Pressey 8 years ago
- Fix up spec, split off to 6502 opcodes doc, add some tests. Chris Pressey 8 years ago
- Update spec. Chris Pressey 8 years ago
- Work on the spec a bit. Chris Pressey 8 years ago
- Write sufficient tests (I think) for analysis of `if`s. Chris Pressey 8 years ago
- Allow `if` analysis to pass (needs more tests.) Better styling. Chris Pressey 8 years ago
- Fix links in README. Implement Context.clone(). Chris Pressey 8 years ago
- Refactor to replace some sketchy code with code actually in use. Chris Pressey 8 years ago
- Add TODO to README, update license information. Chris Pressey 8 years ago