This is the mail archive of the
mailing list for the GCC project.
Re: Internals for STL containers
> > However, _M_impl, _M_start etc are gcc internals and it might be risky for
> > Emacs to rely on them. Can anyone say how likely these internals are to
> > change? I'm not asking for a guarantee. It would be helpful just to know
> > when they last changed as an indication of how volatile this code might be.
On Thu, Feb 07, 2008 at 01:00:17PM +0100, Paolo Carlini wrote:
> I would say they are pretty stable, because we have a stable ABI which
> we are not going to break until C++0x: that means we can only implement
> limited span changes, we cannot add data members, for example neither
> change the memory layout of the classes.
Yes, it would certainly make sense to teach gdb (not just the Emacs
interface of gdb) to recognize STL containers and give a better display.
The members of std::vector have been stable since gcc-3.0, I'm pretty
sure (certainly since 3.2).
But that would be more appropriate to discuss on the gdb list.