|
|
|
|
#1 |
|
Junior Member
Join Date: May 2003
Posts: 19
|
I realize that you want to use labels because it is more resilient to modifications in the code, but this macro cannot be used in certain situations because of the uniqueness (or lack of) of the keys.
For instance: !insertmacro KeyExists A_ROOT A_MAINKEY A_KEY ; Do something like ExecWait that should modify the key ... ; And this will have duplicate labels... !insertmacro KeyExists A_ROOT A_MAINKEY A_KEY I agree with using labels in the name of maintainability, but not at the expense of the efficacy of the macro. If I use the above, I have to remember that it won't work if I use it twice in the same function for the same key. For a small macro like this one, doesn't it make more sense to relax the 'rule' for the benefit of the functionality? |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|