Bug 563439 - [impl] reconsider /*static*/ fields in Scanner
Summary: [impl] reconsider /*static*/ fields in Scanner
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.16   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: 2020-05-21 13:33 EDT by Stephan Herrmann CLA
Modified: 2024-05-07 14:52 EDT (History)
1 user (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 Stephan Herrmann CLA 2020-05-21 13:33:56 EDT 
(In reply to Stephan Herrmann from bug 563430 comment #3)
> While I'm at it: In Object Teams I also made some tweaks in Scanner, where
> JDT has declarations like:
> public /*static*/ final char[][][][] charArray_length
> 
> The history doesn't give a hint on why /*static*/ rather than static. OTOH,
> I don't recall seeing any problems resulting from non-static, it just looked
> wrong to me.

Let's see if we can safely cherry-pick changes from Object Teams.
Comment 1 Eclipse Genie CLA 2022-05-17 00:22:45 EDT 
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.
Comment 2 Eclipse Genie CLA 2024-05-07 14:52:03 EDT 
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.