Markus Armbruster 143a4e4e6f nsc: Rename nstr_exec_val() to nstr_eval() and tighten contract ... nstr_exec_val() can produce three different error values: NSC_NOTYPE on invalid category, invalid type with zero val_as.lng on invalid type (this is a bug), and the wanted type with zero val_s when it can't coerce. None of these should ever happen. Fix it to always produce an NSC_NOTYPE error value. Fix up callers to check for it. Specify the result's type is promoted on success. Ensure it is even when the argument is NSC_VAL with an unpromoted type, which is invalid. Signed-off-by: Markus Armbruster <armbru@pond.sub.org>		2015-02-01 16:52:59 +01:00
..
client	Update copyright notice	2014-01-02 14:33:48 +01:00
lib	nsc: Rename nstr_exec_val() to nstr_eval() and tighten contract	2015-02-01 16:52:59 +01:00
scripts	New make target check	2013-05-08 06:55:11 +02:00
server	Clean up superfluous includes	2014-02-16 13:19:26 +01:00
util	Update copyright notice	2014-01-02 14:33:48 +01:00