llList2Vector, llList2Rot

I'm passing a list between scripts as a string. when I break the string back into a list with llParseString2List, I get 'bad' results from llList2Vector and llList2Rotation.
if element 0 contains a vector, llList2Vector(list, 0) returns <0, 0, 0>.
To get what I consider to be an appropriate result, I have to use: (vector)llList2String(list, 0)

Same with llList2Rot; I have to call it a string, then typecast it as a vector. Why doesn't llList2Rot/llList2Vector typecast it for me? llList2Integer and llList2Float seem to work this way.

It's fairly simple to work around, but the inconsistency is a minor annoyance.

:nod: I totally agree with yah; at the very least, the functionality of the llList2*() functions should be the same; either not bugged or all bugged

Im getting into the habit of simply using an llList2String() for all list extractions, and typcasting that. Ugly, but it's, at least IMO, better to keep things uniformly ugly (as in, I dont have llList2Float() or llList2Integer() instead of (float)llList2String() or (integer)llList2String(), when I *can* use them.)

Not needing to typcast with something as trivial as list element retrival would definately increase the readability of LSL code.

==Chris