This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/4] bitpos expansion summary reloaded
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Siddhesh Poyarekar <siddhesh at redhat dot com>, gdb-patches at sourceware dot org, Pedro Alves <palves at redhat dot com>
- Date: Tue, 13 Nov 2012 20:54:53 +0100
- Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
- References: <20120930065211.GA21118@host2.jankratochvil.net> <20121003184155.03dceed4@spoyarek> <20121003195627.GA17283@host2.jankratochvil.net> <20121004071314.GA4292@host2.jankratochvil.net> <20121021130546.02ea680c@spoyarek> <20121025155412.GA16619@host2.jankratochvil.net> <20121025222123.68c7b118@spoyarek> <20121106200117.GA4110@host2.jankratochvil.net> <20121107134742.GA26600@host2.jankratochvil.net> <87ip9970cg.fsf@fleche.redhat.com>
On Tue, 13 Nov 2012 20:46:07 +0100, Tom Tromey wrote:
> Jan> BTW it would be all sure much easier with C++ and its operator
> Jan> overloading.
>
> Yeah, but I think it is clear now that this will never happen.
> We just have to make the best of the tools we do have.
Pedro told me there were some reasons in the thread but I do not remember any
valid one, sizes were made invalid. I will have to re-read the threads again.
There are only abstract opinions that there may exist systems not supporting
this or that but no valid system.
Developing GDB is not constructive this way, it is still about repeated
catching of crashes from forgotten destructor or exception here and there, the
question of next crash is not if but when.
Regards,
Jan