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
The Gap class is the core wrapper class for accessing the GAP interpreter. Only one instance can be used at a time, for now, since only one GAP interpreter instance can exist in a single process. The default Gap instance gappy.gap is instantiated with some default parameters that will work in many cases. However, it's possible to instantiate one's own instance with different parameters by instantiating a Gap in the normal way. See 640dac6
As d66f403 points out, if a custom Gap is instantiated it's no longer possible to use the default gap.
I would prefer that Gap were a singleton, and that gappy.gap always points to the active instance. Calling Gap() will only update the initialization arguments in the case where the default instance has not already instantiated the GAP interpreter.
OTOH, maybe it should remain possible to have multiple simultaneous Gap instances, in case it's ever possible to have multiple GAP sub-interpreters. I don't know if/when that will ever be possible though.
The text was updated successfully, but these errors were encountered:
the Gap instance being called.
Until and unless there is a good solution to #5 this is necessary, so
that classes implementing _gap_ don't need to rely on the global
singleton.
The
Gap
class is the core wrapper class for accessing the GAP interpreter. Only one instance can be used at a time, for now, since only one GAP interpreter instance can exist in a single process. The defaultGap
instancegappy.gap
is instantiated with some default parameters that will work in many cases. However, it's possible to instantiate one's own instance with different parameters by instantiating aGap
in the normal way. See 640dac6As d66f403 points out, if a custom
Gap
is instantiated it's no longer possible to use the defaultgap
.I would prefer that
Gap
were a singleton, and thatgappy.gap
always points to the active instance. CallingGap()
will only update the initialization arguments in the case where the default instance has not already instantiated the GAP interpreter.OTOH, maybe it should remain possible to have multiple simultaneous
Gap
instances, in case it's ever possible to have multiple GAP sub-interpreters. I don't know if/when that will ever be possible though.The text was updated successfully, but these errors were encountered: