Phoenix Zircon
Registered User
Join date: 6 Nov 2003
Posts: 67
|
12-05-2003 07:43
I hate em with such a huge passion. Would it be possible to get a Case/Select type of construct added to LSL? This would smooth over so many ugly code blocks it's ridiculous. My code gets chunky with listen msg calls and such and a streamlined construct like this would make the code oh so mych more readable and modifiable. Thanks
|
Julian Fate
80's Pop Star
Join date: 19 Oct 2003
Posts: 1,020
|
12-08-2003 16:33
I agree.
|
Nexus Nash
Undercover Linden
Join date: 18 Dec 2002
Posts: 1,084
|
12-08-2003 16:44
If's and ForS are gods tools! Cases are soo restrictive! But sure if it makes your live eaiser.
|
si Money
The nice demon.
Join date: 21 May 2003
Posts: 477
|
12-08-2003 16:52
From: someone Originally posted by Nexus Nash If's and ForS are gods tools! Cases are soo restrictive! But sure if it makes your live eaiser. What? Case is not restrictive at all. It just has a specific purpose, which if/elseif ad infinitum is a PITA for.
|
Eggy Lippmann
Wiktator
Join date: 1 May 2003
Posts: 7,939
|
12-09-2003 04:15
Yes please for the love of god and all thats good and holy get us a switch - case construct fast! And real arrays, with multidimensional abilities. I dont need them to be fancy polymorphic thingies, just plain old direct access arrays, as far as data structures go they are probably the most easy to use and fastest too.
|
Alondria LeFay
Registered User
Join date: 2 May 2003
Posts: 725
|
12-09-2003 06:06
Arrays! Arrays! Arrays!! Swicth would be nice too.
|
Bino Arbuckle
Registered User
Join date: 31 Dec 2002
Posts: 369
|
12-09-2003 11:14
Yes, A R R A Y S ! ! ! !
Or at least an llUpdateListAt(list src, integer index) call or something, so I don't have to futz around inserting and deleting and whatnot.
|
Ama Omega
Lost Wanderer
Join date: 11 Dec 2002
Posts: 1,770
|
12-09-2003 15:14
From: someone Or at least an llUpdateListAt(list src, integer index) call or something, so I don't have to futz around inserting and deleting and whatnot. Yea! Something like: llReplaceSubList(list dest, list src, integer index, integer size) dest : the array with data to be replaced src : the data being inserted index : where to start the replace size : the number of elements to replace. I place arrays as a higher priority than case statements, personally. Case statements can be worked around reasonably well with if else. Its not as pretty but works pretty straight forward. Lists are extremely different than arrays and lack a lot of functionality (multi-dimensions for example) that can't be easily worked around. Lists also have extra overhead (type data per element) that an array wouldn't need.
_____________________
-- 010000010110110101100001001000000100111101101101011001010110011101100001 --
|