Bugzilla – Full Text Bug Listing
| Summary: | Validations to avoid bad code for setting delegate | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Ed Willink <ed> | ||||
| Component: | Core | Assignee: | Ed Merks <Ed.Merks> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 2.7.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 386050 *** |
Created attachment 199373 [details] Demonstration project The attached project gives two errors when genmodeled. The errors go away after regenmodeling without the setting delegate. The first problem is a missing default initial value constant. This also goes away if the attribute is set non-changeable. Perhaps there should be a validation warning for a changeable setting delegate. The second problem is the use of the attribute's field in toString(), even though the field does not exist. This also goes away if the attribute is set volatile. Perhaps there should be a validation warning for a non-volatile setting delegate.