LSL Write Once Debug Everywhere
LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Why Debug Everywhere
Los scripts LSL que escribes una vez pueden corren en varias plataformas.
Por consiguiente, copiar tu script LSL de un lugar a otro puede causar que falle o que no compile.
Entre los lugares que puedes correr tus scripts LSL incluyen Linux, Mac OS X y clientes de Windowsde SecondLife.com que conectan atraves de una conexion de banda ancha de Internet a la red central en Linden labs. También existen otros compiladores y otras redes como compilar, editar y probar procesos fuera de línea.
Este artículo explica como puedes desarollar scripts LSL que corren bien y compila sin errores en todos estas plataformas.
Works at my Desk
Ways in which your script can run fine at your desk while choking at mine include the following.
Astonishing Compile-Time Error Messages
The LSLEditorBugs article explains how a bug in an LSL compiler can make your script fail to compile in one place despite compiling and running well in.
The LSL_Errors article explains how one LSL compiler reporting "ERROR : Syntax error" can mean what another LSL compiler would describe as "ERROR : Byte code assembly failed -- out of memory". Naturally, different LSL compilers provide different efficiencies. For example, the 2007-08 Mac OS X Second Life client could compile 692 cascaded else-if's at a time when the Windows Second Life client could not compile 19 cascaded else-if's.
Astonishingly different clients
El artículo LSL Alternate Editors enumera otros lugares en tu sistema operativo donde puedes tratar de correr tu LSL además de el cliente que SecondLife.com provee libre de costo.
Running Alternative Operating Systems
Running another operating system to test your script may be easier or harder than you think.
Techniques that can let you restart your PC or Mac to run an alternate operating system include:
- Inserting a DVD or CD disc
- Plugging in a USB Flash Drive (UFD)
- Repartitioning your internal ATA hard drive (without scrambling it)
- Adding an external FireWire hard drive
Which technique works best for you varies according to your setup, in particular your boot BIOS.
Which technique works best for you will also vary bizarrely in accord with the copy restrictions added for you by the operating system vendor. For example, Microsoft Windows will often refuse to run from anywhere except from a partition of your internal ATA hard drive.
The http://www.apple.com/macosx/bootcamp/ tool from Apple walks you thru the process of repartitioning your internal ATA hard drive without scrambling it, but only if you have an Intel-based Mac, not a Motorola-based Mac and not an Intel-based PC.
Companies like http://www.parallels.com/ and http://www.vmware.com/ sell you tools for running Windows in parallel with your usual operating system. You can even run Windows in parallel with itself, just to test different configurations without disrupting your normal Windows experience.
Running Linux
Linux demands skill & attention to run well enough to support Second Life.
As yet, Linux demands too much skill & attention: we haven't yet found a "how to" guide to tell us how people who don't already run OpenGL 2.0 in Linux can rapidly learn to run Second Life in Linux.
Techniques we've tried that don't let us run Second Life in Linux include:
- Linux CD-R Ubuntu Feisty 7.04 - ACPI vs. recent Apple hardware
- Linux CD-R Knoppix 2007-01-04 - "Window creation error"
- Linux DVD-R Knoppix 2007-01-04 - "Window creation error"
Searching the web finds a Linux CD-R Knoppix for Second Life, but only a version that requires NVIDIA graphics without supporting the ATI Radeon graphics often found in Mac's.
Running Mac OS X
Mac OS X just works, if you have a Mac.
Mac OS X doesn't work at all if you don't have a Mac.
Running Windows
Windows demands skill & attention to run well enough to support Second Life.
The Windows installer's claim that you need administrator privilege to install appears to be false. People have seen copies of "C:\Program Files\SecondLife\" mostly work when dragged to into the "%userProfile%\Downloads\" of other Windows machines, without administrator privilege.
Also see
Also see: LSL Alternate Editors, LSLEditorBugs