sirp Posted October 27, 2010 Posted October 27, 2010 IntroductionThis book demonstrates the process of creating a language compiler for the CLR. Itcontains a mixture of generic compiler construction topics and topics specific tocompiling for the CLR.How it came to beFor many years, I wanted to write a compiler. I read, or tried to read, a lot of books on thesubject. Two things about these books consistently turned me off: one, they were, oneand all, written using language familiar to mathematics and computer science students,but Greek (many a time, literally) to the rest of us. Two, almost all of them were full ofinformation about sundry alternate means to read source code and understand it, butcontained precious little information about how to generate machine code, andspecifically machine code for the only kind of machine that I had handy; x86.Then, I hit the jackpot; I read a brilliant article series called "Let's Build a Compiler" byDr. Jack Crenshaw. I love Dr. Crenshaw's approach of learning by doing, showing ONEway of doing things while mentioning that there were others, avoiding jargon untilunavoidable and explaining it lucidly when not, and above all, keeping it simple. Thisarticle series taught me more than all the books I had read so far, and even the booksstarted making more sense after I finished the series. "Let's Build a Compiler", © JackCrenshaw, is definitely recommended reading for anyone who wants to learn about howcompilers are built.by Raj ChaudhuriblogLBCC.pdf
JMC31337 Posted October 27, 2010 Posted October 27, 2010 IntroductionThis book demonstrates the process of creating a language compiler for the CLR. Itcontains a mixture of generic compiler construction topics and topics specific tocompiling for the CLR.How it came to beFor many years, I wanted to write a compiler. I read, or tried to read, a lot of books on thesubject. Two things about these books consistently turned me off: one, they were, oneand all, written using language familiar to mathematics and computer science students,but Greek (many a time, literally) to the rest of us. Two, almost all of them were full ofinformation about sundry alternate means to read source code and understand it, butcontained precious little information about how to generate machine code, andspecifically machine code for the only kind of machine that I had handy; x86.Then, I hit the jackpot; I read a brilliant article series called "Let's Build a Compiler" byDr. Jack Crenshaw. I love Dr. Crenshaw's approach of learning by doing, showing ONEway of doing things while mentioning that there were others, avoiding jargon untilunavoidable and explaining it lucidly when not, and above all, keeping it simple. Thisarticle series taught me more than all the books I had read so far, and even the booksstarted making more sense after I finished the series. "Let's Build a Compiler", © JackCrenshaw, is definitely recommended reading for anyone who wants to learn about howcompilers are built.by Raj Chaudhuribloginteresting... so using vb's compiler vbc, you create another compiler to do your work...up until page 51 the author uses vbchave you made your own compiler and created a hello world exe??
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now