Re: C's trikery semantic opens up backdoor in new Linux kernel

[Duncan Sands <baldrick@free.fr>]

> >IMHO the real problem is that
>
> the syntax of C allows such things. Simple as that, it doesn't matter
> if you even can set strict coding standards to make such things hardly
> possible.
>
> >uid is not an opaque type and can
> >be changed with a simple assignment.  Much better if that required
> >a function call.
>
> You can almost always find a workaround. The problem is to use it
> everytime and force people to use it.

I was under the impression that (using preprocessor trickery) it was possible
to get the equivalent of an Ada private type in C.  Then everyone is forced
to use function calls to get/set the value, unless they do type casts etc.
In all cases, abuse would stand out more than it does now.

> For instance considering the simple rule that in a comparison with a
>
> constant value you should always state the constant first:
> |if ((__WCLONE|__WALL) == options) && (0 = current->uid))
>
> wouldn't compile, either.

No, but do you really think such a style could be enforced in the linux
kernel community?  Think of "herding cats".

Duncan.