Matthew Flatt 4807353e8d bytecode validator: check "constant" annotations on variable references ... Bytecode changes in two small ways to help the validator: * a cross-module variable reference preserves the compiler's annotation on whether the reference is constant, fixed, or other * lifted procedures now appear in the module body just before the definitions that use them, instead of at the beginning of the module body original commit: e59066debe		2012-10-19 11:27:52 -06:00
..
commands	raco exe: checks on source and destination paths	2012-05-28 20:30:58 -06:00
demodularizer	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00
bundle-dist.rkt	rename all files .ss -> .rkt	2010-04-27 16:50:15 -06:00
decompile.rkt	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00
embed-sig.rkt	rename all files .ss -> .rkt	2010-04-27 16:50:15 -06:00
sig.rkt	remove obsolete and unused Racket-to-C compiler	2011-09-20 15:26:39 -06:00
zo-marshal.rkt	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00
zo-parse.rkt	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00
zo-structs.rkt	bytecode validator: check "constant" annotations on variable references	2012-10-19 11:27:52 -06:00