Enter your mobile number or email address below and we'll send you a link to download the free Kindle Reading App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry.
> Shop now
For someone wanting to learn how compilers work and, specifically, how the Mono compiler works, this book isn't just bad. it's downright useless. Frankly, I've seen many free online tutorials and papers that do a FAR better job of explaining how compilers work.
Out of the 260 content pages, more than half contain a source-code listing of parts of the Mono C# compiler: The author tries to correlate the Jay parser source to the C# parser implementation, but the result is a densely unreadable fragmented code listing. The 120 pages of code listings contained in this book offer the reader nothing of benefit over reading the Mono C# compiler source itself.
The remaining 100 pages or so consist of lots of class structure diagrams and screenshots, most of which are unnecessary. The actual content that the author has written is poorly structured, far too high-level to be of any use and lacks clear explanation of the implementation of the Mono C# compiler's structure, features and internal workings.
It's almost as though he's summarized several of the CodeProject compiler articles and bound his summary into a book for which he's asking $28.
Finally, I assume that English isn't the author's first language because what text he has written is ... well ... awkward at best and very hard to read.
Before the author publishes any further books for which he charges money, I encourage him to hire an experienced technical editor or, better still, try submitting his future books to a professional technical book publisher to give him a better perspective of the standards expected of a $30 technical book.