For the record, using the libgap Python interface (i.e. from sage.libs.gap.libgap import libgap) automatically takes care of the libgap_enter/exit business. This is only an issue if you want to the libGAP C API directly, which is what Simon is presumably asking.
On Thursday, September 7, 2017 at 4:01:47 PM UTC+2, Dima Pasechnik wrote: > > Hi Simon, > > I don't think anything special like libgap_enter/exit is needed when > calling libgap.* stuff from > Python or Cython. > We do quite a few libgap calls in graphs/strongly_regular_db.pyx > and in graphs/generators/classical_geometries.py > so this all seems to work just fine. > > Do you mean something else? > Dima > > On Thursday, September 7, 2017 at 1:30:29 PM UTC+1, Simon King wrote: >> >> My questions are about how/when to use libgap_enter/exit >> when calling a libGAP_* function. >> >> First question: What should happen if one doesn't use >> libgap_enter/exit? I ask since I called libGAP_EQ without >> libgap_enter/exit, but there is no crash and it just works. >> So, can one do without it, in some cases? >> >> Second question: What should one do if one has a loop >> containing both several python and libGAP_* calls? Put >> libgap_enter/exit around each individual libGAP_* call? >> Or is it possible to have Python calls (and a whole >> "for" loop) between enter and exit? >> >> Best regards, >> Simon >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
