Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335523 - [compiler] separate tuning of severity of decapsulation in "set" callout-to-field
Summary: [compiler] separate tuning of severity of decapsulation in "set" callout-to-f...
Status: VERIFIED FIXED
Alias: None
Product: Objectteams
Classification: Tools
Component: OTJ (show other bugs)
Version: 0.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 0.8 M5   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-26 17:37 EST by Stephan Herrmann CLA
Modified: 2011-01-29 13:32 EST (History)
0 users

See Also:

Attachments
proposed implementation (31.18 KB, patch)
2011-01-26 18:08 EST, Stephan Herrmann CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2011-01-26 17:37:12 EST 
At yesterday's Eclipse Stammtisch in Braunschweig it was suggested that
writing to an inaccessible field (using a decapsulating callout-to-field)
is more severe than reading.

For this reason we should support separate tuning of this diagnostic so that
this situation can be flagged as an error while read access remains a warning.
Comment 1 Stephan Herrmann CLA 2011-01-26 18:08:06 EST 
Created attachment 187698 [details]
proposed implementation

This is basically what I came up with during yesterday's train ride back home
(made one existing test more expressive and implemented the feature).
Comment 2 Stephan Herrmann CLA 2011-01-26 18:12:27 EST 
Patch has been committed as r1245 - r1249.
Comment 3 Stephan Herrmann CLA 2011-01-29 13:32:17 EST 
Verified for 0.8M5 using build 201101290806.