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>
This commit is contained in:
parent
5a1544f925
commit
143a4e4e6f
6 changed files with 29 additions and 20 deletions
|
@ -112,7 +112,7 @@ xdeval(struct valstr *val, struct xdstr *xd,
|
|||
struct castr *ca, void *ptr, int idx)
|
||||
{
|
||||
nstr_mksymval(val, ca, idx);
|
||||
return nstr_exec_val(val, xd->cnum, ptr, NSC_NOTYPE);
|
||||
return nstr_eval(val, xd->cnum, ptr, NSC_NOTYPE);
|
||||
}
|
||||
|
||||
/*
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue