Re: more m4p bugs

On Fri, May 16, 2025 at 10:05=E2=80=AFAM Eric Blake <[email protected]> wro=
te:
>
> 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):
> >
>
> * At the command line, m4 treats -d as taking an optional argument
> (POSIX discourages that practice, but m4 was doing it long before
> POSIX, and since -d is a POSIX extension, it's better to keep status
> quo).  I don't know how easy or hard it is to make a short option take
> an optional argument with python's argument parsing libraries; and I
> also know you are still fine-tuning how debugmode() and --debug
> behave:

Yes, I'm aware of that one. There's certain discrepancies between
argparse and what m4 does. For now I'll try to use argparse and live
with the differences, but if I manage to get everything else to be
100% compatible I will revisit this issue, perhaps write my own argv
parser.

> * Commit 45fdad3 broke reading large files:
> $ seq 2000 > list
> $ git checkout 45fdad3^
> $ echo 'len(include(list))' | m4p
> 8893
> $ git checkout 45fdad3^
> $ echo 'len(include(list))' | m4p
> 8196

Oops! Thank you, I fixed it and added a test for that as well.

Regards,
Nikolaos Chatzikonstantinou