Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: MinGW build failure for GDB 8.2.90 with source-highlight
Date: Thu, 07 Mar 2019 17:11:00 -0000	[thread overview]
Message-ID: <10c9e85f-d216-ef5c-c8ca-636331d0d1ba@redhat.com> (raw)
In-Reply-To: <a1052036b5ace1d67f905d8ce61e0086@polymtl.ca>

On 03/07/2019 04:59 PM, Simon Marchi wrote:

> I don't recall what's the long term solution for this.  We could use gnulib's namespace support [2], but the disadvantage is that we would need to use gnulib::some_function (assuming we name the namespace "gnulib") instead of just some_function to use the "fixed" version.  If we use some_function directly, it will use the buggy version on those systems where it is buggy.

Wrap all of gdb in a namespace.  Recall that this was what led to C++ wildmatching support.

Thanks,
Pedro Alves


  reply	other threads:[~2019-03-07 17:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:36 Eli Zaretskii
2019-03-07 16:59 ` Simon Marchi
2019-03-07 17:11   ` Pedro Alves [this message]
2019-03-07 18:09     ` Simon Marchi
2019-03-07 18:20       ` Pedro Alves
2019-03-07 18:24         ` Simon Marchi
2019-03-07 20:29         ` Eli Zaretskii
2019-03-07 20:13   ` Eli Zaretskii
2019-03-11 14:18 ` Eli Zaretskii
2019-03-12  2:31   ` Simon Marchi
2019-03-12 10:52     ` Pedro Alves
2019-03-12 13:43       ` Simon Marchi
2019-03-12 15:49     ` Eli Zaretskii
2019-03-12 16:29       ` Simon Marchi
2019-03-12 17:53         ` Eli Zaretskii

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=10c9e85f-d216-ef5c-c8ca-636331d0d1ba@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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