Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@redhat.com>,
	gdb-patches@sourceware.org,
	       Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH 0/4] bitpos expansion summary reloaded
Date: Tue, 13 Nov 2012 19:55:00 -0000	[thread overview]
Message-ID: <20121113195453.GA22320@host2.jankratochvil.net> (raw)
In-Reply-To: <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


  reply	other threads:[~2012-11-13 19:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 13:33 Siddhesh Poyarekar
2012-09-28 11:20 ` Jan Kratochvil
2012-09-28 11:40   ` Siddhesh Poyarekar
2012-09-28 12:06     ` Jan Kratochvil
2012-09-28 12:19       ` Siddhesh Poyarekar
2012-09-29 17:39 ` Jan Kratochvil
2012-09-29 18:12   ` Jan Kratochvil
2012-09-30  6:52     ` Jan Kratochvil
2012-10-01  5:21       ` Siddhesh Poyarekar
2012-10-01  6:14         ` Jan Kratochvil
2012-10-03 13:12       ` Siddhesh Poyarekar
2012-10-03 18:38         ` Jan Kratochvil
2012-10-04  7:20           ` Siddhesh Poyarekar
2012-10-03 19:56         ` Jan Kratochvil
2012-10-04  7:13           ` Jan Kratochvil
2012-10-21  7:36             ` Siddhesh Poyarekar
2012-10-22 20:45               ` Tom Tromey
2012-10-23  1:34                 ` Jan Kratochvil
2012-10-23  1:58                   ` Jan Kratochvil
2012-10-23  2:29                     ` Siddhesh Poyarekar
2012-10-23  2:37                       ` Jan Kratochvil
2012-10-23  2:38                   ` Tom Tromey
2012-10-23 19:11               ` Jan Kratochvil
2012-10-24 18:33                 ` Tom Tromey
2012-10-24 18:55                   ` Jan Kratochvil
2012-10-24 20:18                     ` Tom Tromey
2012-10-25 15:54               ` Jan Kratochvil
2012-10-25 16:52                 ` Siddhesh Poyarekar
2012-11-06 20:01                   ` Jan Kratochvil
2012-11-07 13:48                     ` Jan Kratochvil
2012-11-13 19:46                       ` Tom Tromey
2012-11-13 19:55                         ` Jan Kratochvil [this message]
2012-11-01 15:24               ` Jan Kratochvil
2012-11-01 16:56                 ` Siddhesh Poyarekar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121113195453.GA22320@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=siddhesh@redhat.com \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox