Bug 180633 - Clarify / improve the use of K_ACCESSIBLE | IGNORE_IF_BETTER by IAccessRule
Summary: Clarify / improve the use of K_ACCESSIBLE | IGNORE_IF_BETTER by IAccessRule
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-03 03:54 EDT by Maxime Daniel CLA
Modified: 2007-04-03 03:54 EDT (History)
0 users

See Also:

Attachments
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 Maxime Daniel CLA 2007-04-03 03:54:57 EDT 
Code based, circa v_746.
The semantics of K_ACCESSIBLE | IGNORE_IF_BETTER should be the same as those of K_ACCESSIBLE (since nothing better is possible...). The code currently accepts such combination *and memorizes it*. I wonder if wouldn't be better to tolerate it (just as anything but K_NON_ACCESSIBLE and K_DISCOURAGED gets projected to K_ACCESSIBLE), but simply forget it. Also, the doc could be more developed on that peculiar subject.