On Fri, May 16, 2025 at 08:16:24AM -0500, Eric Blake wrote: > Since you continue to patch things as fast as I report them (now > testing with commit a4cc0f3c): >
* RBASE in m4_eval.py is too restrictive (only noticible for bases > 16): $ m4p eval(0r36:10) 36 eval(0r36:a) 10 eval(0r36:z) m4:stdin:3: bad expression in eval: 0r36:z That last line should have been 35. * m4 currently warns about whitespace to incr and decr, and rejects trailing whitespace (unlike eval). It also diagnoses bad input when producing no output: $ m4 incr(1 ) m4:stdin:1: non-numeric argument to builtin `incr' incr(+ + 1) m4:stdin:2: non-numeric argument to builtin `incr' incr(` 1') m4:stdin:3: leading whitespace ignored in builtin `incr' 2 $ m4p incr(1 ) 2 incr(+ + 1) incr(` 1') 2 -- Eric Blake, Principal Software Engineer Red Hat, Inc. Virtualization: qemu.org | libguestfs.org
