Do not exit with an internal error when a badly typed input val is provided to lus2lic -exec.
Instead, print a warning and consider the input as unbound. Is it really the right thing to do?
Showing
- src/lv6version.ml 0 additions, 7 deletionssrc/lv6version.ml
- src/socExecEvalPredef.ml 38 additions, 2 deletionssrc/socExecEvalPredef.ml
- test/lus2lic.log.ref 303 additions, 301 deletionstest/lus2lic.log.ref
- test/lus2lic.sum 3 additions, 3 deletionstest/lus2lic.sum
- test/lus2lic.time 1 addition, 1 deletiontest/lus2lic.time
Loading
Please register or sign in to comment