Ichthyostega 9b8fae1a9b (re)consider the problem how to deal with mandatory/optional object fields ... this is a tricky problem and a tough decision. After quite some pondering I choose to enforce mandatory fields through the ctor, and not to allow myself cheating my way around it		2016-12-03 19:37:52 +01:00
..
backend
build	post-release: tighten library dependencies	2015-11-03 03:39:00 +01:00
code	refactoring(#988): switch function-closure to std::tuple	2016-01-19 03:56:53 +01:00
gui
howto	DOC: remove hotfix patch from backporting/Mint howto	2015-11-15 07:10:45 +01:00
infra	DOC: after release 0.pre.03 -- checklist with steps for release preparation	2015-11-20 06:12:59 +01:00
library	(re)consider the problem how to deal with mandatory/optional object fields	2016-12-03 19:37:52 +01:00
proc
DIR_INFO
index.txt
overview.txt