[M3devel] LINUXLIBC6

[Jay K]

My point was a bit different -- an interpreter could easily be built from the current intermediate representation.
But heck, then again, the frontend is fast..build an interpreter over source?
Well..hm..actually it might not be fast enough.
This gets rambly/philosophical fast...static checking is useful, but when do you do it?
"static and dynamic are relative".
Before the program runs? Every time before it runs?
When/where do you "save away" decisions/checks that have been made, to avoid them on repeat visits?

Nevermind..I'm not making a clear point..


 - Jay

________________________________
> Subject: Re: [M3devel] LINUXLIBC6 
> From: dragisha at m3w.org 
> Date: Sun, 20 May 2012 22:11:39 +0200 
> CC: dabenavidesd at yahoo.es; m3devel at elegosoft.com 
> To: jay.krell at cornell.edu 
>  
>  
> On May 18, 2012, at 9:49 PM, Jay K wrote: 
>  
> LLVM isn't a bad idea, but there is more expertise out there (and in  
> me) with C and C++, so C and C++ are easier to generate. 
> It is a bit of a chore to learn and use. 
>  
>  
> JIT isn't a crazy idea either..or rather, an interpreter. 
> If you look at parse.c..and you add a few thread locals..I think it's  
> not hard to turn it into an interpreter. 
>    (In reality you don't want to start with parse.c because of the GPL.) 
>  
> LLVM and JIT are close enough. You do LLVM, you get JIT. 
>  
> Also, for debugging we need DWARF. Not incompatible with LLVM.