Bug 360866 - Assign value does not work for arrays without using the new keyword
Summary: Assign value does not work for arrays without using the new keyword
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-13 12:29 EDT by Michael Rennie CLA
Modified: 2023-11-19 08:44 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2011-10-13 12:29:11 EDT
Using the following snippet:


package a;
public class AssignArray {
	public static void main(String[] args) {
		String[] array = new String[] {"hello", "world"};
		System.out.println(array); //bp here
	}
}

debug the program and try to change the complete set of values of the array (from the variables view detail pane).

The only way to replace the array is to use 'new String[] {"foo", "bar"}' during the assign value operation, but I would also expect just '{"foo", "bar"}' to work as well.
Comment 1 Eclipse Genie CLA 2019-12-07 14:19:29 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 Sarika Sinha CLA 2019-12-08 23:00:19 EST
It behaves the same now as well.
Comment 3 Eclipse Genie CLA 2021-11-28 11:13:07 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 4 Eclipse Genie CLA 2023-11-19 08:44:22 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.