Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "VIATRA/Query/UserDocumentation/PureWhitelist"
(Update to VIATRA Query 1.2) |
|||
Line 1: | Line 1: | ||
+ | {{caution|Old information|This page is not updated anymore; for more up-to-date details look at the query api documentation at https://www.eclipse.org/viatra/documentation/query-api.html instead.}} | ||
By default, check()/eval() constraints do not support calling arbitrary Java methods, since they are generally assumed to be impure. However, if you have a pure method and want to call it in these types of constraints, you have two options: | By default, check()/eval() constraints do not support calling arbitrary Java methods, since they are generally assumed to be impure. However, if you have a pure method and want to call it in these types of constraints, you have two options: | ||
* if it is implemented by you, annotate it with the <tt>@Pure</tt> annotation of Xbase (<tt>org.eclipse.xtext.xbase.lib.Pure</tt>) | * if it is implemented by you, annotate it with the <tt>@Pure</tt> annotation of Xbase (<tt>org.eclipse.xtext.xbase.lib.Pure</tt>) |
Revision as of 15:26, 14 November 2017
By default, check()/eval() constraints do not support calling arbitrary Java methods, since they are generally assumed to be impure. However, if you have a pure method and want to call it in these types of constraints, you have two options:
- if it is implemented by you, annotate it with the @Pure annotation of Xbase (org.eclipse.xtext.xbase.lib.Pure)
- if it comes from a third-party library, register it via the org.eclipse.viatra.query.patternlanguage.purewhitelist extension point
Some standard library methods are marked as pure by default, including:
- java.lang.Math
- java.lang.String