Markus Zolliker 1c33a41748 treat return value of write_<par> correctly ...

if the return value is 0 or "", and value is different from it,
then the behaviour is incorrect.
Alternative: we do not allow write_<par> to return None, and
check for it, or even validate the returned value.

Change-Id: If7381dd06f7c55bdc4a80981e67f831cd8ee4136
Reviewed-on: https://forge.frm2.tum.de/review/19728
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>

2019-01-11 15:06:41 +01:00

..

client

fix isort

2018-12-04 10:18:55 +01:00

gui

fix isort

2018-12-04 10:18:55 +01:00

lib

fix isort

2018-12-04 10:18:55 +01:00

protocol

added 'export_as' for parameters and commands

2018-12-20 16:42:35 +01:00

__init__.py

improve Py2/3 compat

2018-04-17 17:34:24 +02:00

datatypes.py

datatypes: require min, max ordering for size limits

2018-12-04 13:30:22 +01:00

errors.py

fix isort

2018-12-04 10:18:55 +01:00

features.py

fix isort

2018-12-04 10:18:55 +01:00

metaclass.py

treat return value of write_<par> correctly

2019-01-11 15:06:41 +01:00

modules.py

added 'export_as' for parameters and commands

2018-12-20 16:42:35 +01:00

params.py

added 'export_as' for parameters and commands

2018-12-20 16:42:35 +01:00

parse.py

fix isort

2018-12-04 10:18:55 +01:00

paths.py

fix isort

2018-12-04 10:18:55 +01:00

server.py

fix simulation

2018-12-04 14:03:53 +01:00

simulation.py

fix simulation

2018-12-04 14:03:53 +01:00

version.py

fix isort

2018-12-04 10:18:55 +01:00