All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Joel Soete <soete.joel@tiscali.be>,
	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 01:10:10 -0400	[thread overview]
Message-ID: <20040705051010.GA24583@nevyn.them.org> (raw)
In-Reply-To: <20040703205621.GA1640@ucw.cz>

On Sat, Jul 03, 2004 at 10:56:21PM +0200, Vojtech Pavlik wrote:
> On Sat, Jul 03, 2004 at 12:53:21PM +0000, Joel Soete wrote:
> > Hi Marcelo,
> > 
> > Please appolgies first for wrong presentation of previous post (that was 
> > the first and certainly the last time that I used the 'forwarding' option 
> > of this webmail interface :( ).
> > 
> > Here are some backport to clean up some warning of type: use of cast 
> > experssion
> > as lvalues is deprecated.
> > --- linux-2.4.27-rc2-pa4mm/kernel/sysctl.c.Orig	2004-06-29 
> > 09:03:42.000000000 +0200
> > +++ linux-2.4.27-rc2-pa4mm/kernel/sysctl.c	2004-06-29 
> > 10:10:31.588030256 +0200
> > @@ -890,7 +890,7 @@
> >  				if (!isspace(c))
> >  					break;
> >  				left--;
> > -				((char *) buffer)++;
> > +				buffer += sizeof(char);
> 
> This (although correct in the end) is a wrong thing to do.
> 
> It seems to look like the intention is to move the pointer by a char's
> size, however your change is equivalent to:
> 
> 	buffer += 1;
> 
> And if buffer wasn't void*, which it fortunately is, it would, unlike
> the older construction, move the pointer by a different size.
> 
> 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.  You can't do arithmetic on one either.  GNU
C allows this as an extension.

It's actually this, IIRC:
  buffer = ((char *) buffer) + 1;

-- 
Daniel Jacobowitz

  parent reply	other threads:[~2004-07-05  5:10 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 [this message]
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 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
2004-07-27 15:59         ` 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=20040705051010.GA24583@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=soete.joel@tiscali.be \
    --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.