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
For example there may be cases, particularly if issue #68 is implemented (conditional compilation), where it is useful to set one macro value from another.
For example, say we have the macro
Include:data=info.dat
with contents
one=1
two=two
some-long-name=42
then we have to refer to some-long-name as data.some-long-name within the .vi file.
It may be clearer to use another variable for that name, such as answer. So having the set macro type would be useful:
set:answer=data.some-long-name
so that answer would now be set to 42, the value of data.some-long-name.
Whether the data should be copied or whether the new name is a simple alias needs some thought.
The text was updated successfully, but these errors were encountered:
For example there may be cases, particularly if issue #68 is implemented (conditional compilation), where it is useful to set one macro value from another.
For example, say we have the macro
with contents
then we have to refer to
some-long-name
asdata.some-long-name
within the .vi file.It may be clearer to use another variable for that name, such as
answer
. So having theset
macro type would be useful:so that
answer
would now be set to42
, the value ofdata.some-long-name
.Whether the data should be copied or whether the new name is a simple alias needs some thought.
The text was updated successfully, but these errors were encountered: