<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Clarification: it is "integrated" either way -- no production of .mc files.<div>Just that cm3/builder would know that "IntegratedC" produce a .c file (or perhaps is writing to a pipe) and to then run the C compiler. Vs. pushing that into the backend itself and leaving cm3/builder with "IntegratedObject" that it already knows how to deal with. Either way cm3/builder has to change.</div><div><br></div><div><br></div><div>Currently I'm going through config-only changes.</div><div><br></div><div><br></div><div> - Jay</div><div><br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">CC: m3devel@elegosoft.com<br>From: antony.hosking@gmail.com<br>Subject: Re: [M3devel] C backend -- mode or call quake?<br>Date: Fri, 12 Oct 2012 09:12:53 -0400<br>To: jay.krell@cornell.edu<br><br><div>I vote for integrated. <br><br>Sent from my iPhone</div><div><br>On Oct 12, 2012, at 0:43, Jay K <<a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a>> wrote:<br><br></div><blockquote><div>
<style><!--
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:12pt;font-family:Calibri;}
--></style>
<div dir="ltr">ok..so..I think time to make this decision and implement it.<div><br></div><div> - add a "mode" for C and deal with it in Builder.m3</div><div> I implemented and tested that and presented the diff a few weeks ago</div><div> It is reasonable, simple, works..but it isn't strictly needed.</div><div><br></div><div>or</div><div><br></div><div>- use IntegratedObject and have the C backend call the C compiler "itself" (via the</div><div>existing quake/config files)</div><div>I can go ahead and implement that.</div><div><br></div><div><br></div><div>Either way, cm3 likely must know about the C backend.</div><div><span style="font-size:12pt">It at least has to "new" it, and maybe pass down function pointers for running</span></div><div><span style="font-size:12pt">the C compiler -- or maybe M3C can get the pointers itself.</span></div><div><span style="font-size:12pt"><br></span></div><div>Or I can put this off a bit longer and improve the generated C...</div><div>Using "integrated" saves us from writing and reading back the .mc files.</div><div>More efficient.</div><div><br></div><div><br></div><div><span style="font-size:12pt"> - Jay</span></div><div><br><br></div> </div>
</div></blockquote></div></div> </div></body>
</html>