From: Mark Mitchell <mark@codesourcery.com>
To: ian@zembu.com
Cc: rth@cygnus.com, binutils@sourceware.cygnus.com
Subject: Re: Patches for IRIX6 N32-ABI ld
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990626211555X.mitchell@codesourcery.com> (raw)
In-Reply-To: <19990627012218.14466.qmail@daffy.airs.com>
>>>>> "Ian" == Ian Lance Taylor <ian@zembu.com> writes:
Ian> as far as I am concerned long term maintainability is the
Ian> single most important characteristic of all code changes. I
Ian> will pick maintainability over features every time.
You're preaching to the choir. :-) I'm always adamant about this point
myself when in comes to C++ changes in EGCS.
Ian> I don't really care. But I agree with Richard: I don't want
Ian> to see code that will silently fail if a new value is added
Ian> to the start of an enum.
The thing we're disagreeing about is the unmainaintainability of the
proposed change. I'm very used to the idiom in question (we use it
*lots* in GCC; functions return 0 to indicate falsity, and various
integers to indicate differents kinds of truth, which some callers
care about and some don't.) So, you should be arguing with me about
the maintainability of this idiom, not telling me to prize
maintainability! :-) :-)
But, hey, reasonable people can agree to disagree.
I'll make the change you want and put it in.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Mark Mitchell
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Mark Mitchell
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Mark Mitchell
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Mark Mitchell
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Mark Mitchell
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Mark Mitchell [this message]
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=19990626211555X.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.com \
--cc=rth@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).