No, it does not necessarily require <>. If you write

#include "foo.h"

the C compiler will *also* look in all places where it would look for

#include <foo.h>

The only case where <> is needed is where there are two versions of `foo.h'. One where only "foo.h" will find it and one in the system search path used by <foo.h>. In this case, "foo.h" and <foo.h> will find different versions.

So, it all boils down to the question of whether this (probably rare) case justifies the (not very large) extra complexity of allowing header file names enclosed in <>.

Ah, ok. In that case, I don't think we should go to the trouble of allowing <>. Cheers, Simon