Simplify and document explicit state updater code a bit more. Raise a
SyntaxError instead of ValueError with the appropriate informations to
get a nice display of the error message.
Be more precise about symbols in the state updater description and
symbols in the equation itself -- should fix problems with using
variable names such as x, f, or g. Closes #24.
Avoid adding the values of all Value specifiers to the namespace at each
timestep. Solution is still a bit hacky, ideally a template object would
inform code generation that it needs the "_spikes" attribute, for
example.
Merge remote-tracking branch 'origin/integration_cleanup'
Increase the perfomance of the unitless state variable lookup in Group
Update the is_active state variable in abstract code, not in the
pre_update method.
Update the refractory_until state variable in the threshold template,
not in the post_update method.
Merge branch 'master' into devices