This is the mail archive of the
mailing list for the Archer project.
Re: Template function support
I thought perhaps you'd have a new LOC_TEMPLATE, then add a new symbol
with that class. Then when you do a lookup for "foo" you can tell that
it is a "phony" symbol that represents a template. Finally, the
symbol's value union could have a new field that points to all the
Alternatively such a symbol could just store a type that has a new
TYPE_CODE_. I'm not sure whether this would be any better.
I'm not sure that this is sane and/or easily implemented.
Thanks for the pointers! I don't know which way I'll go. The TYPE_CODE
approach was the only thing I came up with, but I will look into both.
Sami> + return c != NULL&& strchr (name, '>')> c;
I don't think you really need that second clause there.
This is to avoid matching things like operator< operator<=, and
operator<<. Come to think of it the second clause should be
strchr (c, '>') != NULL
I didn't look too closely at all of it. Make sure that psymbol changes
don't poison the bcache, and that lookups that find a name like this
don't do the wrong thing elsewhere in gdb.
Will do. I am not sure I understand this mechanism well, but I'll figure