UseFunc header

Author: deguix (talk, contrib)

Links

Download link:
usefunc.zip (21 KB)

Forum thread (where anything directly about this contribution should always be posted)

Description

Version: 1.0.

UseFunc is a header file wrapping macro-functions into more compact code. Some other features are:

• It uses the same call for both installer and uninstaller. You can change it though, just read the documentation.
• Version specification for every function and header. This adds better compatibility with older function and header versions. Logically, you need some extra code to compare versions...
• Lists of functions and headers that use UseFunc in compile-time.
• Comes with a complete Array header, and the Str header with one function (these are called example headers). The Array header is different from Afrow UK's, because it uses the Math plug-in. (1st contribution using Math plugin, at last!)
• Basic internal error handling for the Array header.

Documentation is included for the UseFunc and the headers. I didn't test every single feature that I put, so if you find any bugs and suggestions, you're welcome to report them to me.

How to use

1. Extract the files in the .zip file into the NSIS folder, all files should go to their respective folders automatically.
2. Put the line !include "UseFunc.nsh" in your script.
3. Define which functions you want to use after the !include "UseFunc.nsh" line. Like: ${StrCase}.
4. Use the function macro in your script.

Versions History

1.0 - 10/Aug/2005

• First version.

Credits

• UseFunc header macro-function wrapper created by deguix.

License

Copyright © 2005 Diego Pedroso

This header file is provided 'as-is', without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this header file.

Permission is granted to anyone to use this header file for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this header file must not be misrepresented; you must not claim that you wrote the original header file. If you use this header file in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered versions must be plainly marked as such, and must not be misrepresented as being the original header file.
3. This notice may not be removed or altered from any distribution.