== Extending SCL environment ==

The SCL values, data types etc. that are available in expressions and commands are defined in SCL modules. Currently all SCL modules must be part of the product plugins (in the future, you can also write modules inside the models). Each module is identified by a URI.

SCL module is a text file ending with extension ".scl". The recommended place for modules is scl/ folder under plugin root, but also other directories can be used:

<b>scl/Test1.scl:</b>
<pre>
fib :: Integer -> Integer
fib x | x <= 1    = 1
      | otherwise = fib (x-1) + fib (x-2)
</pre>


A directory is declared as a SCL package with the following kind of extension points defined in org.simantics.scl.runtime:
<pre>
   <extension point="org.simantics.scl.runtime.package">
      <package URI="http://www.simantics.org/Tests"
               directory="scl"/>
   </extension> 
</pre>

The module is not automatically available in the console, but you must run an import declaration:
<pre>
> import "http://www.simantics.org/Tests/Test1" as Test1
> Test1.fib 13
377
</pre>

Import declaration can also be used in modules to refer other modules. Cyclic module dependencies are not allowed.

== Importing functionality from Java ==

Java interfaces and classes can be imported from Java by declaring them inside importJava block:
<pre>
importJava "java.util.regex.Pattern" where
    data Pattern

importJava "java.util.List" where
    data List a
</pre>

Java methods, constructors and fields can be similarly imported by giving
their type annotations in importJava block:
<pre>
importJava "java.util.regex.Pattern.compile" where
    @JavaName compile
    compilePattern :: String -> Pattern

    @JavaName matcher
    createMatcher :: Pattern -> String -> <Proc> Matcher

importJava "java.util.regex.Matcher" where
    data Matcher

    @JavaName matches
    matcherMatches :: Matcher -> <Proc> Boolean

matches : Pattern -> String -> <Proc> Boolean
matches pattern text = do
    matcherMatches (createMatcher pattern text)
</pre>

Another example:
<pre>
importJava "java.util.ArrayList" where
    @JavaName "<init>"
    createArrayList :: () -> <Proc> List a

    @JavaName "<init>"
    createArrayListWithCapacity :: Integer -> <Proc> List a

    @JavaName size
    sizeList :: List a -> <Proc> Integer

    @JavaName get
    getList :: List a -> Integer -> <Proc> a

    @JavaName set
    setList :: List a -> Integer -> a -> <Proc> ()

    @JavaName add
    addList :: List a -> a -> <Proc> Boolean
</pre>

Java constructor is referred with "<init>". If Java method name and SCL name matches the annotation @JavaName can be left out. Java import mechanism tries to be quite flexible. It provides some arguments based on the effects the function has. It also ignores the return value of the Java method if return type is () in SCL. 

A major functionality currently still missing is the ability to create new implementations of existing Java interfaces in SCL code or extend an existing class. This can be worked around currently by writing new implementations in Java.