bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFA: [guile] Header inclusion update [Error building project using g


From: Adam Fedor
Subject: Re: RFA: [guile] Header inclusion update [Error building project using gnustep-guile]
Date: Sun, 06 Apr 2003 20:20:29 -0600
User-agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.1) Gecko/20020905



David Ayers wrote:

So, if I want to *use* a ScriptKit header, my project would:
#include <ScriptKit/gg_Object.h>
this contains:
#include "gstep_guile.h"
which would be searched for in the same directory in which gg_Object.h was found.

This might even speed up the preprocessing a bit, as it doesn't need to go through the -I paths. I think this should be the general technique. I'm sure Apple used to do the same for Foundation.h (except they used import instread of include. I'd be surprised if they don't anymore. I believe why most people do not use this technique is because they are either not aware of it, or they fear ambiguity about which header is included, when the don't qualify the path. This can only happen if the file didn't exist. But that just a bug in my view. If you prefer, I have no problem reverting it before I commit.


I guess I don't feel strongly about it. Although I think most people aren't aware of the difference and might be confused by it. I'm sure it would be nice to do this eventually to all our projects, since it makes including header files so much easier, but I don't have the time now to explore all the ramifications. Perhaps doing just on guile for now as a test is enough.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]