Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling GapObj on Tuples yields Arrays #596

Closed
SyxP opened this issue Dec 23, 2020 · 3 comments
Closed

Calling GapObj on Tuples yields Arrays #596

SyxP opened this issue Dec 23, 2020 · 3 comments

Comments

@SyxP
Copy link

SyxP commented Dec 23, 2020

See attached code.

julia> GAP.evalstr("(1,2,3)")
GAP: (1,2,3)

julia> GapObj((1,2,3))
GAP: [ 1, 2, 3 ]
@fingolfin
Copy link
Member

There are no tuples in GAP.

Your first input returns a GAP permutation.

Your second input returns a GAP list (roughly corresponds to a Julia Vector/Array).

@fingolfin
Copy link
Member

I don't see an issue here, so I am going to close this. But feel free to provide additional information, then we can reopen.

@SyxP
Copy link
Author

SyxP commented Dec 23, 2020

Ah the difficulty I faced was that when I tried to replicate the GAP code Group((1,2,3)), I tried GAP.Globals.Group(GapObj((1,2,3))) which didn't work, but required GAP.Globals.Group(Gap.evalstr("(1,2,3)"), perhaps not a bug but perhaps should be at least noted somewhere. I think this is likely the first things people might try.

ThomasBreuer added a commit to ThomasBreuer/GAP.jl that referenced this issue Jan 6, 2021
The right way to do this is to check the return value of `evalstr_ex`,
and to call `GAP.error_handler` if necessary,
as was proposed in the discussion of gap-system/gap/issues/4199.

This is intended to resolve issue oscar-system#580.

(The change does of course not affect the problems described in
issue oscar-system#596.)
ThomasBreuer added a commit that referenced this issue Jan 7, 2021
The right way to do this is to check the return value of `evalstr_ex`,
and to call `GAP.error_handler` if necessary,
as was proposed in the discussion of gap-system/gap/issues/4199.

This is intended to resolve issue #580.

(The change does of course not affect the problems described in
issue #596.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants