<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 6, 2019 at 10:18 AM Nathan Sidwell <<a href="mailto:nathan@acm.org">nathan@acm.org</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Yes, a BMI is required for a header import. Textually including the <br>
header import's original header file is not equivalent.<br></blockquote><div><br></div><div>It won't be required for the scan stage will it? If it is, there is a bootstrapping problem because there is no good way to figure out which order to build the header-unit BMIs in if they import other header-units. I've been assuming that the scan stage will be able to just temporarily mask off the defines and replace them with the correct ones for the header-unit while scanning a file, so that scanning has no generated dependencies.</div></div></div>