Subject: Re: include path question
From: Mike Nordell (tamlin@algonet.se)
Date: Sun Jan 28 2001 - 01:19:57 CST
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"
?
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.
Am I hoping for a miracle, or is this something we actually could do without
hurting compatibility?
/Mike - don't...
This archive was generated by hypermail 2b25 : Sun Jan 28 2001 - 01:20:01 CST