This is the mail archive of the
mailing list for the Archer project.
Re: set print objct pros/cons [Re: [Keith Seitz] Re: [tools-team]Status 2008-09-01]
On 09/27/2009 05:21 AM, Jan Kratochvil wrote:
(1) Last "call basep->m ()" should have printed "derived::m"
because "p basep->m" prints "Derived::m()", shouldn't it?
basep->m will always print "base::m" -- your test case did not declare
Base::m virtual. Or is that just an omission in the file you attached?
(2) A lookup can succeed in both "off" and "on" cases with different results.
Indeed. I believe gdb should stick to the language rules, "print object"
or not. We need to break the unwritten gdb development rule that
everything must have a freakin' switch in the debugger. It's
unscalable/unmanageable/user-unfriendly. IMO, "object print" should not
even exist at all.