[M3devel] LINUXLIBC6
Jay K
jay.krell at cornell.edu
Mon May 21 10:40:25 CEST 2012
To be more portable, and get out of the "problem" of being self-hosting.
I realize self-hosting has major benefits too.
Someone just needs to see if Debian et. al. have a general story for compilers that compile themselves.
And I need to really implement the C backend I talk forever and ever about....
- Jay
----------------------------------------
> Subject: Re: [M3devel] LINUXLIBC6
> From: dragisha at m3w.org
> Date: Mon, 21 May 2012 10:00:04 +0200
> CC: dabenavidesd at yahoo.es; m3devel at elegosoft.com
> To: jay.krell at cornell.edu
>
> And why would you/we do it? To be less portable? To escape direct knowledge of endian/word_size/jmpbuf/whatever by cpp and run into C/C++/Java?
>
>
> On May 20, 2012, at 11:32 PM, Jay wrote:
>
> > I meant "gcc frontends", which Modula-3 is structured as, in a somewhat backward-seeming way.
> >
> >
> > Btw, rewriting all of m3front in C or C++ or Java probably wouldn't be very difficult.
> >
> >
> > - Jay (briefly/pocket-sized-computer-aka-phone)
> >
> > On May 20, 2012, at 2:28 PM, Jay <jay.krell at cornell.edu> wrote:
> >
> >> Normally gcc compilers
>
More information about the M3devel
mailing list