Developer's notes

You are probably here because you want to hack the source.

Source Organization

The top directory contains mainly build-support files. Source code is organized as follows:

config: autotools support files, generated by bootstrap, autoconf-m4 macros
libltdl: GNU Libtool libltdl
dox: documentation root (mostly texinfo to pdf, html, info)
- mk: Makefile templates and LaTeX build support
- man: UNIX man pages (empty)
- ... more ...
lib: HAC library files, CHP library files, application support
src: source root
- lexer:
- parser:
- util: project-independent C++ library (data-structures, interface-wrappers, etc.)
  - STL: C++ STL extensions, forward declaration, additional support
  - memory: memory-management libraries and templates
  - numeric: typed numeric, low-level, bitwise operations
  - test: regression tests
  - graph: graph algorithms and structures
- AST: syntax-tree classes
- Object: object-file and middle-end
  - common:
  - def: definitions, unique footprints, template parameters
  - expr: expressions compile-time, run-time
  - inst: instance collections
  - type: type objects
  - ref: instance- and value-reference objects
  - lang: language blocks
  - traits: meta-class traits
  - unroll: expansion phase
- sim: simulators
- net: netlist tools
- guile: Guile extension plug-in primitives code
- scm: Guile scheme code
- common:
- main: top-level programs
test: regression test suite root
- lexer: lexer-focused tests
- parser: parser and front-end focused tests
- prsim: hacprsim tests
- chpsim: hacchpsim tests
- guile: hacguile tests
- net: hacknet tests

Major development plans are listed here. There are many, honest.