Re: Variable objects: references formatting

[Nick Roberts <nickrob at snap dot net dot nz>]

 > > OK, if its a patch for -var-valuate-expression then perhaps the BOGUS
 > > comment could be removed as it seems to address this issue.
 > 
 > I read the "BOGUS" comment as referring to the fact that we have to
 > specially trap structs and unions, instead of simply passing
 > everything through common_val_print.  I don't think this patch affects
 > that "bogusness"; it just makes the workaround work better.

I was guessing.  I see that the check is for var->type, whereas perhaps
val_print prints out children if var->val->type is a struct/class.  But I don't
know the relationship between the two and you're the expert in these matters.

 > (Are there any cases where common_val_print (and thus c_val_print)
 > prints the "{...}" we need automatically for us?  Or is this code the
 > sole source of that behavior?)

I don't really know much about that end of things yet.  I've looked mainly
at the mi directory and variable objects.

-- 
Nick                                           http://www.inet.net.nz/~nickrob