Can Au3Stripper results be further optimized?

[qwert]

I’ve been using the Au3Stripper with great success. But as I bring individual scripts to completion, I’ve noticed what appears to be some excess baggage on board the produced sources. For example:

Global Const $__WINVER = __WINVER()

Func __WINVER()
Local $tOSVI = DllStructCreate($tagOSVERSIONINFO)
DllStructSetData($tOSVI, 1, DllStructGetSize($tOSVI))
Local $aRet = DllCall('kernel32.dll', 'bool', 'GetVersionExW', 'struct*', $tOSVI)
If @error Or Not $aRet[0] Then Return SetError(@error, @extended, 0)
Return BitOR(BitShift(DllStructGetData($tOSVI, 2), -8), DllStructGetData($tOSVI, 3))
EndFunc

.

An SciTE search of the resulting stripped source shows that $__WINVER isn’t referenced. And I’ve found several other constants that also aren’t referenced. For my finished “production” scripts, I’d like to remove every unused element.

 

So my question is this:

 

Is my best approach to just take the stripped version as a "pre-compile candidate”, then manually tweak it to the minimum—and then save it as my production source before a final compile?

 

Or, is there an easier way to reach the minimum code?

 

BTW, I intend to eventually replace constants with their literal values. But that step needs to be taken carefully ... and I don’t want to do it too soon.  That leaves UDFs and and Au3Stripper-determined "defaults" as the elements to focus on.

 

Thanks in advance for any help.

 

 

[BrewManNH]

You could always write your code so that there aren't any unreferenced variables yourself and not rely on someone else to fix your mistakes for you.

[Jos]

How would au3striper be able to determine that the execution of __winver() isn't essential dispite the fact that the receiving variable isn't used?

So i am only stripping variables that have a constant or literal sting on the right side of the =.

Jos

[qwert]

@Jos,

 

That helps. It explains sequences like this, where none of the six constants are referenced ... by my code or any called UDFs, that is:

 

Global Const $KF_EXTENDED = 0x0100
Global Const $KF_ALTDOWN = 0x2000
Global Const $KF_UP = 0x8000
Global Const $LLKHF_EXTENDED = BitShift($KF_EXTENDED, 8)
Global Const $LLKHF_ALTDOWN = BitShift($KF_ALTDOWN, 8)
Global Const $LLKHF_UP = BitShift($KF_UP, 8)

.

I’ll have to think about the __winver() case ... and also about BrewManNH’s comment. To me, this isn’t about mistakes and fixes, just optimization and how to reasonably achieve it.

 

Thanks for your response.

 

[Jos]

Understood your intentions and always appreciate when somebody puts ideas forward.

The thing to realize here is that i have to be very carefull not to break the script when stripping out functions or variables. Au3stripper is not aware of script logic so only checks for variables/functions being used. In your case the variable is filled with some sort of function for which au3stripper has to assume that function could be essential for the script to remain on the safeside.

I wouldn't worry too much about optimization as a few lines more or less will not matter that much in scriptsize.

Jos