On Tuesday, 21 September 2021 at 15:08:44 UTC-7 vdelecroix wrote:
> We could add a sophisticated argument parser in cpyari2 but it is a lot
> of trouble and time penalty at execution.
>
> The only reasonable move that I see is to discuss with pari devs.
>
Yes, I don't think we're willing to inc
As far as cypari2 is concerned, qfminim is auto-generated from
the data pari provides (the pari.desc file, gp help, etc).
Forcing lower case in all situations is a huge backward incompatible
change. I see many D, G, V which are commonly used as upper case
letters in math for discriminant, group a
On Monday, 20 September 2021 at 12:58:10 UTC-7 jus...@mac.com wrote:
> I’m not sure this is relevant to your issue, but FWIW, I tried in recent
> versions of Pari, and noticed two things:
> - “?qfminim" documents the use of ‘b’ as the second argument, while
> "??qfminim" documents the use of ‘B
I’m not sure this is relevant to your issue, but FWIW, I tried in recent
versions of Pari, and noticed two things:
- “?qfminim" documents the use of ‘b’ as the second argument, while "??qfminim"
documents the use of ‘B’.
- using the forms “b=“ and “B=“ in the calls with a second argument makes no
I noticed that in pari.qfminim; from 9.3 to 9.4 there was a trivial change:
the second parameter changed name from 'b' to 'B'. This breaks code that
calls it with 'b' as a keyword. I had trouble tracing this change, but it
looks like this is in some automatically generated interface.
It's gene
