Bug 126092 - Display values of custom data types
Summary: Display values of custom data types
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-01 15:44 EST by Matthias Spycher CLA
Modified: 2020-09-04 15:23 EDT (History)
2 users (show)

See Also:


Attachments
Changes to ...cdt.debug.core (12.44 KB, patch)
2006-02-01 15:45 EST, Matthias Spycher CLA
no flags Details | Diff
Changes to ...cdt.debug.ui (2.46 KB, patch)
2006-02-01 15:47 EST, Matthias Spycher CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Spycher CLA 2006-02-01 15:44:33 EST
This enhancement enables the display of values for custom data types in the variables and expressions view. The basic idea is to define an interface (named ICDIValueType in the provided patches) which can be implemented by types that produce value objects whose string value can be formatted and associated with a label.
Comment 1 Matthias Spycher CLA 2006-02-01 15:45:52 EST
Created attachment 33967 [details]
Changes to ...cdt.debug.core

Introduces ICDIValueType.
Comment 2 Matthias Spycher CLA 2006-02-01 15:47:21 EST
Created attachment 33968 [details]
Changes to ...cdt.debug.ui

Uses ICType.isValueType() to display values of custom data types in CDebugModelPresentation.
Comment 3 Alain Magloire CLA 2006-11-03 10:56:19 EST
excerpt from Mikhail emails:
There are two reasons why I didn't apply (a):
- the main reason: it's two big to apply it without going through the
legal procedure, i.e. fill the questionnaire, submit it to the Eclipse
legal department and wait for permission.
- I was thinking to add an extension point to allow clients to
contribute custom types instead of extending the CDI. It would be great
if we implement all C/C++ specific types as contributions and make the
base of CDI language independent. I think it's doable
Comment 4 Alain Magloire CLA 2006-11-03 12:52:32 EST
Mikhail email:

> From: cdt-debug-dev-bounces@eclipse.org [mailto:cdt-debug-dev-
> bounces@eclipse.org] On Behalf Of Mikhail Khodjaiants
> Sent: Friday, November 03, 2006 11:49 AM
> To: CDT Debug developers list
> Subject: RE: [cdt-debug-dev] CDI proposals (on the wiki)
> 
> > According to an email from Matthias, there was no legal barrier to
> this patch, see:
> 
> As far as I know, even if there are no legal barriers from his company,
> the Eclipse Foundation still have to check the code. The committer who
> appllies the patch should fill a special form and send the patch to the
> Eclipse Foundation. The patch can only be applied after it's been
> approved by them. That's my understanding, by I am not an expert. Ask
> Dave I. or Doug.
> 
> > There is an item to use the logical structure and the detail pane to
> deal with this.  Are we overlapping?
> 
> As far as I remember, the patch extends the existing CDI types by adding
> a new generic type. My suggestion is to add a mechanism (extension
> point) to do it instead of extending the CDI.
> Logical structures and detail panels are used to provide special
> presentations of the existing types.
> 
Comment 5 Doug Schaefer CLA 2006-11-09 13:00:57 EST
Hey guys, after reviewing the patch, I do not see enough content there to warrant a legal review. The actual lines of new code seems to be well less than 100 and I do not see any algorithms there that are not CDT specific. A contribution questionaire is not required.
Comment 6 Sergey Prigogin CLA 2008-01-25 17:40:44 EST
(In reply to comment #3)
> - I was thinking to add an extension point to allow clients to
> contribute custom types instead of extending the CDI. It would be great
> if we implement all C/C++ specific types as contributions and make the
> base of CDI language independent. I think it's doable
 
I don't think the proposed solution is general enough. I'd rather prefer to see the feature described in bug 155331 implemented.