Bugzilla – Full Text Bug Listing
| Summary: | Operation return types are not checked | ||
|---|---|---|---|
| Product: | [Modeling] Epsilon | Reporter: | Dimitris Kolovos <dkolovos> |
| Component: | Core | Assignee: | Dimitris Kolovos <dkolovos> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | agarcdomi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | interim | ||
*** Bug 338379 has been marked as a duplicate of this bug. *** I have fixed this bug in SVN r1447. While fixing this bug, I found a typo in an EVL script inside HUTN. Return types are cached inside EolOperations, and clearing the cache also cleans the cached return type. This is important in EUnit, as we will be reusing the same EolModule over several sets of models. If we didn't clear the cached return type between tests, the return type could refer to a model that is no longer in memory. This issue was detected in one of the Eugenia regression tests, and is now fixed. Fixed in 0.9.1 |
foo().println(); operation foo() : String { return 5; } works fine while it should really throw an exception since foo is declared to return a String but returns an Integer instead