Re: #include "config.h" or #include "parrot/config.h"

[Nathan Torkington]

Andy Dougherty writes:
> > #include "config.h"
> > rather than
> > #include <config.h>

Isn't the correct solution to this problem to say

   #include <parrot/config.h>

That is, include the subdirectory prefix in all #includes.  You -I the
directory containing parrot/, and that avoids randomly located
config.h files from buggering you up.

Nat