in general, do not use a known Name
value in PrintObj
#5701
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses #5699.
For more than 25 years, there is a
PrintObj
method with high rank that just prints a knownName
value of the object in question.According to the documentation of
Name
, a knownName
value should be used only byView
andViewObj
; the functionPrint
is recommended to show GAP input to reconstruct the object in question if this makes sense.When we remove the
PrintObj
method in question, the tests fromtestinstall
andteststandard
show differences essentially in two situations:Rationals
are currently expected to be printed via this name. The solution proposed here is to provide aPrintObj
method with high rank that uses a known name under the condition that a global variable with this name exists.SimpleGroupsIterator
callPrint
in order to show the names of these groups. Here we can callView
instead ofPrint
.(Let us see the results of the other tests, perhaps there are more differences.)