On Fri, Aug 23, 2013 at 12:23 AM, Bennie Kloosteman <[email protected]>wrote:
> I have no issue with going with the CLR first but > > What do you offer over C# - with the existing CLR ? > Who cares? The first objective is to validate and bootstrap the *language*. There is a *lot* of infrastructure that needs to be built before any sort of production-capable implementation becomes possible. The more of that we can do in BitC itself, the happier we are going to be. But in order to do that, we need to have a running version of BitC to bootstrap in. The less investment we need to make in order to have a bootstrap implementation, the better. CLR is merely a collection of features that facilitate a bootstrap implementation. Nothing more. Also, we would have an implementation that early users could play with and generate feedback from. That's very important. So where does this go in the future > I would say most of it would be improvements in the GC > AOT is no big deal . ( CLR a few apps just run ngen as part of the > install) > AOT may be no big deal in your mind, but the fact is that there exists not open source optimization infrastructure that attempts to target garbage-collected languages. We've discussed the issues with LLVM. CLR is missing some key things that we want, and it doesn't provide an optimizer. C-- isn't viable, and that leaves....? GC is actually not one of the more urgent issues. That's something that we can improve over time, but we need control over code generation in order to do so. Even if that compiler sucks, and the resulting code runs glacially, it can be used to start rebuilding some of the things that you mentioned in safe[er] style. > You mentioned you cant use the standard lib due to inheritance , very > little of the standard lib uses inheritance its mainly interfaces... > I was referring to the existing CLR infrastructure, almost *all* of which is inheritance based. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
