-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IOclHelper should evaluate OclExpressions (pre-parsed) #11
Comments
By Christian Damus on Dec 22, 2005 09:46 Committed the fix, adding variants of the evaluate() and check() methods |
By Nick Boldt on Jan 28, 2008 16:34 Move to verified as per bug 206558. |
By Ed Willink on May 27, 2011 02:40 Closing after over a year in verified state. |
By Ed Willink on May 27, 2011 02:41 Closing after over a year in verified state. |
This was referenced Sep 19, 2024
Closed
This was referenced Sep 21, 2024
Closed
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
| --- | --- |
| Bugzilla Link | 114921 |
| Status | CLOSED FIXED |
| Importance | P3 enhancement |
| Reported | Nov 03, 2005 10:20 EDT |
| Modified | May 27, 2011 02:41 EDT |
| Reporter | Christian Damus |
Description
Currently, the IOclHelper interface has the following useful methods: \
OclExpression createInvariant(String expr)
boolean check(Object context, String expr)
Object evaluate(Object context, String expr)
Unfortunately, it is missing two even more useful methods: \
boolean check(Object context, OclExpression expr)
Object evaluate(Object context, OclExpression expr)
which would allow for re-use of an expression that has already been parsed, for
repeated evaluation on the same or different objects.
The text was updated successfully, but these errors were encountered: