Er, you're not saying that *this* sort of bug is the obvious downside to
treating functions as first-class objects? 'cos you only get a bug like
this if you treat functions like *integers*, which is self-evidently nuts
from a practical POV, and only emerges from C because of the loony way it
indicates that a pointer is null (0 indeed!).