You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens in a fresh 4.9.0 :-
gap> 1;2;3;[last,last2,last3];
1
2
3
[ 3, 2, 1 ]
gap> Error("to enter a break loop");
Error, to enter a break loop called from
not in any function at stdin:2
you can 'quit;' to quit to outer loop, or
you can 'return;' to continue
brk> 1;2;3;[last,last2,last3];
1
2
3
[ 3, 3, 2 ]
When I queried this on Slack, Chris Jefferson replied:
Short answer, no. Longer answer, the "bug" is we have a variable called LastDepth, which lets you pick how many of the last variables are changed. In this case we have set LastDepth=1, which means only last is getting updated. Why would we ever want to support that?
The simple fix (you could test it) is to change the 4th argument to SHELL in error.g:240 from '1' to '3'.
This change has been made; testinstall and teststandard pass; and a PR has been made.
The text was updated successfully, but these errors were encountered:
This happens in a fresh 4.9.0 :-
gap> 1;2;3;[last,last2,last3];
1
2
3
[ 3, 2, 1 ]
gap> Error("to enter a break loop");
Error, to enter a break loop called from
not in any function at stdin:2
you can 'quit;' to quit to outer loop, or
you can 'return;' to continue
brk> 1;2;3;[last,last2,last3];
1
2
3
[ 3, 3, 2 ]
When I queried this on Slack, Chris Jefferson replied:
Short answer, no. Longer answer, the "bug" is we have a variable called
LastDepth
, which lets you pick how many of the last variables are changed. In this case we have setLastDepth=1
, which means only last is getting updated. Why would we ever want to support that?The simple fix (you could test it) is to change the 4th argument to SHELL in error.g:240 from '1' to '3'.
This change has been made; testinstall and teststandard pass; and a PR has been made.
The text was updated successfully, but these errors were encountered: