Bug 88023 - Binary methods with linebreaks in header have no name/source range
Summary: Binary methods with linebreaks in header have no name/source range
Status: RESOLVED DUPLICATE of bug 148010
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 87514 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-15 04:09 EST by Markus Keller CLA
Modified: 2006-06-28 10:42 EDT (History)
3 users (show)

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 Markus Keller CLA 2005-03-15 04:09:49 EST 
HEAD

Binary methods with linebreaks after modifiers have no source range. From
jdk1.5.0_01, open java.util.Collections. The three methods below have no source
range and are thus not selected in the java editor when selected in the outline.

    public static <T>
    int binarySearch(List<? extends Comparable<? super T>> list, T key) {

   private static <T>
    int indexedBinarySearch(List<? extends Comparable<? super T>> list, T key)

    private static <T>
    int indexedBinarySearch(List<? extends Comparable<? super T>> list, T key)
Comment 1 Markus Keller CLA 2005-08-22 07:01:36 EDT 
Another binary method from java.lang.Class, where source range and name range
are [offset=-1; length=0]:

    public boolean isAnnotationPresent(
        Class<? extends Annotation> annotationClass) {
        ...
    }

This bug probably also causes problems for content assist and javadoc hovers
(bug 82147). Generalizing title from "Binary methods with linebreaks after
modifiers have no source range".
Comment 2 Markus Keller CLA 2005-09-29 12:04:02 EDT 
*** Bug 87514 has been marked as a duplicate of this bug. ***
Comment 3 Olivier Thomann CLA 2006-02-24 20:46:47 EST 
*** Bug 129317 has been marked as a duplicate of this bug. ***
Comment 4 Markus Keller CLA 2006-04-20 09:00:29 EDT 
For these methods, getParameterNames() also does not find the names in source, unless Javadoc attachments are available (i.e. remove Javadoc attachments to reproduce the missing parameter names).
Comment 5 Jerome Lanneluc CLA 2006-06-28 10:42:20 EDT 
Verified that those methods now have a source range with JDT Core HEAD. I believe the fix for bug 148010 also fixed this bug.

*** This bug has been marked as a duplicate of 148010 ***