Bug 7305 - interface methods are marked abstract
Summary: interface methods are marked abstract
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P4 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-07 08:41 EST by Martin Aeschlimann CLA
Modified: 2003-03-17 11:50 EST (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 2002-01-07 08:41:19 EST 
When getting the flags of a method from an interface (IMethod.getFlags()), such 
methods are marked as 'abstract', even in the source the 'abstract' keyword is 
not used.
We have code in jdt.ui to filter this out again at least at two places.
JavaElementImageProvider and the JavaDoc frontend.
This is not done for the 'public' modifier: Methods in interface are 'public' 
by default, but IMethod.getFlags() does not reflect that.

I think the consistent solution would be to have JavaModel reflecting directly 
the document structure, and not make modifications depending on the Java 
context.
Comment 1 Philipe Mulet CLA 2002-01-09 07:09:21 EST 
If the method was defined in binaries, then we cannot improve the current 
behavior. On sources, I cannot reproduce the problem. The only flag we do 
propagate by mistakre is AccSemiColonBody (internal parsing flag), but it does 
not collide with the visibility flags.
Comment 2 Philipe Mulet CLA 2002-01-09 08:46:40 EST 
Ok to close ?
Comment 3 Martin Aeschlimann CLA 2002-01-09 13:39:22 EST 
you are right , it works. sorry, i made the wrong conclusion.
closing.