Re: Infix/postfix/nary redefinition issue (was loading to_poly_solve has side-effect).

--===============1531209428298126498==
Content-Type: multipart/alternative; boundary="00000000000010ac520657aa2785"

--00000000000010ac520657aa2785
Content-Type: text/plain; charset="UTF-8"

Great! Please share Claude's fix in whatever way is the most convenient for
you, and I will give it another review and integrate it.

serge de marre <[email protected]> schrieb am Di., 28. Juli 2026, 13:05:

> Hi all,
>
> Turns out the issue has nothing to do with to_poly_solve itself, but with
> operator (re)definitions.
> it's not just with nary, but also with prefix, postfix, infix, nofix and
> matchfix.
> I've added a bug entry in sourceforge ( Maxima -- GPL CAS based on
> DOE-MACSYMA / Bugs / #4883 Redefining an operator to be infix/postfix/nary
> causes a parser bug <https://sourceforge.net/p/maxima/bugs/4883/> ) ,
> with steps to reproduce.
> I've also attached a testcase to that sourceforge issue, a testcase that
> currently fails and that should pass (I think).
> I've used claude to assist with the investigation (and the writing of the
> test), and it suggested 2 fixes that I can provide (or I could create a
> pull request),
> The fixes make the provided testcase pass, as well as the 19700+ tests of
> the current run_testsuite(share_tests=true);
>
> serge
> _______________________________________________
> Maxima-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/maxima-discuss
>

--00000000000010ac520657aa2785
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Great! Please share Claude&#39;s fix in whatever way is t=
he most convenient for you, and I will give it another review and integrate=
 it.</div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"=
ltr" class=3D"gmail_attr">serge de marre &lt;<a href=3D"mailto:sdemarre@gma=
il.com">[email protected]</a>&gt; schrieb am Di., 28. Juli 2026, 13:05:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div id=3D"m_-6400024289752784147gmail-:2i6" aria-label=3D"Message Body" rol=
e=3D"textbox" aria-multiline=3D"true" style=3D"direction:ltr;min-height:85p=
x" aria-controls=3D":2kv" aria-expanded=3D"false"><div id=3D"m_-64000242897=
52784147gmail-:2i6" aria-label=3D"Message Body" role=3D"textbox" aria-multi=
line=3D"true" style=3D"direction:ltr;min-height:85px" aria-controls=3D":2kv=
" aria-expanded=3D"false">Hi all,<div><br></div><div>Turns out the issue ha=
s nothing to do with to_poly_solve itself, but with operator (re)definition=
s.</div><div>it&#39;s not just with nary, but also with prefix, postfix, in=
fix, nofix and matchfix.</div><div>I&#39;ve added a bug entry in sourceforg=
e (

<a href=3D"https://sourceforge.net/p/maxima/bugs/4883/" target=3D"_blank" r=
el=3D"noreferrer">Maxima -- GPL CAS based on DOE-MACSYMA / Bugs / #4883 Red=
efining an operator to be infix/postfix/nary causes a parser bug</a>=C2=A0)=
 , with steps to reproduce.</div><div>I&#39;ve also attached a testcase=C2=
=A0to that sourceforge issue, a testcase that currently fails and that shou=
ld pass (I think).</div><div>I&#39;ve used claude to assist with the invest=
igation (and the writing of the test), and it suggested 2 fixes that I can =
provide (or I could create a pull request),</div><div>The fixes make the pr=
ovided testcase pass, as well as the 19700+ tests of the current run_testsu=
ite(share_tests=3Dtrue);</div><div><br></div><div>serge</div></div></div></=
div>
_______________________________________________<br>
Maxima-discuss mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" r=
el=3D"noreferrer">[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/maxima-discuss" rel=
=3D"noreferrer noreferrer" target=3D"_blank">https://lists.sourceforge.net/=
lists/listinfo/maxima-discuss</a><br>
</blockquote></div>

--00000000000010ac520657aa2785--


--===============1531209428298126498==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1531209428298126498==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Maxima-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/maxima-discuss

--===============1531209428298126498==--