From: Vojtech Pavlik <vojtech@suse.cz>
To: Joel Soete <soete.joel@tiscali.be>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
marcelo.tosatti@cyclades.com
Subject: Re: Some cleanup patches for: '...lvalues is deprecated'
Date: Sat, 3 Jul 2004 23:45:33 +0200 [thread overview]
Message-ID: <20040703214533.GA2121@ucw.cz> (raw)
In-Reply-To: <40E7278C.8040001@tiscali.be>
On Sat, Jul 03, 2004 at 09:39:24PM +0000, Joel Soete wrote:
> Very interesting but well I am not enough fluent in C to understand this
> fine detail :(
> Can you explain me by an example (let say a long*) what would did "((char
> *) buffer)++;" versus "buffer += sizeof(char);"
> (Don't worry, if don't have time, I will perfectly understand and will
> experiment by myself)
Ok. Let's assume
int *buffer;
just for this example.
((char *) buffer)++;
increments buffer by 1, while
buffer += sizeof(char);
increments buffer by 4, because an int* is always
increased/decreased by multiples of sizeof(int).
So
buffer += 2;
would increment the pointer by 8.
Similarly for other pointer types.
> >So just use
> >
> > buffer++;
> >
> >here, and the intent is then clear.
> >
> Yes ;)
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-07-03 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 12:53 Some cleanup patches for: '...lvalues is deprecated' Joel Soete
2004-07-03 20:56 ` Vojtech Pavlik
2004-07-03 21:39 ` Joel Soete
2004-07-03 21:45 ` Vojtech Pavlik [this message]
2004-07-05 5:10 ` Daniel Jacobowitz
2004-07-05 8:59 ` David Vrabel
2004-07-05 11:59 ` Joel Soete
2004-07-27 12:54 ` Marcelo Tosatti
2004-07-27 15:59 ` Joel Soete
2004-07-27 15:59 ` Joel Soete
2004-07-27 16:31 ` Jon Oberheide
2004-07-30 9:11 ` Joel Soete
2004-07-30 12:51 ` Joel Soete
2004-07-30 17:29 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2004-07-31 8:41 Mikael Pettersson
2004-08-01 10:40 ` Adrian Bunk
2004-08-02 11:34 Mikael Pettersson
2004-08-02 23:08 ` Adrian Bunk
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=20040703214533.GA2121@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=soete.joel@tiscali.be \
/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