Bug 245751 - Assign Value should attempt to Type.valueOf(String) when setting value
Summary: Assign Value should attempt to Type.valueOf(String) when setting value
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-29 16:38 EDT by Darryl Miles CLA
Modified: 2022-09-22 05:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darryl Miles CLA 2008-08-29 16:38:42 EDT
Build ID: 3.4

Steps To Reproduce:


More information:
When using the "Assign Value" in the debugger, it should be possible to interpret a value like "100" entered into the input box for most types.

This would be used as a fallback to the default Java expression evaluation method, lookup the "valueOf(String)" method on the class, if it exists then attempt to call it with the value typed in is no Exception is thrown then use the resulting object as the new value.  If possible display the exception to the user on error.
Comment 1 Darin Wright CLA 2008-09-02 12:36:41 EDT
(In reply to comment #0)
> lookup the "valueOf(String)" method on the class

I don't understand. Where are you suggesting to "lookup" the "valueOf(...)" method? Which class?

Comment 2 Darryl Miles CLA 2008-09-04 10:20:43 EDT
The class of the data type.
Comment 3 Eclipse Genie CLA 2020-09-01 17:06:29 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 4 Eclipse Genie CLA 2022-09-22 05:14:57 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.