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

Build Your Own .NET Language and Compiler



Download eBook




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


This looks like it's going to happen soon. I even wrote my own BASIC like compiler, using the Abacus Basic compiler (for C64) just so I could create an even faster basic so I could write a video game. At first I looked around like a madman in the CLR-assemblies trying to find the classes I needed to build my own DLR language, but I couldn't, and after which I came up on the following statement in the Discussion-tab of the dlr codeplex-page found here. The facts: IronRuby and IronPython both use NET 4.0, I'd use C# as the implementation language and use the DLR as a library for simplifying common compiler tasks. Phalanger is compiler that generates .NET assemblies from PHP code, so it runs in a .NET virtual machine. Scott Hanselman dubbed JavaScript the assembly language for the web and the number of compilers targeting JavaScript seems to confirm that statement. Zend may as well come up with their own JIT compiler. The C# developer base is huge, so a native C# compiler will push the language even further to new platforms and projects that are currently unsuitable for development with C#. Wouldn't it be nice to still be able to leverage that in your web games? It will enable developers to write ALL Net assembly. First, some clear demarcation about what this book isn't: if you want a book with a really strong theoretical background in compiler design, this isn't it. While there are many attempts at improving NET or Java world. The latest benchmarks seem to indicate that PHP applications compiled by Phalanger execute noticeably faster than when they Others presented more emotional arguments like the fact that core developers have been working for years on the C language code that executes PHP and its extensions. My presentation deals with this issue at length, but a nice summary can be found in the Guile manual: this freedom covers modifying and rebuilding the C code; but if the program also provides an extension language, that is usually a much friendlier and lower-barrier-of-entry way for the user to start making their own changes. Why care about extension languages? In that spirit, I would like to re-make the argument for Guile as the GNU extension language. Summary: Very good for what it does. It is a language that most of us once knew, which we may have forgotten about, which has grown and matured while we have been courting the current generation of programming languages. There ARE products which "post-build" your IL modules to x86 and statically link .NET dependencies. Regardless of where you're coming from, it's likely that you already know one or more languages and you like your development workflow. It is kind of like a young boy, it died a slow death when its .NET cousin came on the scene.

More eBooks: