Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Alan Modra <amodra@bigpond.net.au>,
	binutils@sources.redhat.com, <gdb@sources.redhat.com>
Subject: Re: [RFA] Replace strdup with xstrdup in tic30-dis.c
Date: Wed, 27 Nov 2002 21:55:00 -0000	[thread overview]
Message-ID: <m38yzeck4g.fsf@gossamer.airs.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0211271938270.17787-100000@dair.pair.com>

Hans-Peter Nilsson <hp@bitrange.com> writes:

> On Wed, 27 Nov 2002, Alan Modra wrote:
> > On Tue, Nov 26, 2002 at 03:29:36PM -0800, Ian Lance Taylor wrote:
> > > I tend to think that bfd_boolean is better because it makes the code
> > > slightly more self-documenting.  An int variable might hold any value,
> > > but a bfd_boolean variable is clearly intended to hold only a true or
> > > false value.
> 
> > > But I'm hardly fanatical about it.
> >
> > Nor am I.  :)  So far, it's two people for "bfd_boolean", one for
> > "int".
> 
> One more for "int" here.  I agree that a boolean type has its
> advantages in theory for clarity, but IMO the effects have now
> proved to be a net negative, a maintenance burden.  Let's just
> stick to "int".

I don't agree with this argument.  We've had problems because
`boolean', `true', and `false' are widely used.  In fact, the comment
on those lines in bfd.h is and has been from the start:

/* I'm sure this is going to break something and someone is going to
   force me to change it.  */

We won't have problems with `bfd_boolean'.

Ian


  reply	other threads:[~2002-11-28  5:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <555D137A-FB43-11D6-84AF-00039396EEB8@apple.com>
     [not found] ` <20021119071305.GM997@bubble.sa.bigpond.net.au>
2002-11-19  8:26   ` Andrew Cagney
2002-11-19 13:42     ` Alan Modra
2002-11-19 14:09       ` Andrew Cagney
2002-11-19 18:05         ` Klee Dienes
2002-11-20  8:05           ` Andrew Cagney
2002-11-20 15:09             ` Alan Modra
2002-11-20 22:56               ` Klee Dienes
2002-11-26 14:03                 ` Andrew Cagney
2002-11-26 14:37                   ` Alan Modra
2002-11-26 15:28                     ` Ian Lance Taylor
2002-11-26 15:57                       ` Alan Modra
2002-11-26 16:15                         ` Andrew Cagney
2002-11-27 16:44                         ` Hans-Peter Nilsson
2002-11-27 21:55                           ` Ian Lance Taylor [this message]
2002-11-28 14:39                             ` Alan Modra
2002-11-28 15:23                               ` Andrew Cagney
2002-11-28 21:04                                 ` Alan Modra
2002-11-29  0:41                                   ` Doug Evans
2002-11-29  4:02                                     ` Ben Elliston
2002-11-26 15:58                       ` Klee Dienes
2002-11-27 11:37             ` David O'Brien
2002-11-26 16:23 Doug Evans

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=m38yzeck4g.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=hp@bitrange.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