On Mon, Oct 1, 2018 at 8:58 AM Simon King wrote:
>
> Hi Dima,
>
> On 2018-09-30, Dima Pasechnik wrote:
> > it was written before optional parameters era in GAP, as far as I know.
> > Anyhow, you can use GAP's PushOptions() and PopOptions() to achieve more or
> > less
> > the same effect, with a
Hi Dima,
On 2018-09-30, Dima Pasechnik wrote:
> it was written before optional parameters era in GAP, as far as I know.
> Anyhow, you can use GAP's PushOptions() and PopOptions() to achieve more or
> less
> the same effect, with a big uglier syntax.
"Uglier" only internally. I think it shouldn'
Hi Simon,
On Sun, Sep 30, 2018 at 11:01 AM Simon King wrote:
> On 2018-09-30, Dima Pasechnik wrote:
> > if you have a nontrivial GAP computation to be done in libgap, why not just
> > use libgap's function_factory?
> > Then you don't need to jump various hoops across sage/libgap boundary.
>
> If
Hi Dima,
On 2018-09-30, Dima Pasechnik wrote:
> if you have a nontrivial GAP computation to be done in libgap, why not just
> use libgap's function_factory?
> Then you don't need to jump various hoops across sage/libgap boundary.
If I understand correctly, the function_factory allows to create a
On Sun, 30 Sep 2018, 10:10 Simon King, wrote:
> Hi Vincent,
>
> On 2018-09-30, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> > The main problem is that G is a gap group and not a libgap
> > group. By gap group I mean that the interface going through
> > the pexpect interface. The two sys
On 2018-09-30, Simon King 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 (h
Hi Vincent,
On 2018-09-30, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> The main problem is that G is a gap group and not a libgap
> group. By gap group I mean that the interface going through
> the pexpect interface. The two systems gap and libgap do not
> seem to share the namespaces (
Dear Simon,
The main problem is that G is a gap group and not a libgap
group. By gap group I mean that the interface going through
the pexpect interface. The two systems gap and libgap do not
seem to share the namespaces (which make sense).
For example, this does work
sage: gap(g1)
f1
but
Here is another question on libgap: Let some libgap elements be given;
how to form the list of these elements in libgap? The purpose would, for
example, be to create a group from that list.
For instance:
sage: G = gap.SmallGroup(48,36)
sage: g1,g2,g3,g4,g5 = G.GeneratorsOfGroup()
Since G
