ppamltracer - a lightweight, portable tracing library

	Commit message (Collapse)	Author	Age
*	Version bump to 0.2.1	Benjamin Barenblat	2014-03-10
\|
*	Relicense under Modified (3-clause) BSD License	Benjamin Barenblat	2014-03-10
\|
*	Version bump to 0.2.0	Benjamin Barenblat	2014-03-04
\|
*	Python: Correct use of 'super'	Benjamin Barenblat	2014-02-06
\| \| \| \| \| \|	I invoked 'super' incorrectly throughout the error-handling code in ppamltracer-python; however, not testing those errors hid this issue until now.
*	Python: Make 'report_name_base' optional in calls to 'Tracer'	Benjamin Barenblat	2014-02-06
\|
*	Racket: Make 'report-name-base' optional in calls to 'call-with-tracer'	Benjamin Barenblat	2014-02-06
\|
*	Java: Add 'EnvironmentConfiguredTracer'	Benjamin Barenblat	2014-02-06
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Adding 'ppaml_tracer_init_from_env' (commit b9dfb8d0) makes the Java code substantially more complicated, as it introduces a second mechanism to construct 'Tracer's. While I could simply provide two constructors in the 'Tracer' class, this would make for an ugly and dangerous implementation; after all, the life cycle of a tracer configured explicitly is noticeably different from the life cycle of a tracer configured by sourcing environment variables. Instead, I’ve changed 'Tracer' to be an interface implemented by 'ExplicitlyConfiguredTracer' and 'EnvironmentConfiguredTracer'. This is an API-breaking change.
*	Haskell: Add 'withTracer''	Benjamin Barenblat	2014-01-27
\| \| \| \|	'withTracer'' wraps 'ppaml_tracer_init_from_env' in the C library.
*	Haskell: Fix documentation misspelling	Benjamin Barenblat	2014-01-27
\|
*	Initial commit	Benjamin Barenblat	2014-01-13