So far Scala is the only language I have looked at that does a decent job of mixing object oriented and functional constructs without making your eyes bleed. Nemerle seems pretty nifty based on it's feature list but I'm wondering what programmers they are targeting. .NET programmers seem pretty happy with C#/F# so they don't have much incentive to adopt another language.
Nemerle 1.0
11–20 of 24 posts
Re: Nemerle 1.0
#12It looks all nice and well, but why can't languages these days be compiled ? I reckon it's way harder to do, but there's no major impediment to achieve what can be achieved in a language based say on the CLR.
Re: Nemerle 1.0
#13It looks all nice and well, but why can't languages these days be compiled ? I reckon it's way harder to do, but there's no major impediment to achieve what can be achieved in a language based say on the CLR.
Why waste time writing a compiler when you can leverage much of the work already done to optimize .NET?
If the clients don't have it, make your installer download it and be done with it.
Re: Nemerle 1.0
#14only windows installer...
Re: Nemerle 1.0
#15It looks all nice and well, but why can't languages these days be compiled ? I reckon it's way harder to do, but there's no major impediment to achieve what can be achieved in a language based say on the CLR.
Why waste time writing a compiler when you can leverage much of the work already done to optimize .NET? If the clients don't have it, make your installer download it and be done with it.
It's much harder to get enough of a .NET runtime together for a new platform than it is to lean on a platform compiler and binary toolchain which must already exist. It's all very well saying "just download the installer," but that won't get my nemerle code running on my phone.
Re: Nemerle 1.0
#16Beautifully written intro that gave me a complete feel for the language. I think that it is a really difficult thing, to communicate that well.
All the best ! I hope Nemerle becomes a fantastic option on the .NET platform. Though, with the speed that Microsoft likes to develop C#, it might most probably end up looking like this.
Re: Nemerle 1.0
#17Earlier quoted context omitted.
Why waste time writing a compiler when you can leverage much of the work already done to optimize .NET? If the clients don't have it, make your installer download it and be done with it.
It's much harder to get enough of a .NET runtime together for a new platform than it is to lean on a platform compiler and binary toolchain which must already exist. It's all very well saying "just download the installer," but that won't get my nemerle code running on my phone.
What phone? Chances are Mono run there...
Re: Nemerle 1.0
#18Earlier quoted context omitted.
Exactly. AFAIK, it has small core language and all other constructions like if/else, while, for, foreach etc are made with macros. I think that Nemerle is Lisp macros + static types + OCaml (algebraic data types, pattern matching) + .Net ecosystem (even Visual Studio support).
how does it square typing with macros? is it typed after macro application?
There are different "macro stages" to allow macro application on both typed and untyped source.
Re: Nemerle 1.0
#19It looks all nice and well, but why can't languages these days be compiled ? I reckon it's way harder to do, but there's no major impediment to achieve what can be achieved in a language based say on the CLR.
Compiled in native? CLR compile IL before execution.
In the next version of Nemerle we plan to create Interchangeable back-ends: http://code.google.com/p/nemerle-2/wiki/BackEnds?wl=en-US
As one of the variants we consider to create backend for LLVM. At least we think about it.
Re: Nemerle 1.0
#20Earlier quoted context omitted.
how does it square typing with macros? is it typed after macro application?
There are different "macro stages" to allow macro application on both typed and untyped source.
so if macros can operate on typed source and/or on the typed ast tree, do they (the macros) have a type system that guarantees that they will preserve correct typing? or are types still checked agan (globally?) after applying the macro?
what i'm really asking is, is there anything "smart" about how the macro works with the type system?