[M3devel] LINUXLIBC6

[Daniel Alejandro Benavides D.]

Hi all:
After ESC we do need much debugger at all, in fact it was designed for that for avoiding put much time on it.
Still if we generate C is for super-optimization (but verified also mechanically), so I don't mind that, but for code quality I prefer C, I agree absolutely in that we should support it again for that purpose (as originally).
As for not verified code we should stick with C--, as it is written for that purposes, but for portability specially with implicit safety.
And for not verified nor optimal and not common use code (like mentor) we should make them source packages (in fact If they are written in Obliq we don't want to redistribute that as non-source), instead part of m3-demo package subdirectory or so.
I think for M3CG is that we need a LLVM or so back-end for JIT.
Thanks in advance

--- El vie, 18/5/12, Dragiša Durić <dragisha at m3w.org> escribió:

De: Dragiša Durić <dragisha at m3w.org>
Asunto: Re: [M3devel] LINUXLIBC6
Para: "Jay K" <jay.krell at cornell.edu>
CC: "m3devel" <m3devel at elegosoft.com>
Fecha: viernes, 18 de mayo, 2012 11:58

One thing we also drop is to source level debug modula-3, if we choose to go along generate-C pathway.
On May 17, 2012, at 1:40 AM, Jay K wrote:
  But heck, really, if we generate C, then targets largely drop away.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120518/55302ae7/attachment-0002.html>