* Mike Pall: > I don't think this is an ANSI C violation either, because the > (now) invalid pointer is never used in a subsequent comparison. I think creating an undefined pointer is itself undefined, so it's a violation.