On Thu, Sep 13, 2001 at 11:07:00AM -0600, Nathan Torkington wrote:
> 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.
Yes. What I'd like to see Parrot do is reference all its include files
(not just config because one day we'll be embedding Parrot or linking
it with other stuff and we want to avoid conflicts there too) as
<parrot/foo.h> and add -I.. to the includes target in the Makefile.
(You can guess what "I'd like to see" means, practically. :)
Simon
