public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Question for ISO C standards gurus
Date: Sat, 27 Mar 2004 14:25:00 -0000	[thread overview]
Message-ID: <1080352873.4600.253.camel@localhost.localdomain> (raw)
In-Reply-To: <m3n063ullk.fsf@gossamer.airs.com>

On Fri, 2004-03-26 at 20:25, Ian Lance Taylor wrote:

> I can't see any reason why that would print 5.  Based on the above, p
> should be incremented before the function call to foo().  But that
> doesn't change the value of *p++, which means "get the value at *p,
> then increment p".  The above just means that this should not happen:
>     t1 = *p;
>     foo (t1);
>     p = p + 1;
>
Thanks.  Now I know what the bug is, then.


Diego.

  reply	other threads:[~2004-03-27  2:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 18:47 law
2004-03-25 18:58 ` Dave Korn
2004-03-27  1:35   ` Diego Novillo
2004-03-27 11:25     ` Ian Lance Taylor
2004-03-27 14:25       ` Diego Novillo [this message]
2004-03-29 17:18       ` Dave Korn
2004-03-27 21:56     ` law
2004-03-25 18:59 ` Paul Jarc
2004-03-25 19:14   ` Dale Johannesen

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=1080352873.4600.253.camel@localhost.localdomain \
    --to=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ian@wasabisystems.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).