
| Key: |
SVC-2929
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Cannot Reproduce
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Brandon Shinobu
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
I've been experiencing a lack of compile errors where there ought to be – more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
I strongly suspect there are more errors, as I didn't extensively test every error I could possibly make, however this is a serious issue. I'm surprised no one seems to have noticed it before now.
|
|
Description
|
I've been experiencing a lack of compile errors where there ought to be – more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
I strongly suspect there are more errors, as I didn't extensively test every error I could possibly make, however this is a serious issue. I'm surprised no one seems to have noticed it before now. |
Show » |
Brandon Shinobu made changes - 27/Aug/08 01:44 PM
| Field |
Original Value |
New Value |
|
Description
|
I've also been experiencing a lack of compile errors where there ought to be -- more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
|
I've been experiencing a lack of compile errors where there ought to be -- more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
|
Brandon Shinobu made changes - 27/Aug/08 01:45 PM
|
Description
|
I've been experiencing a lack of compile errors where there ought to be -- more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
|
I've been experiencing a lack of compile errors where there ought to be -- more specifically, errors which ARE caught by the current compiler in the release version of SL. I found these errors in the BETA viewer (Second Life 1.21.0 (94415) Aug 14 2008 15:18:57 (Second Life Beta))
The compiler failed to give an error in the following cases:
global variables without type in the declaration: test = "try";
global variables without type in the declaration OR a semicolon after declaration: test = "try"
global variables without a semicolon after declaration: string test = "try"
global variables without type, or semicolon, being = to another undeclared variable, without a semicolon in the declaration: test = try
global variables with the value ahead of the variable (total nonesense, but I tried it anyway): "try" = test
global variables ending in a parenthesis instead of a semicolon: test = "try")
Extraneous parenthesis and bracket's/bracers after a semi-colon in a statement in the body of the script: SetAction();}
All three at once: SetAction();})]
I strongly suspect there are more errors, as I didn't extensively test every error I could possibly make, however this is a serious issue. I'm surprised no one seems to have noticed it before now.
|
made changes - 27/Aug/08 02:25 PM
|
Link
|
|
This issue Relates to SVC-1276
[ SVC-1276
]
|
made changes - 28/Aug/08 03:00 PM
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Cannot Reproduce
[ 5
]
|
made changes - 28/Aug/08 03:16 PM
|
Link
|
This issue Relates to SVC-1276
[ SVC-1276
]
|
|
made changes - 28/Aug/08 03:17 PM
|
Link
|
|
This issue is related to by SVC-1276
[ SVC-1276
]
|
made changes - 13/Nov/08 12:11 PM
|
Workflow
|
jira-2007-12-22a
[ 58500
]
|
jira-2008-11-14
[ 82602
]
|
made changes - 13/Nov/08 04:46 PM
|
Workflow
|
jira-2008-11-14
[ 82602
]
|
jira-2008-11-14a
[ 92227
]
|
|
I cannot reproduce this. The errors you mention give syntax errors when compilation is attempted.
Note – my guess is you were actually not in a Mono enabled region. Mono regions say 1.24... when you check Help / About Second Life. The 1.23 regions are not compatible with the new viewers.
Behavior with 1.21 viewer:
1.24 region, Mono compile - gives syntax errors as it should
1.24 region, LSL2 compile - gives syntax errors
1.23 region, LSL2 compile - NO ERRORS
The 1.24 server will be everywhere on 29 August, so the incompatibility with old 1.23 regions isn't considered an issue.