User talk:Ppaatt Lynagh

I tested Separate Words offline using LSLEditor 2.15 and got the results I documented.

I'm quite sure, the results you got are not intended by the author of the routine! I'll check that in-world next time I've access to.

Greetz Huney

---

Fascinating, thank you, I am much curious now.

Q1. Are the results I got not the results that everyone gets in world?? Do LSLEditor 2.15 and Second Life 2007-09-12 disagree?

A1a. I checked it in-world and yes, i got same results like you.

A1b. I checked again with LSLEditor and they really disagree on these results. And it's not the only difference. This term ie. worked correctly in LSLEditor:
float number;
string char = (string)(integer)float;

which didnt compile in-world and needed be changed to
float number;
string char = (string)((integer)float);

which in LSLEditor worked correctly, too.

Q2. Some of these strings are hard to copy/ paste accurately: all that punctuation gets garbled sometimes. If we consistenly get different counts of strings back, maybe we should try experimenting by writing code to count and print the strings of the spacers list and the separatorrs list?

A2. I compared the pasted strings and they were identical. You may try yourself. Here you can get LSLEditor: http://www.lsleditor.org/

Q3. Who is the author of the routine?

Me, Ppaatt Lynagh, I wrote the original separateWords routine of the Separate Words article myself.

Q4: What is the intent of the example?

The example I gave was the deeply geeky example of breaking LSL source into words. Words of source are not just the 0 to 16 alphanumeric words, but by intent do include the punctuation marks that appear in the 0 to 33 list. Code that runs afterwards has no hope of discarding the // commentary or reconstructing the "quoted strings" or interpreting \ escapes unless those punctuation marks appear in the output.

The example might not feel right until after you first meet an expression compiler like Chatbot, for which separateWords is just the first step, followed by assignValues, indexParameters, resultOf, etc.

Can we somehow keep this brief and illuminating example to teach new people by the sudden sharp pain of astonishment ... and yet also add English to reduce that pain?

-- most curiously yours, thanks in advance -- Ppaatt Lynagh 05:23, 13 September 2007 (PDT)

A4. I just formatted your article and executed the routine using LSLEditor (as I had no access in-world at the time I worked on Wiki) to get the sample results for use within the doc.

When I wrote my comment: "I'm quite sure, the results you got are not intended by the author of the routine!" I didnt know what exactly llParseString2List does. I simply *expected* the results I got from LSLEditor. Meanwhile I read the description and I know, the in-world results comply with that function's design. Sorry for the confusion I raised.

Meanwhile I learned, that the results from LSLEditor and in-world compiler may differ and I'll report that to LSLEditor's author.

I hope you nontheless enjoyed my reformatting of your article.

Greetz --Huney Jewell 07:51, 13 September 2007 (PDT)