[M3devel] cm3cg coverage/profiling features?

Darko Volaric lists at darko.org
Thu Aug 13 02:29:03 CEST 2015


It's the one from the Releases section on GitHub.

On Wed, Aug 12, 2015 at 5:27 PM, Darko Volaric <lists at darko.org> wrote:

> I'm using:
>
> Critical Mass Modula-3 version d5.9.0
>
>   last updated: 2010-07-21
>
>   compiled: 2014-08-27 19:15:04
>
>   configuration: /usr/local/cm3/bin/cm3.cfg
>
>   host: AMD64_DARWIN
>
>   target: AMD64_DARWIN
>
>
>
> On Wed, Aug 12, 2015 at 5:23 PM, Antony Hosking <hosking at purdue.edu>
> wrote:
>
>> I wasn’t aware this had changed.
>> When was this regression introduced?
>>
>> On Aug 13, 2015, at 2:11 AM, Darko Volaric <lists at darko.org> wrote:
>>
>> 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?
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150812/fa43dc09/attachment-0002.html>


More information about the M3devel mailing list