SCL Tutorial - Revision history

Hannu Niemisto: /* Importing functionality from Java */

2016-11-22T15:21:52Z

Importing functionality from Java

← Older revision		Revision as of 15:21, 22 November 2016
Line 93:		Line 93:
	their type annotations in importJava block:		their type annotations in importJava block:
	<pre>		<pre>
	importJava "java.util.regex.Pattern~~.compile~~" where		importJava "java.util.regex.Pattern" where
	@JavaName compile		@JavaName compile
	compilePattern :: String -> Pattern		compilePattern :: String -> Pattern

Hannu Niemisto: /* Importing functionality from Java */

2012-09-24T11:48:50Z

Importing functionality from Java

← Older revision		Revision as of 11:48, 24 September 2012
Line 133:		Line 133:
	</pre>		</pre>

	Java constructor is referred with "<init>". If Java method name and SCL name matches the annotation @JavaName can be left out.		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.		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.

Hannu Niemisto: /* Importing functionality from Java */

2012-09-24T11:46:26Z

Importing functionality from Java

@@ Line 133: / Line 133: @@
 </pre>
-Names of classes and methods must be compile time constants. Also the type of the method must be completely defined, because SCL compiler cannot infer the type from the Java method. Java method signature is however checked to be compatible with SCL type. Overloaded methods are handled by filtering out those methods whose signatures do not match.
+Java constructor is referred with "<init>". If Java method name and SCL name matches the annotation @JavaName can be left out.
-The complete list of functions for accessing Java classes and interfaces is:
+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.

Hannu Niemisto: /* Importing functionality from Java */

2012-09-24T11:44:59Z

Importing functionality from Java

← Older revision		Revision as of 11:44, 24 September 2012
Line 81:		Line 81:
	== Importing functionality from Java ==		== Importing functionality from Java ==

	Java interfaces and classes can be imported to Java ~~with annotated data definitions~~:		Java interfaces and classes can be imported from Java by declaring them inside importJava block:
	<pre>		<pre>
	~~@JavaType~~ "java.util.regex.Pattern"		importJava "java.util.regex.Pattern" where
	data Pattern		data Pattern

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

	~~There are SCL macros for calling~~ constructors and ~~methods of the classes and~~		Java methods, constructors and fields can be similarly imported by giving
	~~accessing fields. These macros are defined~~ in ~~http~~:~~//www.simantics.org/Java.~~		their type annotations in importJava block:
	<pre>		<pre>
	~~import~~ "~~http://www~~.~~simantics~~.~~org/Java~~" ~~as Java~~		importJava "java.util.regex.Pattern.compile" where
			@JavaName compile
			compilePattern :: String -> Pattern

	~~compilePattern~~ : String -> ~~Pattern~~		@JavaName matcher
	~~compilePattern = Java.staticMethod "java.util.regex.Pattern.compile"~~		createMatcher :: Pattern -> String -> <Proc> Matcher

	~~@JavaType~~ "java.util.regex.Matcher"		importJava "java.util.regex.Matcher" where
	data ~~Pattern~~		data Matcher

	~~createMatcher~~: ~~Pattern~~ -> ~~String -~~> ~~Proc Matcher~~		@JavaName matches
	~~createMatcher = Java.methodProc "matcher"~~		matcherMatches :: Matcher -> <Proc> Boolean

	~~matcherMatches: Matcher -> Proc Boolean~~		matches : Pattern -> String -> <Proc> Boolean
	~~matcherMatches = Java.methodProc "matches"~~		matches pattern text = do
			matcherMatches (createMatcher pattern text)
	matches : Pattern -> String -> Boolean
	matches pattern text = ~~runProc~~ (createMatcher pattern text ~~>>= matcherMatches~~)
	</pre>		</pre>

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

	createArrayListWithCapacity : Integer -> Proc (List a)		@JavaName "<init>"
	~~createArrayListWithCapacity = Java.constructorProc "java.util.ArrayList"~~		createArrayListWithCapacity :: Integer -> <Proc> List a

	sizeList : List a -> Proc Integer		@JavaName size
	~~sizeList = Java.methodProc "size"~~		sizeList :: List a -> <Proc> Integer

	getList : List a -> Integer -> Proc a		@JavaName get
	~~getList = Java.methodProc "get"~~		getList :: List a -> Integer -> <Proc> a

	setList : List a -> Integer -> a -> Proc ()		@JavaName set
	~~setList = Java.methodProc "set"~~		setList :: List a -> Integer -> a -> <Proc> ()

	addList : List a -> a -> Proc Boolean		@JavaName add
	~~addList = Java.methodProc "add"~~		addList :: List a -> a -> <Proc> Boolean
	</pre>		</pre>

Tuukka Lehtonen at 19:42, 6 September 2012

2012-09-06T19:42:39Z

← Older revision		Revision as of 19:42, 6 September 2012
Line 1:		Line 1:
	[[Category: Simantics Constraint Language]]		[[Category: Simantics Constraint Language]]

	== Getting started ==		== Getting started ==

