By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,220 Members | 1,493 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,220 IT Pros & Developers. It's quick & easy.

#include <boost/shared_ptr.hpp> or #include "boost/shared_ptr.hpp"?

P: n/a
Is there a general rule/convention for when to use angle brackets and
when to use quotes in #include statements? Is the angle bracket reserved
for "system" header files (e.g. standard library headers), or is it for
general "stable" include files?

What about the grey areas in between these and actual application code,
e.g. headers for a library that is under my control but external to the
project being compiled?

I know both styles work, and in the case of the Boost headers I've seen
both of them used in example code, I'm just wondering if one is more
"correct"?

Cheers,
Colin
Aug 29 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
<>will search the system folder and project/IDE specified additional
include dictionary
"" will search in your project dictionary

Colin Caughie wrote:
Is there a general rule/convention for when to use angle brackets and
when to use quotes in #include statements? Is the angle bracket reserved
for "system" header files (e.g. standard library headers), or is it for
general "stable" include files?

What about the grey areas in between these and actual application code,
e.g. headers for a library that is under my control but external to the
project being compiled?

I know both styles work, and in the case of the Boost headers I've seen
both of them used in example code, I'm just wondering if one is more
"correct"?

Cheers,
Colin
Aug 29 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.