On Fri, Aug 23, 2013 at 3:33 PM, Jonathan S. Shapiro <[email protected]>wrote:

> On Fri, Aug 23, 2013 at 2:23 PM, David Jeske <[email protected]> wrote:
>   I'm particularly curious how you think bitc-the-second differs from
> Nemerle1/2, since it has modular compilation, inference, variants,
> pure-functional, and compile-time-metaprogramming.
>
> Since I can't find a proper language reference for Nemerle, I'm not sure
> how to answer that. I looked at their web site. It leaves me with more
> questions than answers about Nemerle.
>

I hear you. Nemerle docs are a bit of a mess. I think the original
programmers are Russian, so clean English documentation may not be their
strong suit. I also think they were hired off to work on
Kotlin<http://kotlin.jetbrains.org/>
.

http://nemerle.org/wiki/index.php?title=Reference

http://nemerle.org/wiki/index.php?title=Documentation
https://github.com/rsdn/nemerle/wiki

Another fast whole-program-compiler-of-the-week is
Nimrod<http://nimrod-code.org/>(compiles to C). Seems interesting for
it's use of multi-methods rather
than vtables, and semi-decent compile-time macros. Other than that it's
very early.


>  Mono seems darn close to an open-source implementation of an AOT
>> optimization infrastructure (which admittedly could use work, but it's
>> quite capable and even supports LLVM as a backend for AOT).
>>
>
> Yes. And since LLVM doesn't track type information for registers, it's not
> a particularly good target for GC'd languages.
>

I'm confused. Mono supports either their own CLR style AOT+JIT, or static
LLVM (though they use their own GC, not LLVMs). Their own AOT+JIT could be
improved for sure. However, by my read it is an open source AOT
optimization infrastructure. What am I not seeing?


>  I think this is already changing because of mono-team's work on their
>> excellent Xamarin/Mono C# mobile development direction. However, this is
>> more focused on Mono/LLVM/AOT since AFAIK iOS does not allow JIT.
>>
>
> Yes. There is an allergy to C# in the open source community because of its
> connection to Microsoft. What you say about Xamarin may be true, but it
> surprises me.
>

I was unclear. What I meant to say was:

Xarmarin is applying Mono and C# successfully to non-Microsoft areas (Mac,
iOS, and Android). I anecdotally see this driving more open-source interest
in C#, because it makes C# more viable off windows. I hope this will
eventually translate into more open-source contribution to Mono itself.
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to