Re: [PATCH] keeping convenience variables (take 2)

Jim Blandy
2005-11-22T05:38:26Z

I may be missing something, be patient:

If I understand the original motivation for this, you don't actually
need to keep around any values that aren't using the builtin types.
Or at least, that could be using the built-in types; it wasn't clear
whether they actually did.

I'm uncomfortable with this whole "print type name and then re-parse
later" approach. I think it's a real kludge. And the fact that it
doesn't seem really necessary for the problem that originally
motivated the change is a red flag, it seems to me.

I can certainly see that it's useful to keep the convenience variables
around across symfile selections and endianness switches; I just think
we should find a better way to handle the types than this.

If the convenience variables you set up in your script, holding
addresses and such, don't refer to the builtin types, why don't they?
Could they? I understand that changing architectures or
architectural variants affects the builtin types, but it seems more
feasible to track those changes than to try to track objfile-based
types as they disappear and reappear.