|Assertions [message #579604]
||Mon, 28 September 2009 12:15
| Henrik Lindberg
Registered: July 2009
Oisin started talking about debugging builds, and this triggered an
idea. Do you think it is valuable to be able to specify assertions?
I am thinking of something that can be executed before/after other
actions. This can be used to make sure the input is sane to an action,
that an action did produce something that is sane etc.
Imagine a build where some actions did produce a file, but it is empty.
It should really have produced serveral files. The build process will
not notice this, and eventually something really bad happens when trying
With assertions in place, they could issue warnings or errors, stop the
b3 could come with some standard assertion implementations - 'not
empty', '>= n files', '>= n bytes', 'list of files', 'permissions check'
- to name a few from the top of my head.
Do you think this is useful? If so, I will include this in the model.
Powered by FUDForum
. Page generated in 0.02015 seconds