Content deleted Content added
Add more information about the new additions to the module |
|||
Line 2,216:
The <code>[[#detaching_substack|detaching_substack]]</code> modifier erases the current parameters from the parent stack, allowing the current stack to rename its parameters freely and merge them back to the parent stack, renamed.
It is possible to leave a substack without merging it to the parent by using the <code>[[#leaving_substack|leaving_substack]]</code> modifier. In this case, at some point it will be necessary to call <code>[[#flushing|flushing]]</code> in order to merge the stack previously left unmerged. Alternatively, it will be possible to enter it again by calling <code>[[#entering_substack|entering_substack]]</code>, and finally merge it via <code>[[#merging_substack|merging_substack]]</code>.
An example will probably clarify the mechanism better than anything else:
Line 2,232:
renaming_by_replacing|^.*$|This was called “%0”|1|<!-- Rename all parameters -->
merging_substack|
entering_substack|new|<!-- Enter into
pulling|1|<!-- Pull the parameter named “1” from the parent stack -->
mapping_by_replacing|^.*$|This value once was “one”|1|<!-- Replace the content of all parameters -->
merging_substack|
Line 2,252:
renaming_by_replacing|^.*$|This was called “%0”|1|<!-- Rename all parameters -->
merging_substack|
entering_substack|new|<!-- Enter into
pulling|1|<!-- Pull the parameter named “1” from the parent stack -->
mapping_by_replacing|^.*$|This value once was “one”|1|<!-- Replace the content of all parameters -->
merging_substack|
|