<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 18, 2013 at 11:16 PM, David van der Spoel <span dir="ltr"><<a href="mailto:spoel@xray.bmc.uu.se" target="_blank">spoel@xray.bmc.uu.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 2013-03-18 20:40, Teemu Murtola wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"> * Doxygen documentation may reference headers by file name, and this<br></div><div class="im">
may silently break if the referenced header gets renamed.<br></div><div class="im"><br>
</div></blockquote>
Thanks for thinking this through. I guess it may not be worth the effort then. I don't understand the doxygen comment though, I thought it picked up all files on its way.</blockquote><div><br></div><div style>You don't need to give up so easily. ;) I still estimate this at only a few hours of effort; your best bet would probably be writing a few scripts to rename the include guards and all instances of the basenames of the headers in the source tree. And searching for wildcards like "*.h" from the source. For doxygen, it indeed picks up all the files, but I was referring to possible comments like "See basicoptions.h for the available concrete classes.", which explicitly mention the name of some file. There isn't that many of these, as mostly the documentation only references class names, but there are some.</div>
<div style><br></div><div style>Teemu</div></div></div></div>