Originally posted by Edgewize
>>The ENV variable is going to be tougher than I expected,
>>The upshot is that you will not be limited to the digits $0-$9 for user-defined variable names
While I did suggest that the variables should not be restricted 0-9 previously, as a Quick and dirty the environment could be queried in the same way that the registry currently is (ie a command).
>>I found your post about positional vs named parameters, and I'll admit that I like the idea very much.
>>I very much doubt that Justin would re-integrate this back into the official NSIS :/ Maybe if I throw in some buzzwords like 'XML compliant parser' he'll like it.
I can't understand this as it does not change the size of the generated install code at all as the code you write is more usable and readable. The only "tricky" bit I can now think of (as I now guess that the parms are stored positionally internally) is the need for each command a ParmName->ParmPosn table and where this/these should be located.