From: "Joel Soete" <soete.joel@tiscali.be>
To: "Daniel Jacobowitz" <dan@debian.org>, "Vojtech Pavlik" <vojtech@suse.cz>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
marcelo.tosatti@cyclades.com
Subject: Re: Some cleanup patches for: '...lvalues is deprecated'
Date: Mon, 5 Jul 2004 13:59:21 +0200 [thread overview]
Message-ID: <40BD9F8700015B8E@ocpmta2.freegates.net> (raw)
In-Reply-To: <20040705051010.GA24583@nevyn.them.org>
Hello Daniel,
> > So just use
> >
> > buffer++;
> >
> > here, and the intent is then clear.
>
> Except C does not actually allow incrementing a void pointer, since
> void does not have a size.
That make better sense to me because aifair a void * was foreseen to pass
any kind of type * as actual parameter?
(So as far as I understand, the aritthm pointer sould be dynamic for the
best 'natural' behaviour?)
> You can't do arithmetic on one either. GNU
> C allows this as an extension.
>
> It's actually this, IIRC:
> buffer = ((char *) buffer) + 1;
>
Many thanks,
Joel
---------------------------------------------------------------------------
Tiscali ADSL LIGHT, 19,95 EUR/mois pendant 6 mois, c'est le moment de faire
le pas!
http://reg.tiscali.be/default.asp?lg=fr
next prev parent reply other threads:[~2004-07-05 11:59 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
2004-07-05 5:10 ` Daniel Jacobowitz
2004-07-05 8:59 ` David Vrabel
2004-07-05 11:59 ` Joel Soete [this message]
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=40BD9F8700015B8E@ocpmta2.freegates.net \
--to=soete.joel@tiscali.be \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.