Bug 124093 - spec preference options at constant itself
Summary: spec preference options at constant itself
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-17 05:18 EST by Martin Aeschlimann CLA
Modified: 2007-06-22 10:10 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 Martin Aeschlimann CLA 2006-01-17 05:18:54 EST
Comment 1 Martin Aeschlimann CLA 2006-01-17 05:22:59 EST 
20060117

To know what a preference constant is about
(e.g. JavaCore.COMPILER_PB_PARAMETER_ASSIGNMENT), one has to find a part of the actual key of the constant (e.g. 'parameterAssignment') in the comment of method getDefaultOptions().

It would be a big help if the constant itself contains the spec. The comment in getDefaultOptions() is so huge that it is hard to find anything.
Comment 2 Philipe Mulet CLA 2006-01-17 06:02:10 EST 
Remember that the constants are only helpers to remember the names. This is why the doc of getDefaultOptions() historically contained all the data.