EF Klaar
Registered User
Join date: 11 Jun 2007
Posts: 330
|
09-11-2009 03:10
As I understand it, LSL is the TLA for Linden Scripting Language, and LSO is the file-type extension for the result of a compilation of a script using the LSL compiler. My question is about the correct usage of terms when referring to scripts, the result of a compilation, the compiler itself and to the run-time interpreter, as well as the use of the plain language associated with these.
How should I refer to a script that has been compiled for/by/under LSL/LSO/Mono, and to a script that is running under/on LSL/LSO/Mono?
What does the "O" in LSO stand for?
And should "Mono" always be capitalised?
And I do know that it's improper to start a sentence with a conjunction. But sometimes I deliberately choose to do so.
|
Argent Stonecutter
Emergency Mustelid
Join date: 20 Sep 2005
Posts: 20,263
|
09-11-2009 03:15
Don't forget, sometimes the LSL byte code is referred to as "LSL2" just to add to the confusion.
|
Carbon Philter
Registered User
Join date: 4 Apr 2008
Posts: 165
|
09-11-2009 06:11
From: EF Klaar And I do know that it's improper to start a sentence with a conjunction. But sometimes I deliberately choose to do so.
Tsk tsk, EF. That's like ending a sentence with a proposition - improper grammar up with which I will not put!
|
Day Oh
Registered User
Join date: 3 Feb 2007
Posts: 1,257
|
09-11-2009 06:43
From: EF Klaar What does the "O" in LSO stand for? I always just assumed it meant opcodes... even though Linden Script Opcodes does sound funny
|
Argent Stonecutter
Emergency Mustelid
Join date: 20 Sep 2005
Posts: 20,263
|
09-11-2009 06:47
Object, I suspect. That's the traditional intermediate file name for compilers on UNIX, going back to the beginning. You had "foo.c" compiled to "foo.o", "foo.p" for the Berkeley Pascal compiler compiled to "foo.po", and so on. Comes from DEC operating system's ".obj" files combined with the fact that Ritchie was typing on an ASR33 teletype so wanted to make names as short as possible. If you've ever used a teletype you'll understand why.
|
EF Klaar
Registered User
Join date: 11 Jun 2007
Posts: 330
|
09-11-2009 07:08
From: Carbon Philter Tsk tsk, EF. That's like ending a sentence with a proposition - improper grammar up with which I will not put! And that's one of the many sayings Winston will be rightly remembered by. From: Day Oh Linden Script Opcodes does sound funny Which could explain why everyone keeps quiet about it. From: Argent Stonecutter sometimes the LSL byte code is referred to as "LSL2" Eek! The term "byte code", which I'd forgetten, will, however, almost certainly, prove useful, in the future. Sorry. Pub lunches, you know.
|
EF Klaar
Registered User
Join date: 11 Jun 2007
Posts: 330
|
09-11-2009 07:19
From: Argent Stonecutter foo I've never learned how that came to be used as a generalisation in programming examples, and I would dearly love to. From: Argent Stonecutter If you've ever used a teletype you'll understand why. I guess I'd be showing my age if I mentioned punched tape and editing code using sticky splices, though I can offer the excuse that my school was never furnished with the most up-to-date equipment.
|
Argent Stonecutter
Emergency Mustelid
Join date: 20 Sep 2005
Posts: 20,263
|
09-11-2009 08:01
From: EF Klaar I've never learned how that came to be used as a generalisation in programming examples, and I would dearly love to. More than you ever wanted to know about foo: http://www.catb.org/jargon/html/F/foo.html#
|
Winter Ventura
Eclectic Randomness
Join date: 18 Jul 2006
Posts: 2,579
|
09-11-2009 08:18
"foo" is what pre-algebra called "n"
_____________________
 ● Inworld Store: http://slurl.eclectic-randomness.com ● Website: http://www.eclectic-randomness.com ● Twitter: @WinterVentura
|