[m-dev.] For review: handling one by one variable retrieval within the external debugger

[Erwan Jahier]

Fergus Henderson wrote:

> > +/*
> > +** "variables" representing the saved values of succip, hp etc,
> > +** which are the "variables" for which get_type_and_value
> > +** fails, are not of interest to the trace analyzer.
> > +** MR_trace_get_type_and_value_filtered() and MR_trace_get_type_filtered()
> > +** will succeed for theses variables.
> 
> s/succeed/fail/
> 
[...]
> 
> Also you should document why it fails for variables with names
> that start with `TypeInfo', `ModuleInfo', or `HLDS'.

So I propose:

/*
** "variables" representing the saved values of succip, hp etc,
** which are the "variables" for which MR_trace_get_type_and_value()
** succeeds, are not of interest to the trace analyzer.
** MR_trace_get_type_and_value_filtered() (resp.
MR_trace_get_type_filtered)
** will behave the same way as MR_trace_get_type_and_value() except it
will
** fail for these uninteresting variables (The ones that start by
`TypeInfo',
** `ModuleInfo', or `HLDS').
*/

-- 
R1.