On Monday, 1. January 2007 17:25, Andreas Schwab wrote:
quoted text
> Ingo Oeser <ioe-lkml@rameria.de> writes:
> > Then this works, because the side effect (+20) is evaluated only once.=
=20
quoted text
>=20
> It's not a side effect, it's a non-lvalue, and you can't take the address
> of a non-lvalue.

Just verified this. So If we cannot make it work in all cases, it will
cause more problems then it will solve.

So we are left with a function, which will=20
a) only be used by janitors to provide "kfree(x); x =3D NULL;"=20
    with an macro KFREE(x) in all the simple cases.

b) be used by developers, who are aware of the fact that reusable
    pointer values should set to NULL after kfree().

Doing a) and b) is "running into open doors", so doesn't prevent any
error, obfuscates code more and works only sometimes.

I give up here and would vote for dropping that idea then.


Regards

Ingo Oeser