On Mon, Aug 26, 2013 at 9:29 PM, David Jeske <[email protected]> wrote:
> On Mon, Aug 26, 2013 at 8:30 PM, Jonathan S. Shapiro <[email protected]>wrote: > >> Informally: A compilation approach in which the compiler can choose to >> emit code at static compile time that generates and invokes code at >> runtime. E.g. to perform dynamic loop unrolling. Have a look at Engler's >> work on tick-c at Stanford, which I've mentioned here several times,. >> > > tick-c is crafty, and I follow you now. In the CLR, this is > reflection.Emit(). C# lacks any nice tick-c/D like syntax for this, but > AFAIK Nemerle supports it. > You can certainly *do* this stuff with reflection.Emit(), but the overheads are so high as to make it prohibitive. tick-C doesn't pay any overhead for emitted code safety. Nemerle allegedly supports a lot of things. It's too bad that the language has no definition. I don't mean that sarcastically; I'd really like to be able to understand what they are doing, but in the absence of any sort of language specification that's challenging. Jonathan
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
