On Sun, Jan 28, 2001 at 08:19:57AM +0100, Mike Nordell wrote:
> Sam TH wrote:
> > Paths are sometimes neccessary, however. I remember once needing to
> > include a file named foo.h, but a different foo.h than the compiler
> > found in the search path. So the absolute path had to be used.
> >
> > I can dig up what actually happend, if you care Mike.
>
> Don't bother (been there myself and it wasn't a pretty picture).
>
> But, since we will probably never move any of the _internal_ AW directories
> relative to one another, would it be a mess if we started to use e.g
> #include "../../af/xp/yahoo.h"
> ?
I don't see why we need to do this. I can't imagine us ever having
namespace conflicts either within abi, or with system libraries. Why
do we need this?
>
> OK, I here assume that those directories would not be moved, but seriously,
> how large is that risk?
>
> I think that Mac (pre Mac-X) can't handle that since it doesn't know what a
> path is, but do we support that platform? If not, would it hurt any of our
> other platforms. I know that if we started to use it it would speed up
> compile time (less dirs to search), it would actually *enhance* decoupling
> since people would then *think* about what they were including and so on.
>
Well, AFAIK, Hubert is trying to get the Mac port to work on Mac OS
<X, so that would be a problem.
sam th
[EMAIL PROTECTED]
http://www.abisource.com/~sam/
GnuPG Key:
http://www.abisource.com/~sam/key
PGP signature
