<html><head><style type="text/css"></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">David wrote:<br>>As far as I remember, the implementation of #include "file" is unspecified by the standard. <br>>while Visual C++ and GCC do first look at 'directory where the current file is',<br>I know better why I don't use such compilers anymore when I read this :-)<br>It was for me a de-facto standard that the #include "file" would look first in the directory where the file is.<br>Does cairo bother with Borland or others dynosaurs compilers like the ones you mention anyway ?<br> <br>Nicholas wrote:<br>>Say I have /usr/include/cairo-new and /usr/include/cairo-old do I then <br>>need another cairo subdirectory under them?<br>There would  be solutions, you could on these unix-like system, provide a dynamic link to the current used directory<br>and change it when you wish to (I reasonably suppose you don't use both libs versions at the same time),<br>Or encapsulate the related cairo includes to your custom include file and specify unambiguously the alternative version subfolder name that you may use in your encapsulating include file, but this suppose you won't publish the alternative directory change ...<br><br>These are good points though,  thanks for the enlightening comments,<br><br>Fabien.</div></body></html>