Tempfile-free evaluation by optparse.compose (fullly backward-compatible)
#27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ShamrockLee
changed the title
optparse.compose (fullly backward-compatible)
ShamrockLee
changed the title
optparse.compose (fullly backward-compatible)optparse.compose (fullly backward-compatible)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The previous API requires a temporary file to be created and sourced, which might be a problem in restricted environments where accessing to temporary directories are restricted or where file IO is relatively expensive. Besides, the temporary files are often left undeleted despite the
rmline being sourced.This PR proposes a way to print out the configuration headers through a new function
optparse.compose, which can be evaluated (eval "$(optparse.compose)") or sourced (. <<(optparse.compose)) in the user scripts to include the configurations without the need of temporary files.The changes are a backward-compatible, as
optparse.buildnow write to the temporary file the result ofoptparse.composeplus the lineremove $tempfile.This PR also include some house-keeping such as removing trailing white spaces and tabs from the generated result,
sample_head.shandREADME.md.