Using @ScriptLineNumber for error checking

[Chimaera]

i understand this function is usefull for UN compiled scripts etc but

I can easily add [102] in the error to determine a location like

' Error Found ', ' Netstop1 Failed Execution [102]

but if im changing stuff and adding code this will soon become a train wreck

Is there a simple way to add the correct line number without having to go and re edit all error codes every time i change something?

And this is for a compiled script btw

 

[JohnOne]

@ScriptLineNumber will always be the ScriptLineNumber  however much code you add. It's the whole point.

Are you using it wrong?

Post example.

[AdmiralAlkex]

You can put @ScriptLineNumber as a default argument to the function that write the error log/text. Example:

_Error("Netstop1 Failed Execution")

_Error("cheese steak jimmy's")

Func _Error($sText, $iLine = @ScriptLineNumber)
    MsgBox(0, "Line number " & $iLine, $sText)
EndFunc

 

Edit:

@ScriptLineNumber won't work for compiled files, you will have to rethink that.

Edited August 16, 2015 by AdmiralAlkex

[Chimaera]

@ScriptLineNumber will always be the ScriptLineNumber  however much code you add. It's the whole point.

Are you using it wrong?

Post example.

It works for uncompiled

but on compiled it shows -1

I need it for Compiled

Im just trying to find a way of having scriptchange adjustable entries so when i change things therror location will be correct in the compiled version

 

Edited August 16, 2015 by Chimaera

[JohnOne]

There are tons of topics on this, and a wiki I believe.

[Chimaera]

hmm ive never seen one but ill go look

[AdmiralAlkex]

I think you'll have to write a pre-processor to run before compilation then to insert the numbers in the compiled script. Not sure there's any other way if you have to have compiled.

[Chimaera]

Yep so im seeing from the reading material

Thx all

Mind you im only interested where my line is in my script so i can still do them by hand...

which puts me within a couple of lines of the problem

Thing i dont get it this

Local $checkerror = @ScriptLineNumber
            Local $checkerror2 = $checkerror +2

you would think remembers the value as it is just a number but you cant get it to show outside when its compiled

 

Edited August 16, 2015 by Chimaera

[JohnOne]

Hard writing line numbers to script is not required.

Try top google searvh answer.

[Chimaera]

I had already looked at that but

I dont use Obfuscator anyway

And ive added

#AutoIt3Wrapper_Run_Au3Stripper=y
#Au3Stripper_Parameters=/mo

but it still returns -1 for this after compilation the [106] is the actuall

$hNotify = _Notify_Show(0, ' Error Found ', ' Netstop1 Failed Execution [106] ' & @ScriptLineNumber, 0, 1)

Just so we are clear on what im trying to achieve here

I dont really mind about knowing the line number from a 15000 compiled script

I only am bothered about what my line number is in my part of the script so i can goto my section and relook at the error for the Run or shellexecute etc that caused it

which is why im surprised that the number from this

Local $checkerror = @ScriptLineNumber
Local $checkerror2 = $checkerror

isnt remembered as a variable so i can pass it to the error report like this

$hNotify = _Notify_Show(0, ' Error Found ', ' Netstop1 Failed Execution [106] ' & $checkerror2, 0, 1)

Ive tried Int/Hex/Binary/Num and loads of other stuff but it cant remember it as a variable?

Edited August 16, 2015 by Chimaera

[jchd]

There is nothing surprising since it's documented behavior:

@ScriptLineNumber

Line number being executed - useful for debug statements (e.g. location of function call). Only significant in uncompiled scripts - note that #include files return their internal line numbering

[JohnOne]

You have to compare the compiled script error line number with outputted combined script.

[jchd]

The compiled script line number is always = -1

[AdmiralAlkex]

The compiled script line number is always = -1

Not when you crash, which seems to be what JohnOne is talking about, (but not what the OP is doing) which is admittedly a little strange. If the crash dialog know the line why can't @ScriptLineNumber?

[JohnOne]

Yes, I'm doing a lot of getting it wrong of late.

I've always been a lover of the idea of @funcname macro, but I suppose an implementation of that would similar be a -1 in compiled script.

[Chimaera]

which is admittedly a little strange.

Thats me all over

As much as i hate it, its not possible to have it work in the way my head tells me it should

Thats life, dont worry about it guys and thx

[jchd]

Admiral,

Yes I was talking about the macro, the heart of the topic. Note that once compiled, the macro would count lines in the run script, contrary to the macro in non-compiled context.

J1,

@FuncName would help in simple scripts, but @CallStack even more in complex ones, even if we get only function names and no copy of arguments passed.

[mLipok]

I had already looked at that but

I dont use Obfuscator anyway

And ive added

#AutoIt3Wrapper_Run_Au3Stripper=y
#Au3Stripper_Parameters=/mo

but it still returns -1 for this after compilation the [106] is the actuall

$hNotify = _Notify_Show(0, ' Error Found ', ' Netstop1 Failed Execution [106] ' & @ScriptLineNumber, 0, 1)

 

 

Try this:

#AutoIt3Wrapper_Run_Au3Stripper=y
#Au3Stripper_Parameters=/mo /rsln

 

 

[jguinch]

I don't know if I really understand the goal, but here could be a way :

 1/ Add the _MyDebug function (see below) to your code (at the end for example)
 2/ In SciTE, select the whole code, but not the MyDebug function
 3/ Go to Tools > Trace: Add Trace Lines
 4/ Go to Search > Replace (CTRL + H) : replace ConsoleWrite('>Error code by _MyDebug('>Error code

Now, you can compile your script and launch the compiled script with the /MyDebug parameter
 

_MyDebug() :

Func _MyDebug($sLine)
    Local Static $iDebugMode = -1
    If $iDebugMode = -1 Then
        If StringInStr($CmdLineRaw, "(?i)/MyDebug") Then
            _DebugSetup("MyDebug")
            $iDebug = 1
        Else
            $iDebugMode = 0
        EndIf
    EndIf

    If $iDebugMode Then
        _DebugOut($sLine)
    EndIf
EndFunc

It's just an idea, don't knock me !

[mLipok]

you should check if _DebugSetup was aleready called and so you can chceck if debug window is visible