Justin Clark-Casey (justincc)
|
f94d07f2e2
|
Add regression test to check that specifying a non-existent event raise a syntax error
This was the case before any of the recent changes
|
2013-11-16 03:02:57 +00:00 |
|
Justin Clark-Casey (justincc)
|
79c1ed8cb9
|
Add syntax checking for no_sensor() no-arg event
|
2013-11-16 03:00:03 +00:00 |
|
Justin Clark-Casey (justincc)
|
ec4d96acc9
|
refactor common code out of no argument LSL event regression tests
|
2013-11-16 02:58:06 +00:00 |
|
Justin Clark-Casey (justincc)
|
edd7e19463
|
If anything other than a single integer is specified for events that only take a single integer, generate a syntax error on LSL script compile rather than an exception later on.
This applies to events changed, collision, collision_start, collision_end, on_rez, run_time_permissions, sensor, touch, touch_start, touch_end
|
2013-11-16 02:50:14 +00:00 |
|
Justin Clark-Casey (justincc)
|
62006baaef
|
Make state_exit, moving_end, moving_start, not_at_rot_target, not_at_target and timer LSL events generate a syntax error if inappropriately given arguments.
This matches behaviour seen on the LL grid and a previous change for state_entry.
These are all the events which should take no arguments
|
2013-11-16 01:30:23 +00:00 |
|
Justin Clark-Casey (justincc)
|
d728c1beb2
|
refactor LSL_EventTests.TestStateEntryEvent into single method to test compile
|
2013-11-16 01:25:25 +00:00 |
|
Justin Clark-Casey (justincc)
|
fd24147afa
|
Add initial test for checking that specifying a parameter in LSL state_entry() generates a syntax error.
Same for other events to follow at a later date.
|
2013-11-09 00:36:05 +00:00 |
|