|
Shaden Sura
Registered User
Join date: 10 Oct 2006
Posts: 68
|
10-17-2007 17:31
I a getting a error when I try to save the script any1 know about this ?
(216, 94) : ERROR : SYntax error
// This is the extended character.
Indices += llSubStringIndex(EXTENDED_INDEX, llGetSubString(Token, 0, 0)) + 95];
|
|
revochen Mayne
...says
Join date: 14 Nov 2006
Posts: 198
|
10-17-2007 17:36
Hi Shaden Try it without the ] after +95  |
|
Shaden Sura
Registered User
Join date: 10 Oct 2006
Posts: 68
|
10-17-2007 17:50
like this ?
Indices += llSubStringIndex(EXTENDED_INDEX, llGetSubString(Token, 0, 0)) + 95;
|
|
Shaden Sura
Registered User
Join date: 10 Oct 2006
Posts: 68
|
10-17-2007 18:03
woot it fix but know U have another error X3 w/
// XyText Message Map.
integer DISPLAY_STRING = 204000;
integer DISPLAY_EXTENDED = 204001;
integer REMAP_INDICES = 204002;
integer RESET_INDICES = 204003;
integer SET_CELL_INFO = 204004;
|
|
Stephen Zenith
Registered User
Join date: 15 May 2006
Posts: 1,029
|
10-18-2007 01:25
From: Shaden Sura woot it fix but know U have another error X3 w/
// XyText Message Map.
integer DISPLAY_STRING = 204000;
integer DISPLAY_EXTENDED = 204001;
integer REMAP_INDICES = 204002;
integer RESET_INDICES = 204003;
integer SET_CELL_INFO = 204004; What do the errors actually say? |
|
Krista Chaffe
Registered User
Join date: 16 Jun 2007
Posts: 96
|
10-18-2007 12:17
I had the same problem, particularly in LSE, compile results are different in world
I don't remember how I fixed it, what I did to debug was.
Removed large sections of the offending code until error went away. Then started adding back as parts worked.
What I do remember is that the error had nothing to do with the reported location. The compile was screwed up further up the file.
|
|
Jesse Barnett
500,000 scoville units
Join date: 21 May 2006
Posts: 4,160
|
10-18-2007 14:14
From: Krista Chaffe I had the same problem, particularly in LSE, compile results are different in world
I don't remember how I fixed it, what I did to debug was.
Removed large sections of the offending code until error went away. Then started adding back as parts worked.
What I do remember is that the error had nothing to do with the reported location. The compile was screwed up further up the file. You know that you can run lslint through LSLE now don't you? Even better, if you dbl click the error entry it will bring you up to the error and put your cursor on the exact part of the line.
_____________________
I (who is a she not a he) reserve the right to exercise selective comprehension of the OP's question at anytime. From: someone I am still around, just no longer here. See you across the aisle. Hope LL burns in hell for archiving this forum
|
|
Krista Chaffe
Registered User
Join date: 16 Jun 2007
Posts: 96
|
10-25-2007 12:12
Figured it out.
LSE doesn't compile exactly the same as the SL. That fails in Lse but compiles in SL
|