--- 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 thing to keep in mind is that the directory may
> not be sufficient on
> > > some platforms. VMS, specifically, ignores the
> directory portion of the
> > > include filename. (And the suffix, generally, but
> that's separate)
> >
> > Hmm. So would you suggest adding -I[.include]
> -I[.include.parrot] for VMS
> > as well? (My VMS days were a very long time ago.)
> >
> > > 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 :-).
>
> Perhaps I'm missing something here, but I always thought
> that
>
> #include "config.h"
> rather than
> #include <config.h>
>
> would ensure that the local Perl version would get always
> get picked up in
> preference.
>
The point is not us finding our config.h; the problem is if
we are embedded, we don't want to clobber our embedder's
config.h. (Besides, when we're being embedded, there're no
promises about what order the -I flags will be when we're
compiled. E.g.:
#include "parrot/embed.h" /* includes "parrot/config.h"
#include "project.h" /* includes "config.h" */
int call_parrot(...)
{
IV i;
...
#ifdef USE_FUNCTION_FOO
embedders_foo();
#endif
...
}
-- BKS
__________________________________________________
Terrorist Attacks on U.S. - How can you help?
Donate cash, emergency relief information
http://dailynews.yahoo.com/fc/US/Emergency_Information/
