Re: [RFC][patch 2/9] export values mechanism to Python

Tom Tromey
2008-07-26T17:17:27Z

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

>> * I suspect it will be more common to use a string-valued expression
>> here than it will be to use a string constant.

Daniel> I don't know about that... If we have a foo and want to
Daniel> determine what sort of foo it is, we'll want foo.type and
Daniel> foo.subtype; in other words I expect pretty-printers to use
Daniel> lots of fixed-name members.

Good point.

>> * This approach also works nicely for arrays.
>> * This approach does not mix the Value namespace with the
>> debuggee's field names.

Daniel> I thought about making both approaches work.
[...]

Daniel> So, it only makes sense if we plan to have no instance methods for
Daniel> values. You'd know better than I do whether instance methods are
Daniel> likely to be useful here.

I don't really know. I was just thinking we should be a bit
conservative so that if we find out we need methods later, we can add
them without worry.

There do seem to be a number of methods defined in value.h. I don't
know whether it makes sense to expose most of these to python, though.

Tom