ScriptLineNumber During Execution

[IAMK]

I was playing around with AutoIT and ran into the following issue of @ScriptLineNumber not working in .exe form. It is only to be used during debugging, so is there any way I can achieve the same effect in .exe form?

I have the following scripts:
Included file:

Func CHECK_InArrayScope($arraySize, $elementPosition, $errorFrom = "Unspecified.") ;This requires the array's size to be passed, not the actual array.
   If($arraySize < 1) Then
      MsgBox(0, "ERROR: Empty Array.", "The array you tried to access is empty!" & @CRLF & @CRLF & "Terminating script! Please update the script before running it again!" & @CRLF & @CRLF & "Source: " & $errorFrom)
      Exit 0
   ElseIf($arraySize < $elementPosition) Then
      MsgBox(0, "ERROR: Out of array scope.", "The array is too small and doesn't contain the element you tried to access!" & @CRLF & @CRLF & "Terminating script! Please update the script before running it again!" & @CRLF & @CRLF & "Source: " & $errorFrom)
      Exit 0
   EndIf
EndFunc

Script:

Local $myArray[2] = ["NULL", "HI"]

#include "OtherFile.au3"

CHECK_InArrayScope(UBound($myArray) - 1, 2, String(@ScriptName & " <Line " & @ScriptLineNumber & ">"))

 

[BrewManNH]

First, if you're using it in debugging, you don't need to compile it until it's working correctly. Second, you can parse the script for any instances of @ScriptLineNumber and convert them to the actual line number, then compile it if you insist on keeping debugging code in production exes.

Something as simple as this would work as well.

#include <File.au3>
$sScriptIn = "My_FileNameHere.au3"
$aFileRead = FileReadToArray($sScriptIn)
$LineCount = @extended
For $I = 0 To $LineCount - 1
    $aFileRead[$I] = StringReplace($aFileRead[$I], "@scriptlinenumber", " '" & $I + 1 & "' ")
Next
_FileWriteFromArray($sScriptIn, $aFileRead)
_ArrayDisplay($aFileRead)

 

[IAMK]

 @BrewManNH Well, the main reason I am playing around with error handling is for 2 reasons:
1- I can't actually test my scripts on my computer. They need to be run on our product with the .exe.
2- It's mostly for other people who try to update my scripts for their own projects (each project is slightly different, but the same tasks get done). I want to give them plain English explanations in places I think errors mostly occur, because trying to debug what happens when a co-worker tells me "it stopped working" is a pain...

I think running a script to change the text would confuse them, and it would never get run, even if I made it hardcode the line numbers, compile, then change back to @ScriptLineNumber in the script and save. I already have enough problems with people not downloading the #included files and asking me why the script won't work.

A simpler approach I can do may be to give each call a unique ID. E.g. FunctionName_1, FunctionName_2, etc...

Or... Is there a way for something like your solution, but in the compiler? It doesn't change the .au3 itself, but upon compilation, it replaces @ScriptLineNumber with a hardcoded line number?

 

[BrewManNH]

If you have downloaded the Scite4AutoIt package, you can use the directive #AutoIt3Wrapper_Run_Before to run the parsing script first, have it make the changes needed, then compile that script, that results from the parsing.

Of course, all of this could be avoided by not letting others muck around with your scripts. If they can't even be trusted to download the necessary files to run the script in the first place, should they really be expected to understand whatever else would be needed?

I think using the _Debug* functions in the Debug.au3 UDF might be of some help in this. Perhaps _DebugReportVar, with a hard coded line number or identifying text reference, would be sufficient. Have it output to a text file.

Unfortunately, anything else won't really work in a compiled script due to the loss of line numbering.

[mLipok]

@IAMK

Did you try to use:

#AutoIt3Wrapper_Run_Au3Stripper=Y
#AutoIt3Wrapper_Au3stripper_Stop_OnError=Y
#Au3Stripper_Parameters=/MO /RSLN

?

[IAMK]

@BrewManNH Thanks, I will do that.

@mLipok No, I have never used wrappers. I'll look into using some from now on. Thanks.

[IAMK]

If I use #include or #AutoIt3Wrapper_Run_Before, is there a way for me to get the name of the file/script which used the include/wrapper?

When I use a function call, I can simply pass the name as a variable, but no function calls are made when using include/wrapper.