search

raysilent / lslforge

LSLForge - Eclipse plugin to assist with LSL scripting for Second Life. This repository is used for development, pull requests and bug reports.
16 stars 8 forks source link

Support OSSL (OpenSim) library #9

Open RayZopf opened 8 years ago

RayZopf commented 8 years ago

https://code.google.com/archive/p/lslforge/issues/56
Posted on Oct 9, 2014 by Quick Kangaroo OSSL is intended to be a superset of LSL, so should generally be simple to support without impact to the LSL support. In addition to the minor syntax difference (statements may not be parenthesized), I have several suggestions: 1. LSLForge obviously lacks templates for os* library functions. Rather than simply adding them to LSLForge, it might be a good idea to add a preference, possibly as a project parameter, pragma or file name pattern. 2. OSSL allows library functions to have multiple argument patterns. For instance, osTeleportAgent has three syntactically distinct forms (see http://opensimulator.org/wiki/OsTeleportAgent ) 3. it would be nice to have .osslp/.osslm/.ossl file extensions supported, both to distinguish them in your version control and deployment system and perhaps as a way to enable ossl extensions.

we could, of course, fork development to produce an osslforge, but it feels to me like a bad idea.

zauberparacelsus commented 8 years ago

I'd like to see this for the InWorldz functions too. Right now, I work around this by declaring dummy versions of the IWSL functions and constants in a special .lslp file, and then manually delete them when copying and pasting in the compiled file.

While it works, it's somewhat tedious, especially for some of my larger scripts that may be using at least 20-30 different IWSL functions.

EDIT: And yeah, forking seems like a bad idea to me as well.