> The actual spec says "should". Bleah. I don't agree with your reading that argv being non-NULL is a "should." The POSIX Specification does not say "The valu

> The actual spec says "should". Bleah. I don't agree with your reading that argv being non-NULL is a "should." The POSIX Specification does not say "The value in argv[0] should exist" it says "The value in argv[0] should point to a filename string..." The value existing is a foundational assumption in the specification. It is therefore required. (This is consistent with the fact that it's explicitly required that argv[argc] == NULL, which necessarily means that argv != NULL. Consider this: https://pastebin.com/1gieMqEd https://pastebin.com/1gieMqEd If argv is NULL, then pointer arithmetic on it and dereferencing it is undefined behavior, and cannot possibly conform to the guarantee.)