From: Michael Meissner <meissner@cygnus.com>
To: jsm@cygnus.com, raeburn@cygnus.com
Cc: bfd@cygnus.com
Subject: Re: [toddpw@wrs.com: Patch to opcodes/ppc-opc.c to avoid overnested parens in MSVC.]
Date: Wed, 29 Jul 1998 19:58:00 -0000 [thread overview]
Message-ID: <199807300258.WAA02410@tiktok.cygnus.com> (raw)
| Perhaps a better fix would be to create an enumerator instead of a
| large collection of macros?
It depends, some older compilers (notably PCC varients) had problems with more
than 150 enums. On the other hand, bfd would certainly not build on such
systems, so maybe we don't have to worry about such systems.
next reply other threads:[~1998-07-29 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-29 19:58 Michael Meissner [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-07-28 11:47 Jason Molenda
1998-07-29 15:29 ` Ken Raeburn
1998-07-29 16:12 ` Jason Molenda
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=199807300258.WAA02410@tiktok.cygnus.com \
--to=meissner@cygnus.com \
--cc=bfd@cygnus.com \
--cc=jsm@cygnus.com \
--cc=raeburn@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).