Bug 6246 - editor preferences: use of 'keywords' 'build-in types' is incorrect
Summary: editor preferences: use of 'keywords' 'build-in types' is incorrect
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Kai-Uwe Maetzel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-23 05:25 EST by Adam Kiezun CLA
Modified: 2001-12-12 08:15 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Kiezun CLA 2001-11-23 05:25:50 EST
according to the java lang spec (section 3.9)
the list of java keywords is as follows:

abstract double int strictfp
boolean else interface super 
break extends long switch 
byte final native synchronized 
case finally new this 
catch float package throw 
char for private throws 
class goto protected transient  
const if public try 
continue implements return void 
default import short volatile 
do instanceof static while 

//---
then, there are 3 reserved words (2 boolean literals and a null literal):
true, false, null

the notion of 'built-in' types does not exist!
only some of the java keywords are recognized as such by our java editor, 
which is incorrect.

suggest adding all keywords to the keyword list,
create another entry for reserved words (the 3 mentioned)
and removing the 'built-in types' entry
Comment 1 Erich Gamma CLA 2001-11-23 05:55:29 EST
We should complete the keyword list.

The distinction between built-in types and keywords is subtle and can easily 
confuse users. Need to understand the background first why there is a 
distinction between keywords and built-in types.

true, false, null: should be handled as keywords and not as built-in types.
Comment 2 Kai-Uwe Maetzel CLA 2001-12-12 08:15:39 EST
Build > 20011212.