|
|
#3 |
|
Major Dude
|
That's what StrFunc/UseFunc, and Instructor's header files do. The best of them would be UseFunc, because function calls and the functions themselves have less instructions than the others.
Just look at the call to StrCase now: code: This call is suitable for both installer and uninstaller. The echo line is optional. Or I could use your example function to create one with UseFunc. It would be built like this: code: I'm just not sure if the version and credits should be necessary. Those are only used when the internal echo message when a function is included, and to create new defines just for the version and the credits. You see there that the header has the prefix name for all its functions called "Cool". If you have a function called "Function", you would have the final function name as "CoolFunction". Also, the name of the function is used for all its posterior uses: there is no need to put it several times. You can also use the ${_Name} define for this. The function can be included the same way as you did with StrFunc. ${CoolFunction} outside functions and sections for function definition, ${CoolFunction} "Return_var" "Input_var" inside sections or functions. Any function definition is only added to the size of the installer if you call it first. I'll release it to public soon as it has a documentation. Last edited by deguix; 13th July 2005 at 15:45. |
|
|
|
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|