Bug 578861 - o.e.j.i.compiler.parser.Scanner.getNextChar() throws ArrayIndexOutOfBounds on each file
Summary: o.e.j.i.compiler.parser.Scanner.getNextChar() throws ArrayIndexOutOfBounds on...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.22   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-21 03:36 EST by Andrey Loskutov CLA
Modified: 2024-02-19 17:15 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 Andrey Loskutov CLA 2022-02-21 03:36:47 EST 
Continuation from bug 563017 comment 8.

Remaining 3 (and most likely more) need additional effort, because all Scanner.getNextChar(*) implementations are copy-pasted and show same issue.

Code to reproduce (important are lambdas and "record"):

public record X(String name, String abc, String something) {
	enum E {
		A
	}

	static class C {
		E e = E.A;
	}

	public static void main(String[] args) {
		C c = new C();
		switch (c.e) {
		case A -> {
			System.out.println("Hello A");
		}
		default -> System.out.println("Hello E");
		}
	}
}
Comment 1 Eclipse Genie CLA 2024-02-19 17:15:15 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.