Tuukka Lehtonen at 19:42, 6 September 2012

2012-09-06T19:42:33Z

← Older revision		Revision as of 19:42, 6 September 2012
Line 1:		Line 1:
			[[Category: Simantics Constraint Language]]

	== Getting started ==		== Getting started ==

Hannu Niemisto: /* Getting started */

2012-08-25T07:54:45Z

Getting started

← Older revision		Revision as of 07:54, 25 August 2012
Line 38:		Line 38:
	</pre>		</pre>

	If you write a command that has side-effects~~. It~~ is executed in the console:		If you write a command that has side-effects, it is executed in the console:
	<pre>		<pre>
	> print "Hello" ; print "world!"		> print "Hello" ; print "world!"

Hannu Niemisto: /* Importing functionality from Java */

2012-08-24T13:48:24Z

Importing functionality from Java

← Older revision		Revision as of 13:48, 24 August 2012
Line 147:		Line 147:
	It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function		It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function
	<pre>runProc : Proc a -> a</pre>		<pre>runProc : Proc a -> a</pre>
	can be used to declare that the procedure actually is ~~reflectively~~ transparent. See above how it was used to defined matches function. It should be used sparingly in ordinary SCL code, because if it is used for a procedure that is not actually referentially transparent, strange behavior can occur when the compiler reorders or removes dead code.		can be used to declare that the procedure actually is referentially transparent. See above how it was used to defined matches function. It should be used sparingly in ordinary SCL code, because if it is used for a procedure that is not actually referentially transparent, strange behavior can occur when the compiler reorders or removes dead code.

	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 and creating them with constructor macro.		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 and creating them with constructor macro.

Hannu Niemisto: /* Importing functionality from Java */

2012-08-24T13:47:42Z

Importing functionality from Java

← Older revision		Revision as of 13:47, 24 August 2012
Line 143:		Line 143:
	Macro ''constructor'' expects the full class name as a parameter. Macros ''staticMethod'' and ''staticField'' expect the full method or field name including the full name of the class containing the method or field. Macros ''method'', ''field'' and ''setField'' expect only the name of the method or field without the containing class name.		Macro ''constructor'' expects the full class name as a parameter. Macros ''staticMethod'' and ''staticField'' expect the full method or field name including the full name of the class containing the method or field. Macros ''method'', ''field'' and ''setField'' expect only the name of the method or field without the containing class name.

	xxxProc-variants of the macros access Java methods that are not ~~reflectively~~ transparent (have side-effects). They expect Proc Something as a return type of the function. Note that although functions ''staticField'' and ''field'' only read a value of the field, they are not ~~reflectively~~ transparent if it is possible that the value of the field changes.		xxxProc-variants of the macros access Java methods that are not referentially transparent (have side-effects). They expect Proc Something as a return type of the function. Note that although functions ''staticField'' and ''field'' only read a value of the field, they are not referentially transparent if it is possible that the value of the field changes.

	It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function		It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function
	<pre>runProc : Proc a -> a</pre>		<pre>runProc : Proc a -> a</pre>
	can be used to declare that the procedure actually is reflectively transparent. See above how it was used to defined matches function. It should be used sparingly in ordinary SCL code, because if it is used for a procedure that is not actually ~~reflectively~~ transparent, strange behavior can occur when the compiler reorders or removes dead code.		can be used to declare that the procedure actually is reflectively transparent. See above how it was used to defined matches function. It should be used sparingly in ordinary SCL code, because if it is used for a procedure that is not actually referentially transparent, strange behavior can occur when the compiler reorders or removes dead code.

	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 and creating them with constructor macro.		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 and creating them with constructor macro.

Hannu Niemisto: /* Importing functionality from Java */

2012-08-24T13:44:19Z

Importing functionality from Java

← Older revision		Revision as of 13:44, 24 August 2012
Line 143:		Line 143:
	Macro ''constructor'' expects the full class name as a parameter. Macros ''staticMethod'' and ''staticField'' expect the full method or field name including the full name of the class containing the method or field. Macros ''method'', ''field'' and ''setField'' expect only the name of the method or field without the containing class name.		Macro ''constructor'' expects the full class name as a parameter. Macros ''staticMethod'' and ''staticField'' expect the full method or field name including the full name of the class containing the method or field. Macros ''method'', ''field'' and ''setField'' expect only the name of the method or field without the containing class name.

	xxxProc-variants of the macros access Java methods that are not reflectively transparent (have side-effects). They expect Proc Something as a return type of the function. Note that although functions ''staticField'' and ''field'' only read a value of the field, they are not reflectively transparent if it is possible that value of the field changes.		xxxProc-variants of the macros access Java methods that are not reflectively transparent (have side-effects). They expect Proc Something as a return type of the function. Note that although functions ''staticField'' and ''field'' only read a value of the field, they are not reflectively transparent if it is possible that the value of the field changes.

	It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function		It is common that Java methods that have side-effects can be combined so that resulting methods are side-effect free. SCL function