Change Log:
--------------------
version 1.2.8:
- probe APIVersion 100019 and 100020 (for next time)
version 1.2.7:
- probe APIVersion 100017 and 100018
version 1.2.6:
- probe APIVersion 100016 and 100017
version 1.2.5:
- Allow Lua compiler without version in its name.
- Added optional parameter -Compiler to specify the path to the Lua compiler, if in another location.
version 1.2.4:
- probe APIVersion 100015 and 100016
- added language jp
version 1.2.3:
- probe APIVersion 100014 and 100015
version 1.2.2:
- Probing APIVersion 100013 and 100014
- Language add: zh
version 1.2.1:
- Probing APIVersion 100013
version 1.2.0:
- Added language br
- Parse XML: Generate different code for GUI-XML and Key-Binding-XML. Add line numbers to generated source output.
- renamed the title for better description of what this script actually does.
version 1.1.0:
- Support substitute $(APIVersion)
version 1.0.0
- initial version
Description:
--------------------
This is NOT an addon
This is for addon developers
Description
This is a powershell script to check addon source for syntax errors and search for leaking global symbols. (Including a simple XML scan)
All credits for the idea go to @merlight. This is a portation* to Windows. *Perl is not mine and I don't want to install ActivePerl "just for that".
The main objective is finding variables going to global namespace unintended. This can cause strange side-effects and crashes. Hard to find, because one has to track down who conflicts with whom, first.
Global variables are slower than local variables. Finding unintended global variables may mean finding unexpected slow-downs, too. And finally: It happens really easy, even if you know about it and take care.
A secondary objective is a validation of the manifest file, the XML- and Lua files including localization files.
The script supports the subtitutes $(language) and $(APIVersion) and shows you wrong paths, normally silently ignored by ESO: You may think you have included a library and checked it more than once, until you realized that you have typed "lib" and not "libs".
By probing languages you normally do not select, the compiler will find missing quotes or commas for you.
All happend in addons already.
Setup
Before you can use the powershell script you need to download a Lua compiler for Windows. e.g. from here: http://sourceforge.net/projects/luabinaries/files/5.1.5/Tools%20Executables/
Select your CPU architecture (most likely x64 = lua-5.1.5_Win64_bin.zip). The CPU architecture of the ESO client does not matter, we want to check the addon source only.
Copy th...
--------------------
version 1.2.8:
- probe APIVersion 100019 and 100020 (for next time)
version 1.2.7:
- probe APIVersion 100017 and 100018
version 1.2.6:
- probe APIVersion 100016 and 100017
version 1.2.5:
- Allow Lua compiler without version in its name.
- Added optional parameter -Compiler to specify the path to the Lua compiler, if in another location.
version 1.2.4:
- probe APIVersion 100015 and 100016
- added language jp
version 1.2.3:
- probe APIVersion 100014 and 100015
version 1.2.2:
- Probing APIVersion 100013 and 100014
- Language add: zh
version 1.2.1:
- Probing APIVersion 100013
version 1.2.0:
- Added language br
- Parse XML: Generate different code for GUI-XML and Key-Binding-XML. Add line numbers to generated source output.
- renamed the title for better description of what this script actually does.
version 1.1.0:
- Support substitute $(APIVersion)
version 1.0.0
- initial version
Description:
--------------------
This is NOT an addon
This is for addon developers
Description
This is a powershell script to check addon source for syntax errors and search for leaking global symbols. (Including a simple XML scan)
All credits for the idea go to @merlight. This is a portation* to Windows. *Perl is not mine and I don't want to install ActivePerl "just for that".
The main objective is finding variables going to global namespace unintended. This can cause strange side-effects and crashes. Hard to find, because one has to track down who conflicts with whom, first.
Global variables are slower than local variables. Finding unintended global variables may mean finding unexpected slow-downs, too. And finally: It happens really easy, even if you know about it and take care.
A secondary objective is a validation of the manifest file, the XML- and Lua files including localization files.
The script supports the subtitutes $(language) and $(APIVersion) and shows you wrong paths, normally silently ignored by ESO: You may think you have included a library and checked it more than once, until you realized that you have typed "lib" and not "libs".
By probing languages you normally do not select, the compiler will find missing quotes or commas for you.
All happend in addons already.
Setup
Before you can use the powershell script you need to download a Lua compiler for Windows. e.g. from here: http://sourceforge.net/projects/luabinaries/files/5.1.5/Tools%20Executables/
Select your CPU architecture (most likely x64 = lua-5.1.5_Win64_bin.zip). The CPU architecture of the ESO client does not matter, we want to check the addon source only.
Copy th...