@ScriptLineNumber - Why - Not significant in compiled script

[mLipok]

when I read about @ScriptLineNumber in HELP then I see

Line number currently being executed. Useful for debug statements specially when a function is call you can pass the caller line number. (Not significant in compiled script)

Question: why ? Not significant in compiled script

[water]

Not very accurate: Comments and/or unused functions are removed while compiling so the line number isn't correct any more.

[mLipok]

OnAutoItExitRegister('EXIT_REG')
#include <Constants.au3>
#include <SendMessage.au3>
MsgBox(1,'TEST', @ScriptLineNumber )
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
Sleep(1)
MsgBox(1,'TEST', @ScriptLineNumber )
LOCAL $A
MsgBox(1,'TEST', $A[1])

Func EXIT_REG()
MsgBox(1,'TEST', '@ExitCode = ' & @ExitCode & @crlf & '@ExitMethod = ' & @ExitMethod)

EndFunc

FIRST:

I know there is a Error in MsgBox(1,'TEST', $A[1])

$A is not an array

but

try to compile this script

why error shows that message (Line 583)

Line 583 (File "L:TOOLsMacrotest_ScriptLineNumber.exe"):

Error: Subscript used with non-Array variable.

Is there any way to compile au3 script to exe and using autoitwrapper to create au3 output file which show me exactly what was in this line

Is exactly that same how in exe

ps.

this is not a try to decompile script

this is a trying to debug my own scripts which are very big and complicated, and used by diffrent users in many location

Edited May 7, 2013 by mlipok

[water]

This subject has been discussed a few times in the past. Compile your script with obfuscator settings set to /striponly and the obfuscated version of your script (in the script directory) will show the exact line where the error occurres.

[guinness]

You should also look at adopting other approaches of logging errors and not rely solely on @ScriptLineNumber to provide the answer. It's also a good learning curve of writing 'error free' code!

[mLipok]

Hello gentlemen.
I know that this topic has already been discussed (as indeed you said).
I know this thread is a little old.

but
It was my topic, and a lot has changed since then, for example, I mean Track Ticket #2524, and the resource of my knowledge.

I would, therefore, at the moment, ask a more specific question:

Example, the following script:
 

_TEST(@ScriptLineNumber)
Func _TEST($sLine)
    MsgBox(1,'$sLine = ', $sLine )
    ConsoleWrite('$sLine = '& $sLine & @CRLF)
EndFunc ;==>_TEST

and the question:

Why in the compiled version of the script, the message is given a value of -1 ?

---

You should also look at adopting other approaches of logging errors and not rely solely on @ScriptLineNumber to provide the answer. It's also a good learning curve of writing 'error free' code!

 

I think at the moment, you can trust me and believe in the word that in the field of testing, debugging, and analysis of the code, including unit tests, I have a lot of experience.

Described here is the problem with @ ScriptLineNumber I treat as a deepening of my knowledge, and add to the system debugging that I develop (at least in the privacy of my workshop).

But of course I'm going to share all the results of my work.

Edited November 20, 2013 by mlipok

[water]

The macro @ScriptLineNumber is not significant in a compiled script. Full stop.

AFAIK nothing has changed in the betas.

[mLipok]

Oh well, it's hard.

But everything is clear and thanks for the reply.

[water]

I know it would be nice to get a linenumber even from a compiled script.

But hey, there seem to be more important problems to solve and features to implement

[mLipok]

I know myself I submit problems to solve

[Gianni]

maybe >this can be of interest

[mLipok]

@PincoPanco

I use all this methode.

I even find an issue in Obfuscator and show how to fix them -  I mean Track Ticket #2524.

 

---

 

I see a summary of that discussion was the same as this.

 

The subject @ScriptLineNumber in compiled scripts has been discussed many times. The forums search feature is your friend 

 

But I came across an interesting statement.

Write a small script that reads each line and replaces @scriptlinenumber with the actual line number.

Won't work with the @scriptlinenumber default value for a parameter trick.

 

I think a little bit, a little Experiment, I think I can figure out a thing 

Thanks.

[Gianni]

Have you tried >this too?
It "retains" the line number of the script also when compiled

and displays the correct line number of the error in the executable.

 

[mLipok]

Finaly solved thanks to @Jos who realized my concept.

Here  you can read about, and below is a solution:

#AutoIt3Wrapper_Run_Au3Stripper=Y
#Au3Stripper_Parameters=/rsln

mLipok

Edited August 6, 2014 by mLipok