From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] undef reg in gdb_curses.h
Date: Thu, 17 Oct 2013 16:58:00 -0000 [thread overview]
Message-ID: <52601714.4080000@redhat.com> (raw)
In-Reply-To: <1382024768-24151-1-git-send-email-tromey@redhat.com>
On 10/17/2013 04:46 PM, Tom Tromey wrote:
> Let me know what you think.
I think, this is the right thing to do.
That define looks like an old BSD thing. Just googling
around for "#define reg register" finds:
http://marc.info/?l=netbsd-bugs&m=91480640622229&w=2
http://www.retro11.de/ouxr/211bsd/usr/include/curses.h.html
Which ended on Mac OS too:
https://www.opensource.apple.com/source/Libcurses/Libcurses-24/curses.h
Curious how nobody reported this before -- maybe people have been
using GNU ncurses on Macs.
--
Pedro Alves
next prev parent reply other threads:[~2013-10-17 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 15:46 Tom Tromey
2013-10-17 16:58 ` Pedro Alves [this message]
2013-10-29 16:41 ` Tom Tromey
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=52601714.4080000@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--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