On 2018-09-30, Simon King <simon.k...@uni-jena.de> wrote: > D) libgap's and gap's methods should have roughly similar semantics
That said: Of course I see the point of designing the libgap interface in the way it was done: libgap(X), where X is something in Sage, should return something in libgap that corresponds to X (hence, if X is a string, it should return a libgap-string), whereas evaluation of commands should only happen when explicitly requested (i.e., when doing libgap.eval(X)). So, point D) of my wish list actually isn't really a wish. The differences however make porting my code from gap to libgap go beyond search-and-replace... -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
