無料のKindleアプリをダウンロードして、スマートフォン、タブレット、またはコンピューターで今すぐKindle本を読むことができます。Kindleデバイスは必要ありません。
ウェブ版Kindleなら、お使いのブラウザですぐにお読みいただけます。
携帯電話のカメラを使用する - 以下のコードをスキャンし、Kindleアプリをダウンロードしてください。
OK
Write Great Code, Volume 2: Thinking Low-Level, Writing High-Level ペーパーバック – 2006/3/24
The second volume in the Write Great Code series supplies the critical information that today's computer science students don't often get from college and university courses: How to carefully choose their high-level language statements to produce efficient code. Write Great Code, Volume 2: Thinking Low-Level, Writing High-Level, teaches software engineers how compilers translate high-level language statements and data structures into machine code. Armed with this knowledge, a software engineer can make an informed choice concerning the use of those high-level structures to help the compiler produce far better machine code--all without having to give up the productivity and portability benefits of using a high-level language.
- 本の長さ634ページ
- 言語英語
- 出版社No Starch Press
- 発売日2006/3/24
- 寸法17.78 x 3.81 x 23.5 cm
- ISBN-101593270658
- ISBN-13978-1593270650
登録情報
- 出版社 : No Starch Press; 第1版 (2006/3/24)
- 発売日 : 2006/3/24
- 言語 : 英語
- ペーパーバック : 634ページ
- ISBN-10 : 1593270658
- ISBN-13 : 978-1593270650
- 寸法 : 17.78 x 3.81 x 23.5 cm
- カスタマーレビュー:
著者について
著者の本をもっと発見したり、よく似た著者を見つけたり、著者のブログを読んだりしましょう
他の国からのトップレビュー
This book is not a cookbook for writing better code. Hyde explains why certain programming constructs are better than others (and in what cases), and backs it up with evidence from the assembly code (that is the entire premise of the book). Finally, solid proof of (and against) what I've been hearing all along from instructors and other programmers on message boards or face-to-face communication. That in mind, it would have been nice to have a summary of the tips at the end of the chapters, or the end of the book, as a quick-reference kind of thing. These concepts are the perfect thing to consider when fine-tuning your code. I take the stance that if you fine-tune as you go, you have less work later, so I took notes as I read and have started implementing changes for the better (with evidence that it is better) in some of my coding.
Does anyone write code in Pascal anymore? Seriously? Hyde discusses examples in C/C++ and Pascal for the most part (favoring Pascal, by my estimation), so it is nice that the book is language-independent for the reader. The assembly examples in the book are in 80x86 and PowerPC...I think it would have been better to release two versions of this book, one where the assembly is 80x86 (because it is so ubiquitous, if for no other reason), and then another where the assembly is in PowerPC assembly. I didn't pick this up to become an assembly language programmer, and quite frankly, the PowerPC examples just confused me. It looks like my cat stepped on my keyboard and it appeared in print.
The tone of the text is sometimes condescending (especially in the first 5-6 chapters), with a not-so-subtle "real men only code in assembly" message. It seriously reminds me of my parents/grandparents whining about how hard they had it growing up...walking barefoot to school in the winter...and only having assembly to work with in writing programs.
So by the end of this book, I think I have met Hyde's goal for the readers. I can't sit down and write an assembly program, but I can read enough assembly to compare different versions of my high-level program to say what is better. As the subtitle suggests, I am "thinking low-level" now as I write my programs (in C...which most programmers would call low-level). I suggest "actively" reading this book and coding up a few examples with your compiler and examining the output, following along in the text. Doing that really made the material click for me.
Overall, it's a good book and definitely worth it. This is a long one though, and takes some time to digest. See you in volume 3!
After reading the text your understanding of software/hardware interface will be improved by several orders of magnitude.
The only small annoyance is the fact that a lot of times Mr Hyde start the discussions on various topics using HLA listings as example and even if he provide details on MASM/TASM applications he does so comparing these to HLA. Hence you have to always study the HLA examples ( HLA is some kind of low-level language the author developed ).
Since I'm not interested in HLA ( probably like a lot of the readers out there ) I did not like the ( small ) additional effort it required.
Overall this book is a little gem.