Bug 539596 - [11] Investigate bringing [selective] protected methods under nestmate ambit
Summary: [11] Investigate bringing [selective] protected methods under nestmate ambit
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.9   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact: Manoj N Palat CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-27 23:35 EDT by Manoj N Palat CLA
Modified: 2023-01-29 06:56 EST (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 Manoj N Palat CLA 2018-09-27 23:35:49 EDT 
Investigate whether we can get protected methods use nesting, atleast selectively if not all, and elide bridge method generation

See bug 535918 comment 16 - part regarding protected..
ample:
org.eclipse.jdt.core.tests.compiler.regression.LocalVariableTest.test007()
generates synth field access method.

Question:  While talk was about private members, should we include other constellations, too? (here: inherited protected member).
Comment 1 Eclipse Genie CLA 2020-11-08 01:17:30 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.
Comment 2 Eclipse Genie CLA 2023-01-29 06:56:24 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.