improve documentation of evalstr_ex
, evalstr
#898
Merged
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.
evalstr_ex
(addresses DocumentGAP.evalstr_ex
? #894)evalstr
(adresses Change documentation to warn against usingGAP.evalstr
#897)Changing
evalstr
such that GAP's screen output is shown in the Julia session seems to be not possible if the libgap functionGAP_EvalString
is used. The return value contains strings that describe the screen output plus the return value of each command, and separating the screen output from the string that represents the return value is in general not possible. Note that the pointers to the return values are not useful here because the objects may have changed since they got created, as in the following example.In the case of functions that have a return value and cause some printing to the screen, we cannot decide which part of the 5th entry in each entry of the result of
evalstr_ex
belongs to the return value.(Perhaps libgap's
GAP_EvalString
should be changed accordingly. The fourth position in the entries of the result is currently unused.)