Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Script Error : Local List: null , Function Args: i OR isks ?!

Salvador Nakamura
http://www.sl-index.com
Join date: 16 Jan 2007
Posts: 557
08-17-2007 06:52
Hello all,

After making the classical error of rewriting a large script without compiling it a few times, i am now left with this repeated error:

local list: null
function args: null
localist: null
function args: i
localist: null
function args: null
localist: null
function args: isks

i spend some hours checking the code, tried googling the error, but no succes..

anybody know what might cause this error !?
RJ Source
Green Sky Labs
Join date: 10 Jan 2007
Posts: 272
08-17-2007 07:03
I believe this is a symptom of the too-many-ifs problem.
If so, the error messages won't make sense, and the only way to get around them is to fiddle with the code.

If you have a large section with a bunch of if else-ifs, and maybe some more nesting under that, try experimenting in that area (I.e., moving the else sections around, especially moving the section where your error occurs further up in the else-if structure).
Salvador Nakamura
http://www.sl-index.com
Join date: 16 Jan 2007
Posts: 557
08-17-2007 07:20
TY RJ , that could make sense, i do have a lot of if/else's.. will try

*sadly the "error cursor" is at line 1, so that does not seem to be of any help.
Salvador Nakamura
http://www.sl-index.com
Join date: 16 Jan 2007
Posts: 557
08-17-2007 07:53
i have cleaned some if/else statements , and changed some to "else if" , no luck sofar.

*whenever i delete the contents of a state (any state) it will compile and save ?!
Shadow Subagja
Registered User
Join date: 29 Apr 2007
Posts: 354
08-17-2007 10:09
can you post the code, or at least a skeleton example of it that still produces the error?
Tiarnalalon Sismondi
Registered User
Join date: 1 Jun 2006
Posts: 402
08-17-2007 10:40
From what it sounds....the script is just too long. I've had a problem before were I got a wierd error and if I deleted a few lines it would compile fine...didn't matter what lines (as long as the code itself was still ok that is).

I would look to see if you can optimize some parts of it to use less lines of code, or if not, then you might need to make some part of it another script.

I could be wrong, however, as the errors from LSL are not always very informative. I would try seeing if the above is a feasible work around and see if it compiles after you do a test.
RJ Source
Green Sky Labs
Join date: 10 Jan 2007
Posts: 272
08-17-2007 10:55
I've seen these errors go away when 1) when I delete enough stuff from the script, or 2) rearrange and lessen the else-if nesting. But once I fix 2), then all the stuff I took out in 1) seems to be ok in the script again.

The way I finally tracked it down to a 'fix' was making a copy of the script with the error. Then delete one of the else if lines. If it compiles, put that else back but closer to the top of the group, and your done (for today). If it does not compile, delete another if, and continue, until you find the one that fixes (and I use that term loosely) it.
Salvador Nakamura
http://www.sl-index.com
Join date: 16 Jan 2007
Posts: 557
08-18-2007 14:15
i did not have much if/else that where not needed, i managed to tweak a few, but had no result, then i blended 2 states using switches thus more if's again, still no go, but it shortend my script by 20 lines orso, then i placed a income sharing routine in a function, clearing another 10 lines, AND YAY it worked again :D

i can not be fully sure, but i think the sollution was clearing a total of 50 lines from the script, which brought the total back to 550 (with //debug and blank lines)

(?¿)

*Thanx for all the help !
Core Taurog
Registered User
Join date: 2 May 2007
Posts: 17
08-21-2007 14:21
This is the shortest bit of code I've managed to make to reproduce your problem (well you can take the touch_start out too, but it's less obvious why you couldn't see the real error message :p ):

CODE

integer x;
list i = [x];

default
{
state_entry()
{
}
touch_start(integer i)
{
}
}


You get two of the helpfull lines going on about "null", and then the somewhat more useful line:
(1,11) : ERROR: uninitialised variables can't be included in lists

Given the length of your code, my guess is you got spammed with the helpfull "null" stuff, and the uninitialised variable thing got lost somewhere, or just cut off altogether.

I've had it a few times, and knew it was something to do with lists; I did manage to crash the editor a few times before figuring out exactly what it was :p

regards,

Core