| Summary: | Missing compiler error when using wrong field specifier in Callout to field (long) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Objectteams | Reporter: | Jan Marc Hoffmann <exelnet> | ||||
| Component: | OTJ | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | P3 | Flags: | stephan.herrmann:
iplog+
|
||||
| Version: | 0.7.1 | ||||||
| Target Milestone: | 0.8 M4 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 182859 [details]
Test and fix
Well spotted.
Actually the check was already in place, it just used a wrong
value for comparison.
Thanks, Jan Marc.
Released for M4 as r1018 f. Verified for M4 using build 201012150343 |
Build Identifier: The following code does not trigger a compiler error: public class A { String value; } public team class MyTeam2 { protected class MyRole playedBy A { String getValue() -> get void value; } } There should be an error @ get void value; Since the field value is of the type String and not void or anything else. Everything works here. The check seems not be implemented. greetings Jan Marc Reproducible: Always