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

2001-09-14 Thread Mattia Barbon
> On Thu, Sep 13, 2001 at 11:07:00AM -0600, Nathan Torkington wrote: > > Isn't the correct solution to this problem to say > >#include > > > > That is, include the subdirectory prefix in all #includes. You -I the > > directory containing parrot/, and that avoids randomly located > > config.

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

2001-09-14 Thread Simon Cozens
On Thu, Sep 13, 2001 at 11:07:00AM -0600, Nathan Torkington wrote: > Isn't the correct solution to this problem to say >#include > > That is, include the subdirectory prefix in all #includes. You -I the > directory containing parrot/, and that avoids randomly located > config.h files from b

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

2001-09-13 Thread Dan Sugalski
At 06:31 PM 9/13/2001 +0300, Jarkko Hietaniemi wrote: > > > > Not, mind, that I'm proposing prepending parrot_ to all the filenames, > > > > though that's an option certainly. > > > > > >That would be fun on 8.3 filesystems :-). > > > > I'm seriously considering not going out of our way to support

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

2001-09-13 Thread Nathan Torkington
Andy Dougherty writes: > > #include "config.h" > > rather than > > #include Isn't the correct solution to this problem to say #include That is, include the subdirectory prefix in all #includes. You -I the directory containing parrot/, and that avoids randomly located config.h files from b

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

2001-09-13 Thread Andy Dougherty
On Thu, 13 Sep 2001, Dave Mitchell wrote: > Andy Dougherty <[EMAIL PROTECTED]> wrote: > > > > > changing parrot.h to do #include "parrot/config.h" and > > > > > then changing > > > > > Makefile to add -I./include to CCFLAGS. > > > Perhaps I'm missing something here, but I always thought that

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

2001-09-13 Thread Jarkko Hietaniemi
> > > Not, mind, that I'm proposing prepending parrot_ to all the filenames, > > > though that's an option certainly. > > > >That would be fun on 8.3 filesystems :-). > > I'm seriously considering not going out of our way to support what could be > reasonably considered antique systems. That'd i

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

2001-09-13 Thread Dan Sugalski
At 08:59 AM 9/13/2001 -0400, Andy Dougherty wrote: >On Wed, 12 Sep 2001, Dan Sugalski wrote: > > > > > changing parrot.h to do #include "parrot/config.h" and > > > > then changing > > > > Makefile to add -I./include to CCFLAGS. > > > One thing to keep in mind is that the directory may not be suff

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

2001-09-13 Thread Benjamin Stuhl
--- Dave Mitchell <[EMAIL PROTECTED]> wrote: > Andy Dougherty <[EMAIL PROTECTED]> wrote: > > On Wed, 12 Sep 2001, Dan Sugalski wrote: > > > > > > > changing parrot.h to do #include > "parrot/config.h" and > > > > > then changing > > > > > Makefile to add -I./include to CCFLAGS. > > > > > One t

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

2001-09-13 Thread Dave Mitchell
Andy Dougherty <[EMAIL PROTECTED]> wrote: > On Wed, 12 Sep 2001, Dan Sugalski wrote: > > > > > changing parrot.h to do #include "parrot/config.h" and > > > > then changing > > > > Makefile to add -I./include to CCFLAGS. > > > One thing to keep in mind is that the directory may not be sufficien

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

2001-09-13 Thread Andy Dougherty
On Wed, 12 Sep 2001, Dan Sugalski wrote: > > > changing parrot.h to do #include "parrot/config.h" and > > > then changing > > > Makefile to add -I./include to CCFLAGS. > One thing to keep in mind is that the directory may not be sufficient on > some platforms. VMS, specifically, ignores the d

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

2001-09-13 Thread 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 f

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

2001-09-12 Thread Dan Sugalski
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 wi

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

2001-09-12 Thread Benjamin Stuhl
--- 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. > > I'd

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

2001-09-12 Thread Andy Dougherty
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. I'd suggest cd parrot mkdir include mkdir