<div dir="ltr">OK, but can someone explain to me why other, less obscure features have been removed?<div><br></div><div>For instance, cm3 used to keep on compiling files after errors were found. Now it seems to stop after one module. That loss of functionality seriously reduces productivity. I couldn't find any switch to reverse the change. When was this change decided? Is there a way to restore it?</div><div><br></div><div>But more generally: even if the functionality is broken, if it's still there there is a chance someone will fix it, if we remove it we're drawing a line underneath it and ending it.</div><div><br></div><div>The repository is replete with stuff that isn't used or is broken, so removing this one function seems arbitrary. Should we have some sort of consistency?</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 12, 2015 at 8:21 AM, <span dir="ltr"><<a href="mailto:mika@async.caltech.edu" target="_blank">mika@async.caltech.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Don't forget the as-yet-unborn users!<br>
<br>
In all seriousness... the compiler includes a lot of cool stuff, and I<br>
wish it worked. I used some of these features that Jay is talking about<br>
when SRC M3 was all there was, and I remember it did work.<br>
<br>
I think the profiling (and probably other stuff) has been broken since<br>
today's junior high school students were born though.<br>
<br>
Mika<br>
<br>
Darko Volaric writes:<br>
>--===============9067918515746620203==<br>
>Content-Type: multipart/alternative; boundary=bcaec548634a0fec67051d1eb98e<br>
><br>
>--bcaec548634a0fec67051d1eb98e<br>
>Content-Type: text/plain; charset=UTF-8<br>
<div><div class="h5">><br>
>Why does it have to be removed? Is there some pressing reason that<br>
>justifies removing functionality? How does it improve the compiler?<br>
><br>
>Also, how does asking in the mailing list justify its removal? Not all<br>
>users follow the mailing list, and future users do not get a say.<br>
><br>
>On Tue, Aug 11, 2015 at 11:14 PM, Jay K <<a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a>> wrote:<br>
><br>
>> Does anyone use the coverage or profiling or<br>
>> optimization-via-profiling-feedback features of cm3cg?<br>
>> I'm removing dead stuff.<br>
>><br>
>> Thank you,<br>
>> - Jay<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> M3devel mailing list<br>
>> <a href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a><br>
>> <a href="https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel" rel="noreferrer" target="_blank">https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel</a><br>
>><br>
>><br>
><br>
</div></div>>--bcaec548634a0fec67051d1eb98e<br>
>Content-Type: text/html; charset=UTF-8<br>
>Content-Transfer-Encoding: quoted-printable<br>
><br>
><div dir=3D"ltr">Why does it have to be removed? Is there some pressing rea=<br>
>son that justifies removing functionality? How does it improve the compiler=<br>
>?<div><br></div><div>Also, how does asking in the mailing list justify its =<br>
>removal? Not all users follow the mailing list, and future users do not get=<br>
> a say.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=<br>
>">On Tue, Aug 11, 2015 at 11:14 PM, Jay K <span dir=3D"ltr"><<a href=3D"=<br>
>mailto:<a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a>" target=3D"_blank"><a href="mailto:jay.krell@cornell.edu">jay.krell@cornell.edu</a></a>&g=<br>
>t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=<br>
> .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
><br>
><br>
><div><div dir=3D"ltr">Does anyone use the coverage or profiling or optimiza=<br>
>tion-via-profiling-feedback features of cm3cg?<div>I'm removing dead st=<br>
>uff.</div><div><br></div><div>Thank you,</div><div>=C2=A0- Jay<br><br><br><=<br>
>/div> </div></div><br>
><br>_______________________________________________<br><br>
>M3devel mailing list<br><br>
><a href=3D"mailto:<a href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a>"><a href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a></a><br><br>
><a href=3D"<a href="https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel" rel="noreferrer" target="_blank">https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel</a>" rel=<br>
>=3D"noreferrer" target=3D"_blank"><a href="https://mail.elegosoft.com/cgi-bin/mailma=" rel="noreferrer" target="_blank">https://mail.elegosoft.com/cgi-bin/mailma=</a><br>
>n/listinfo/m3devel</a><br><br>
><br></blockquote></div><br></div><br>
><br>
>--bcaec548634a0fec67051d1eb98e--<br>
><br>
>--===============9067918515746620203==<br>
>Content-Type: text/plain; charset="us-ascii"<br>
>MIME-Version: 1.0<br>
>Content-Transfer-Encoding: 7bit<br>
>Content-Disposition: inline<br>
<span class="">><br>
>_______________________________________________<br>
>M3devel mailing list<br>
><a href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a><br>
><a href="https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel" rel="noreferrer" target="_blank">https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel</a><br>
><br>
</span>>--===============9067918515746620203==--<br>
</blockquote></div><br></div>