1 ## Importing functionality from Java
\r
3 Java interfaces and classes can be imported from Java by declaring them inside `importJava` block:
\r
6 importJava "java.util.regex.Pattern" where
\r
9 importJava "java.util.List" where
\r
13 Java methods, constructors and fields can be similarly imported by giving
\r
14 their type annotations in `importJava` block:
\r
17 importJava "java.util.regex.Pattern.compile" where
\r
19 compilePattern :: String -> Pattern
\r
22 createMatcher :: Pattern -> String -> <Proc> Matcher
\r
24 importJava "java.util.regex.Matcher" where
\r
28 matcherMatches :: Matcher -> <Proc> Boolean
\r
30 matches : Pattern -> String -> <Proc> Boolean
\r
31 matches pattern text = do
\r
32 matcherMatches (createMatcher pattern text)
\r
38 importJava "java.util.ArrayList" where
\r
40 createArrayList :: () -> <Proc> List a
\r
43 createArrayListWithCapacity :: Integer -> <Proc> List a
\r
46 sizeList :: List a -> <Proc> Integer
\r
49 getList :: List a -> Integer -> <Proc> a
\r
52 setList :: List a -> Integer -> a -> <Proc> ()
\r
55 addList :: List a -> a -> <Proc> Boolean
\r
58 Java constructor is referred with `"<init>"`. If Java method name and SCL name matches the annotation `@JavaName`
\r
59 can be left out. Java import mechanism tries to be quite flexible. It provides some arguments based on the effects
\r
60 the function has. It also ignores the return value of the Java method if the return type is `()` in SCL.
\r
62 A major functionality currently still missing is the ability to create new implementations of existing Java interfaces
\r
63 in SCL code or extend an existing class. This can be worked around currently by writing new implementations in Java.
\r
65 ## Relational sublanguage
\r
67 * Select, when, enforce
\r
70 ## Other language features
\r
72 * Defining data types
\r
73 * Defining type classes
\r
75 * Restricted imports
\r
76 * Documentation strings
\r
77 * Private definitions
\r
78 * Binary operator precedence
\r