lslforge icon indicating copy to clipboard operation
lslforge copied to clipboard

Support OSSL (OpenSim) library

Open RayZopf opened this issue 8 years ago • 1 comments

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.

RayZopf avatar Feb 26 '16 14:02 RayZopf

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.

zauberparacelsus avatar Mar 09 '16 02:03 zauberparacelsus