 UbitUmarov
|
8f1a68633e
update lsl2c tools and parsing files. This may fix some issues with precendence of unary operators in same case, hope not break on others :(
|
6 years ago |
 Melanie Thielker
|
b16abc8166
Massive tab and trailing space cleanup
|
7 years ago |
 Justin Clark-Casey (justincc)
|
cbd428cff3
Add LSL transaction_result event.
|
9 years ago |
|
Justin Clark-Casey (justincc)
|
2f94165dcc
Add lsl arg syntax checking for control event
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
f1cd813a29
refactor: rename internal lsl parser VectorDeclaration -> VecDeclaration for consistency
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
871ac5b16c
Add arg checking for at_target lsl event
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
a5e4780547
Add lsl event arg checking for at_rot_target
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
b757ab2586
Add lsl event argument checking for attach and on_rez
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
a64377149d
Add parameter checking for land_collision, land_collision_start and land_collision_end lsl events
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
79c1ed8cb9
Add syntax checking for no_sensor() no-arg event
|
10 years ago |
|
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.
|
10 years ago |
|
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.
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
2b069a3b1e
If the LSL state_entry() event definition contains any parameters, then generate syntax error as seen on the LL grid
|
10 years ago |
|
Justin Clark-Casey (justincc)
|
daad0a3e11
Revert "Bind ~ and ! operators in LSL tighter in order to resolve issues in LSL where these aren't evaluated propertly."
|
12 years ago |
|
Justin Clark-Casey (justincc)
|
a8a9d13dc0
Bind ~ and ! operators in LSL tighter in order to resolve issues in LSL where these aren't evaluated propertly.
|
12 years ago |
 Mike Mazur
|
48bc2f3a42
Allow empty assignment in for-loop
|
15 years ago |
|
Melanie Thielker
|
fb3d5770dd
Make the LSL HTTP server create and give out URLs to scripts
|
15 years ago |
 Homer Horwitz
|
7083be07b0
Allow empty statements in LSL (; followed by ;). Fixes Mantis#2320
|
15 years ago |
|
Melanie Thielker
|
d95794d05c
Refactor XEngine parser as per suggestions from mikem
|
16 years ago |
|
Melanie Thielker
|
a5d2674a43
This is an attempt to fix the handling of constants in LSL.
|
16 years ago |
|
Mike Mazur
|
16cf5aa2b8
Allow the list hack from issue 1863 to compile, however its behavior is
|
16 years ago |
|
Mike Mazur
|
56c4cc39ff
Allow assignments in if/while/do-while control statements. Fix issue 1862.
|
16 years ago |
|
Mike Mazur
|
eef3864278
Fix issue 1860; exception thrown in the parser on if/if-else/for/while/do-while
|
16 years ago |
 Charles Krinke
|
476e08286e
Mantis#1728. Thank you kindly, Mikem for a patch that solves:
|
16 years ago |
 Johan Berntsson
|
130d8047a2
Thanks Mike for another LSL compiler patch which fixes a bug where 'vector v=<0, 0, -0.5>' caused a syntax error, and implements multiple assignments in one line (x = y = 3;)
|
16 years ago |
|
Johan Berntsson
|
a73e3b4e3f
another patch from Mike: the llscript compiler is now available in XEngine as well. Thanks Mike
|
16 years ago |
