<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yiv0478267898"><div id="yui_3_16_0_ym19_1_1464713825283_2666"><div id="yui_3_16_0_ym19_1_1464713825283_2665" style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10631">Hi Jay and all:</div><div id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10632">I am searching options to make it easier (maybe tricking our selves) for new Modula-3 users explore our system.</div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10633">As
I said recently, there is a java front end (just misses IRC type checking m3clipse)
and there was FOSS "Scale compiler" backend written in Java, M3 DEC-SRC front end compatible (it generated Sparc, Alpha and Powerpc object code). An excerpt from The Common Language Encoding Form(Clef) Design Document:</div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10805"><br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10699">"For Modula-3, Scale uses the Digital Equipment Corporation
(DEC) Systems Research Center (SRC) Modula-3 front end to generate an AST representation. M32CLEF
reads the Modula-3 AST and uses the generation interface to convert it to Scale's high-level representation." [1]<br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11267"><br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11303"><br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11054"><br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11133">But anyway in my research found DEC was working just before sold to Compaq in an enriched type system, so I would prefer to let current compiler to do the job just in case we anyhow got their experimental type checker:</div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11441"><br clear="none"></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11439"><div id="yui_3_16_0_ym19_1_1464713825283_3065">"Modern programming languages, such as C++, Java, and Ada, include
compile-time checks to detect a wide range of possible errors. The
checks are based on declaring or inferring a type for each object (i.e.,
variables and procedures) and analyzing the program to establish that
objects are used in ways consistent with their types. This kind of
automated support is especially helpful for detecting the kinds of
errors (such as passing arguments that overflow a corresponding
parameter) so successfully used by attackers of operating system and
network software. Ever more expressive type systems are a continuing
theme in programming language research, with considerable attention
being directed recently at the representation of security properties
using types (<span id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11435">Digital</span> <span id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11436">Equipment</span> <span id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11437">Corporation</span>, <span id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11438">1997</span>). Success would mean that compile-time checks could play an even bigger role in supporting trustworthiness properties. " [2]</div><div id="yui_3_16_0_ym19_1_1464713825283_3086"><br></div><div id="yui_3_16_0_ym19_1_1464713825283_3087">Thanks in advance for any comment<br></div></div><div id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_10634"><br clear="none"><span></span></div><div id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11302"><br clear="none"><span></span></div><div dir="ltr" id="yiv0478267898yui_3_16_0_ym19_1_1464709041595_11509"><div id="yui_3_16_0_ym19_1_1464713825283_2910" style="line-height: 1.35; ">
<div id="yui_3_16_0_ym19_1_1464713825283_2911" style="clear: left; ">
<div id="yui_3_16_0_ym19_1_1464713825283_2912" style="float: left; padding-right: 0.5em;text-align: right; width: 1em;">[1]</div><div id="yui_3_16_0_ym19_1_1464713825283_2913" style="margin: 0 .4em 0 1.5em;"><div id="yui_3_16_0_ym19_1_1464713825283_2937" dir="ltr">«Abstract». [on line]. Available on en: ftp://ftp.cs.umass.edu/pub/osl/papers/clef97-abs.html. [Accessed: 31-may-2016].</div></div>
</div><div dir="ltr">
<span id="yui_3_16_0_ym19_1_1464713825283_2914" title="url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fzotero.org%3A2&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&rft.type=webpage&rft.title=Abstract&rft.identifier=ftp%3A%2F%2Fftp.cs.umass.edu%2Fpub%2Fosl%2Fpapers%2Fclef97-abs.html"></span>
</div></div></div><div id="yui_3_16_0_ym19_1_1464713825283_2826" style="line-height: 1.35; ">
<div id="yui_3_16_0_ym19_1_1464713825283_2827" style="clear: left; ">
<div id="yui_3_16_0_ym19_1_1464713825283_2828" style="float: left; padding-right: 0.5em;text-align: right; width: 1em;">[2]</div><div id="yui_3_16_0_ym19_1_1464713825283_2829" style="margin: 0 .4em 0 1.5em;">«Trust in Cyberspace». [on line]. Available on: http://cryptome.org/tic.htm. [Accessed: 31-may-2016].</div>
</div><div dir="ltr">
<span id="yui_3_16_0_ym19_1_1464713825283_2830" title="url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&rfr_id=info%3Asid%2Fzotero.org%3A2&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&rft.type=webpage&rft.title=Trust%20in%20Cyberspace&rft.identifier=http%3A%2F%2Fcryptome.org%2Ftic.htm"></span>
</div></div><div id="yui_3_16_0_ym19_1_1464713825283_2844" class="yiv0478267898qtdSeparateBR"><br clear="none"><br clear="none"></div><div class="yiv0478267898yqt6371813428" id="yiv0478267898yqt30634"></div></div></div></div><div class=".yiv0478267898yahoo_quoted"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"><font face="Arial" size="2"> El Martes 31 de Mayo de 2016 11:35, Elmar Stellnberger <estellnb@elstel.org> escribió:<br clear="none"></font></div> <br clear="none"><br clear="none"> <div class="yiv0478267898y_msg_container">Am 2016-05-31 um 09:32 schrieb Jay K:<br clear="none">> i.e. I'd really like to get out of the build system business.<br clear="none">> like to just use autotools or cmake?<br clear="none"><br clear="none">A make-based build solution would have other advantages as well like <br clear="none">f.i. parallel build by make --jobs=4. That way CM3 could build up to <br clear="none">four times faster.<br clear="none"><br clear="none">> But I suspect our system's qualities is difficult to replicate within the other frameworks.<br clear="none">> i.e. the incrementality<br clear="none">> The way every dynamic library is also available statically.<br clear="none">><br clear="none"><br clear="none"> Why not employ a simple hand written make-file that determines that <br clear="none">by environment variables? i.e. what libraries to build statically.<div class="yiv0478267898yqt3894085595" id="yiv0478267898yqtfd16517"><br clear="none">_______________________________________________<br clear="none">M3devel mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:M3devel@elegosoft.com" target="_blank" href="mailto:M3devel@elegosoft.com">M3devel@elegosoft.com</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel">https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel</a><br clear="none"></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></body></html>