https://bugs.freedesktop.org/show_bug.cgi?id=65108
--- Comment #12 from Stephan Bergmann <[email protected]> --- (In reply to comment #11) > I'd suggest my compromise: using "" for includes in the same directory as > the cxx file, and <> for everything else; clearly we'd need a script to > identify and re-write for those. Do we have such a thing ? :-) A conforming compiler is not require to support #include <...> for anything but the standard headers. In practice, the compilers we use today do. So, all other things being equal, the safest thing to do would be to use #include "..." for inclusion of all of LO's source files. However, the odd behavior of MSVC described in comment 8, <http://msdn.microsoft.com/en-us/library/36k2cdd4%28v=vs.80%29.aspx> "#include Directive (C/C++)" can be used as an argument in favor of <...>. Though I would probably use <...> exclusively then, and not even stick to "..." for inclusion of source files from the same directory. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
