User talk:Yosef Enoch

llGetObjectDesc

I saw your addition to llGetObjectDesc, but I'm not sure what you mean by it. Could you provide an example of this? Are you saying that:

<lsl>default{

   state_entry(){
       llSetObjectDesc("\n");
       llSleep(0.5);
       string v = llGetObjectDesc();
       llOwnerSay(llList2CSV([v == "\n", v == "\\n"]));
   }

}</lsl> Are you saying the above code will say:

• "Object: 0, 1"

I'm pretty sure it should be saying:

• "Object: 1, 0"

I can't get inworld right now to test this.

I think you have become a bit confused, escape characters are a feature of the compiler, not the runtime. The compiler is what translates escape codes in string constants in the source code. -- Strife ^{(talk|contribs)} 20:39, 17 July 2009 (UTC)

It looks like LSL can't handle comparisons within functions. It's not compiling with llOwnerSay(llList2CSV([v == "\n", v == "\\n"]);

Besides that, llSetObjectDesc("\n"); sets the objects desc to ?... Maybe 'cause it doesn't know how to handle a line break there... (o.O)

-- ^{(talk|contribs)} 22:00, 17 July 2009 (UTC)

P.S.: When you set the description manually to \n in the description field of the prim, then LSL will return "\\n" with llGetDesc(). Which is... somehow correct.

-- ^{(talk|contribs)} 22:04, 17 July 2009 (UTC)

Gives 0,0 -- ^{(talk|contribs)} 23:09, 17 July 2009 (UTC)

Not surprised, the description field isn't supposed to be multi-line. So does it just strip carriage returns or strip the next lines? <lsl>default{

   state_entry(){
       llSetObjectDesc("~\n~");
       llSleep(0.5);
       string v = llGetObjectDesc();
       llOwnerSay(llList2CSV([v == "~", v == "~~", v == "~?~", llStringToBase64(v)]));
   }

}</lsl> So what does it say? -- Strife ^{(talk|contribs)} 01:11, 19 July 2009 (UTC)

Object say: 0, 0, 1, fj9+

--Kuraiko Yoshikawa 14:27, 19 July 2009 (UTC)

No surprise, will document. -- Strife ^{(talk|contribs)} 21:12, 19 July 2009 (UTC)