public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: Falk Hueffner <falk@debian.org>
Cc: Joe Buck <Joe.Buck@synopsys.COM>,
	Dave Korn <dave.korn@artimi.com>,
	'Daniel Berlin' <dberlin@dberlin.org>,
	mrc.lrn@inwind.it, gcc@gcc.gnu.org
Subject: Re: Pointers in comparison expressions
Date: Wed, 13 Jul 2005 21:42:00 -0000	[thread overview]
Message-ID: <20050713214235.GB41922@dspnet.fr.eu.org> (raw)
In-Reply-To: <878y0bd2pd.fsf@debian.org>

On Wed, Jul 13, 2005 at 01:28:14AM +0200, Falk Hueffner wrote:
> You're missing my point; size_t was just an example, whoever does this
> will know what the correct type is for their system.  All I'm saying
> is that we shouldn't go to the trouble to document and kick along some
> language extension, maybe even miss some optimization because of it,
> when there's a perfectly fine alternative to it for the user.

Having the user add stupid, potentially breakable casts which decrease
readability just because the standard says the compiler is allowed to
be a prick is not necessarily a good idea.  I don't really see the
point of breaking or even warning on pretty much every memory
management or garbage collection code out there.

  OG.

  parent reply	other threads:[~2005-07-13 21:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 16:24 Mirco Lorenzoni
2005-07-12 16:32 ` Daniel Berlin
2005-07-12 16:53   ` Dave Korn
2005-07-12 21:00     ` Andreas Schwab
2005-07-12 21:42     ` Erik Trulsson
2005-07-12 22:09       ` Joe Buck
2005-07-12 22:28         ` Erik Trulsson
2005-07-12 22:38           ` Falk Hueffner
2005-07-12 23:17             ` Joe Buck
2005-07-12 23:28               ` Falk Hueffner
2005-07-13  2:02                 ` Joe Buck
2005-07-13 21:42                 ` Olivier Galibert [this message]
2005-07-12 23:27             ` Michael Meissner
2005-07-12 22:46           ` Joe Buck
2005-07-16 11:49       ` Vincent Lefevre
2005-07-17 16:55         ` Paul Koning
2005-07-18  1:49           ` Vincent Lefevre
2005-07-18  3:13             ` D. Hugh Redelmeier
2005-07-18 13:13               ` Paul Koning
2005-07-18 13:09             ` Paul Koning
2005-07-12 17:03 ` chris jefferson
2005-07-12 23:18 ` Michael Meissner
2005-07-22 23:20 ` Geoffrey Keating
2005-07-13 13:53 Morten Welinder
2005-07-24  1:13 Paul Schlie
2005-07-26  4:43 ` Geoff Keating

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=20050713214235.GB41922@dspnet.fr.eu.org \
    --to=galibert@pobox.com \
    --cc=Joe.Buck@synopsys.COM \
    --cc=dave.korn@artimi.com \
    --cc=dberlin@dberlin.org \
    --cc=falk@debian.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mrc.lrn@inwind.it \
    /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).