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

[Simon Cozens]

On Wed, Sep 12, 2001 at 07:12:44PM -0400, Dan Sugalski wrote:
> At 03:59 PM 9/12/2001 -0700, Benjamin Stuhl wrote:
> >--- Andy Dougherty <[EMAIL PROTECTED]>
> >wrote:
> >> In perl5, we've had occasional header file name conflicts
> >> over the
> >> years.  One common example is someone putting a file
> >> named "config.h"
> >> in /usr/local/include.  Other conflicts with "string.h"
> >> and "memory.h"
> >> are also conceivable.
> 
> Yep, those two are definitely worrisome, as are some of the others. 
> (Stack.h, registers.h...)

*Nod*. Patches, especially from the bandwidth police, would be very
welcome. :)