Bug 415275 - [compiler][internal] minimize differences between AllocationExpression and QualifiedAllocationExpression
Summary: [compiler][internal] minimize differences between AllocationExpression and Qu...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 04:46 EDT by Stephan Herrmann CLA
Modified: 2022-09-02 12:54 EDT (History)
2 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 Stephan Herrmann CLA 2013-08-17 04:46:29 EDT 
Work in bug 413460 indicates that classes AllocationExpression and
QualifiedAllocationExpression are diverging in their implementations.

I'm not sure if all differences are semantically motivated.

To facilitate applying the same fix to both classes also in the future,
we might want to refactor methods like resolveType to better show similarities
and intended differences.

See also bug 358007.
Comment 1 Manoj N Palat CLA 2018-05-16 01:38:15 EDT 
Bulk move out of 4.8
Comment 2 Eclipse Genie CLA 2020-07-13 18:50:53 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 3 Eclipse Genie CLA 2022-09-02 12:54:14 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.