Re: [IDEA+RFC] Possible solution for min()/max() war

David Woodhouse (dwmw2@infradead.org)
Fri, 31 Aug 2001 00:02:05 +0100

ptb@it.uc3m.es said:
> Well, I understand what you mean, but if the linux kernel wants it
> and the C spec doesn't forbid it, then it'll either stay that way or
> an "official" way will be found of evoking the desired behaviour.

In the world I've been living in for the last few years, GCC people don't
seem to take that much care to avoid breaking the kernel, especially when
the kernel is being gratuitously broken. David's __builtin_ct_assertion()
stuff looks like a sane way of getting the desired behaviour without having
to sacrifice any chickens, and getting that merged into GCC so that we can
start to use it seems like a good idea.

> OTOH I now can't get #__LINE__ to expand as I want it where I want
> it.

Heh. That's magic.

--
dwmw2




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/