Bug 235058 - [spec] javadoc for JavaCore#setComplianceOptions needs improvement
Summary: [spec] javadoc for JavaCore#setComplianceOptions needs improvement
Status: CLOSED DUPLICATE of bug 263769
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-02 03:32 EDT by Maxime Daniel CLA
Modified: 2014-10-06 09:44 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Daniel CLA 2008-06-02 03:32:14 EDT
I20080530-1730
The javadoc forJavaCore#setComplianceOptions starts with:
	 * Sets the default's compiler options inside the given options map according
	 * to the given compliance.

which is almost meaningless.
Having discussed with Olivier and read the code, I believe that the original intent was to set in the provided map the values of the sole options that were impacted by the compliance, deriving their values as the compiler would do 'by default' when provided the compliance only (that is, without any other option than JavaCore.COMPILER_COMPLIANCE being specified by the caller). Since some of these options definitely have a non-mandatory flavor when considering some compliance levels (aka JavaCore.COMPILER_PB_ASSERT_IDENTIFIER for 1.3 or 1.4), rendering the effective behavior in a concise documentation may turn out to be a bit challenging.
Comment 1 Markus Keller CLA 2014-10-06 09:44:54 EDT

*** This bug has been marked as a duplicate of bug 263769 ***