strip comments. the wiki is the documentation
terrorize README and remove invalid tests.
I'll rewrite these in a better format with examples.
automate error collection for assertions and expectations
split apron into modules
Leave 'apron' as sourceable toplevel file.
Allow user setup/teardown functions
add note about currently known limitations
capture the return value from a replayed function
actually return correctly from APRON_replay as per the doc
add support for expectations
redirect functions registered as mocks
Calling 'APRON_register rm' will define a function called 'mock_rm' with
the same function body and unset the original 'rm'.
make mock registration fatal
This shouldn't ever happen since the mocks are defined by the calling
test framework. Failure should only occur when the function doesn't
exist, in which case it's an application error we don't want to try to
cleanup some dross from initial churn
add some survival tactics
use a single var to maintain state
Create a poor man's enum to describe the current state of Apron.
README: fix typos