How to get rid of "possibly used before declaration"

[c.haslam]

Unusually, I need code modelled on the following not to warn me "$L03P1: possibly used before declaration":

#include
local $t[3] = [1,2,3]
$s = "L03P1"
Assign($s,$t,2)
_arraydisplay($L03P1)

Is this possible? If so, how?

...chris

[kor]

certainly possible

just declare the variable

#include <Array.au3>
local $t[3] = [1,2,3], $s = "L03P1"
Assign($s,$t,2)
_arraydisplay($L03P1)

Edited August 4, 2012 by kor

[BrewManNH]

Try this, it's the only way I could find to disable the checking for variable declaration.

#AutoIt3Wrapper_Run_AU3Check=n ; <<<<<<<<<<<<<<
#include <Array.au3>
local $t[3] = [1,2,3], $s = "L03P1"
Assign($s,$t,2)
_arraydisplay($L03P1)

[c.haslam]

Thank you both.

Declaring the variable is probably not possible for what I am doing in my project. My script will be reading an Excel spreadsheet which will have 3 sheets: Main, Labo(u)r and Parts. Main is a list of various repairs. A repair may require one labo(u)r code or several; each repair may require no parts, or several parts. So the requirements are not exactly rectangular. The hierachy is Operation -> Labo(u)r -> Parts.

This would be easy in Python, but not in AutoIt!

The script is running now, with the data in a .au3 file (and the script in another). Each row of the Main 2-d array has an element which is the name of a Labo(u)r 2-d array. Each row in each Labo(u)r array has an element that is the name of a Parts 2-d array. I am probably breaking a rule of AutoIt, but the script does work, and has been working for a few years.

My interest in putting the data in Excel is for ease of update of data by the principal user, my son. He knows Excel, but is reticient to learn anything about AutoIt. The script automates, as far as possible, use of a manufactuer's web application.

[kor]

Try this, it's the only way I could find to disable the checking for variable declaration.

#AutoIt3Wrapper_Run_AU3Check=n ; <<<<<<<<<<<<<<
#include <Array.au3>
local $t[3] = [1,2,3], $s = "L03P1"
Assign($s,$t,2)
_arraydisplay($L03P1)

interesting. while not really related, do you know of a way to still check for declaration errors, but not have scite popup that annoying window? Edited August 4, 2012 by kor

[BrewManNH]

Here's another way I remembered about using #Forcedef

#forcedef $L03P1
#include <Array.au3>
local $t[3] = [1,2,3], $s = "L03P1"
Assign($s,$t,2)
_arraydisplay($L03P1)

[c.haslam]

I was looking for something to do what #forecdef does a few weeks back. Thank you for reminding me. Is it documented anywhere? I ask because there may be other # tidbits that would be useful.

[guinness]

#forceref and #forcedef should be using sparingly and only when you know what you're doing. This is one reason (probably) why it isn't documented. Those who need it will find out by digging around the forum.

[c.haslam]

Thank you for the advice. I will heed it!