Bug 37199 - org.eclipse.jdt.internal.core.Initializer.isBinary is always false
Summary: org.eclipse.jdt.internal.core.Initializer.isBinary is always false
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-04 07:57 EDT by Jesper Kamstrup Linnet CLA
Modified: 2003-07-18 06:57 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 Jesper Kamstrup Linnet CLA 2003-05-04 07:57:05 EDT 
isBinary in org.eclipse.jdt.internal.core.Initializer is always false,
regardless of whether the type in which it is declared is a SourceType or
BinaryType.

This fact can cause problems elsewhere if it's necessary to determine whether an
IJavaElement can be manipulated (even though it's not binary (as of isBinary) it
returns null from getCompilationUnit).
Comment 1 Philipe Mulet CLA 2003-05-05 06:59:17 EDT 
Initializers (instance or static) do not exist in classfiles, these are 
artifacts declared in source, and then inlined into constructors or clinit 
method.

What are you looking for exactly ? Initializers should be able to find their 
defining compilation unit though. Is this what you are arguing about ?
Comment 2 Jesper Kamstrup Linnet CLA 2003-05-06 00:31:21 EDT 
I see your point.

My concrete problem is a problem with JDT UI. 
org.eclipse.jdt.internal.ui.reorg.SourceReferenceAction.isDeletedFromEditor(ISourceReference)
fails when the IJavaElement is an initializer from a class file. I will file a
bug report against JDT UI instead.

Thanks for your comments.