Mon premier blog

Build Your Own .NET Language and Compiler by Edward G. Nilges

Build Your Own .NET Language and Compiler Edward G. Nilges ebook
Format: chm
Page: 408
ISBN: 1590591348, 9781590591345
Publisher: Apress

But despite The build is orchestrated by a build script, which is essentially just another piece of Fantom code. You don't test the .NET StreamWriter class to make sure it writes to a stream; you test the code you've written to make sure it writes the right thing to the stream. Net are also leveraging powerful .Net platform capabilities, on Windows. You wouldn't build your whole system with a DSL, but, like the 5ESS switch, you could use it to code a critical function in a way that is easier to understand and maintain and, therefore, ensure its quality. I would build a language/compiler-environment that would make it easy to plug all this in as features. This applies to all language features, standard library functions and classes, and public APIs. I will start with a language definition, explore compiler architecture, and then walk you through the code generation subsystem that spits out a .NET assembly. Functional languages are killer at creating DSLs. If you have worthless tests covering essentially non-functional code, then neither the compiler nor your coverage tool will ever be able to say “this property doesn't appear to be used by anything”. One interesting example NET CLR (and other platforms). NET Framework APIs that are required to build your own .NET compiler. Compilation for JVM, .Net and JavaScript are currently supported, and given the infrastructure they've put into place, it should be possible to target other platforms as well. If a project requires lots of concurrency/parallelism, its own language, or lots of math, you should think functional programming. Fantom is a bit different from the languages we looked at previously--including Ceylon, Kotlin, Xtend, Groovy and even Java 8's new lambdas -- as it targets multiple platforms.