From: SourceForge.net <no...@so...> - 2010-04-20 08:21:24
|
Feature Requests item #2989788, was opened at 2010-04-20 08:21 Message generated for change (Tracker Item Submitted) made by zhnmju123 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=396647&aid=2989788&group_id=29557 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: ZenJu (zhnmju123) Assigned to: Nobody/Anonymous (nobody) Summary: File Include variant Initial Comment: Hi Rich, > If you have further questions, please feel free to add them here. Hopefully this doesn't seem like spamming, but you checked "Close comment posting" for the other ticket, so I need to create a new one ;) Reference: https://sourceforge.net/tracker/?func=detail&atid=396647&aid=2989216&group_id=29557 > potential ambiguity With "" There is a fixed sequence in which the preprocessor looks for the file. It first starts searching in the directory that holds the sourcefile using an "#include". If it is found, it stops, so there is no ambiguity for users. So from a library user's point of view using "" doesn't seem to introduce any drawbacks, but at least saves one precondition (project include path). Looking at the style of the library as a whole, avoiding dependencies seems to be a major design goal? Regards, ZenJu ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=396647&aid=2989788&group_id=29557 |