Re: more m4p bugs

On Mon, May 19, 2025 at 01:35:53PM -0500, Eric Blake wrote:
> On Mon, May 19, 2025 at 02:05:28PM -0400, Nikolaos Chatzikonstantinou wrote:
> > On Mon, May 19, 2025, 1:27 PM Eric Blake <[email protected]> wrote:
> > 
> > > On Mon, May 19, 2025 at 10:46:10AM -0500, Eric Blake wrote:
> > > > 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):
> > > >
> > > > Now testing with b686ed, you have a problem with redefining a macro as
> > > > empty if it has been undefined in the meantime:

Another cute stack trace worth fixing:

$ echo 'eval(1,2,a)' | m4p
Traceback (most recent call last):
  File "/home/eblake/m4p/.venv/bin/m4p", line 8, in <module>
    sys.exit(main())
             ~~~~^^
...
  File "/home/eblake/m4p/m4p/parser.py", line 649, in call_builtin_aux
    return self.m4_eval(pathname, line, args)
           ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/home/eblake/m4p/m4p/parser.py", line 906, in m4_eval
    arg_width = int(arg_width)
ValueError: invalid literal for int() with base 10: b'a'

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org