On 2017-09-08, Simon King <[email protected]> wrote:
> Hi Vincent,
>
> On 2017-09-08, Vincent Delecroix <[email protected]> wrote:
>> In the above code you are *not* calling the C API. Just avoid the
>> libgap_enter / libgap_exit.
>
> I know. But part of my question was whether it is safe to have
> python calls inside a libgap_enter/exit pair.
More concretely: From sage.libs.gap.element, I copied the following
function (that is not declared in libs/gap/element.pxd):
cdef inline GapElement_FiniteField make_GapElement_FiniteField(parent,
libGAP_Obj obj):
cdef GapElement_FiniteField r =
GapElement_FiniteField.__new__(GapElement_FiniteField)
r._initialize(parent, obj)
return r
The function is not a call to the C API either, but in my code I am
calling this function plus stuff like libGAP_ELM_PLIST and libGAP_EQ
in a tight loop. So, is it really needed that I enclose each individual
libGAP_* into a libgap_enter/exit pair? Thus, switching several times
between enter and exit in a tight loop?
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
