Jeroen Demeyer on Wed, 05 Dec 2018 09:49:40 +0100


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Split up Section: programming/specific


For the Python bindings to PARI/GP, I need to decide which GP functions to interface and which not. I do this based on the information in pari.desc: I only consider "Class: basic" and I skip "Section: programming/control" because those don't make sense outside of GP. I obviously skip functions without a C-Name.

However, inside "Section: programming/specific" there are many functions that don't make sense ("quit", everything regarding scoping such as "localbitprec" and "exportall") but also functions which are useful ("setrand" for example).

It would be useful to split this section into "things specific to GP" and "general-purpose non-mathematical functions". What do you think?


Jeroen.