Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 97187

Summary:	[rendering] Shows Single Char for primitve Types
Product:	[Eclipse Project] JDT	Reporter:	Benjamin Pasero <ENJ>
Component:	Core	Assignee:	Jerome Lanneluc <jerome_lanneluc>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, kirill_frolov, martinae
Version:	3.1
Target Milestone:	3.1 RC2
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Benjamin Pasero

2005-05-30 04:59:31 EDT

In cases where I hover over fields which are primitive types, the JavaDoc is
just displaying the single char representation of the Type, e.g. "Z Main.foo"
for a boolean.

When hovering over local types, I am seeing the type in the Hover, e.g. "boolean
Main.bar()".

I think the JavaDoc should always try to show the type, especially since it is
not quite clear to read a "boolean" out of "Z".

Ben

Comment 1 Dirk Baeumer

2005-05-30 06:47:25 EDT

Martin, I quess that happens now for resolved field declarations in
JavaElementLabels. I enabled the code after JDT/Core has fixed the bug. We
should indeed render boolean here not Z.

Comment 2 Benjamin Pasero

2005-05-30 06:52:23 EDT

Note that this happens for all primitive types (e.g. "D" for "double").

Possible connection: Bug #97206

Ben

Comment 3 Martin Aeschlimann

2005-05-30 06:56:01 EDT

The bug is in jdt.core. The signature returned here is 'LZ;'

public class B {
	boolean fBoolean;
	{
		fBoolean= true;  // hover over 'fBoolean'
	}

}

Comment 4 Philipe Mulet

2005-05-30 07:45:17 EDT

+1 for RC2

Comment 5 Martin Aeschlimann

2005-05-31 05:49:31 EDT

*** Bug 97399 has been marked as a duplicate of this bug. ***

Comment 6 Jerome Lanneluc

2005-05-31 06:41:26 EDT

Changed BindingKeyParser and its subclasses to handle base types separately from
other types (see consumeBaseType(char[]) ).
Added regression test BindingKeyTest#test039()

Comment 7 Dirk Baeumer

2005-06-06 08:47:22 EDT

*** Bug 98476 has been marked as a duplicate of this bug. ***

Comment 8 Olivier Thomann

2005-06-06 20:08:13 EDT

Verified in N20050606-0010

Comment 9 Frederic Fusier

2005-06-10 09:33:11 EDT

Verified for 3.1 RC2 using build I20050610-0010