The following table outlines different approaches for reading this book.
You are | You want to | Recommendation |
---|---|---|
New to programming | Learn everything you can | Read the entire book. |
New to programming | Learn Delphi | Read chapters 1 to 28 and skip the C++ sections. |
New to programming | Learn C++ | Read chapters 1 to 28. You’ll have to read the Delphi and C++ sections of each chapter, because the Delphi sections tell you why and how something works, and the C++ sections tell you how the same thing works in C++. |
New to programming | Learn C# | Read the C++ sections of all chapters in the book, check the chapter’s Delphi section if you don’t understand a particular topic, and finally read Chapters 29 and 30. |
Delphi developer | Learn Delphi | Read chapters that cover topics you’re interested in, and also read Chapters 4, 5, 29, and 30 to learn about cool new things added to the Delphi language. |
Delphi developer | Learn C++ | At least skim the Delphi section of each chapter and more thoroughly read the C++ section. |
Visual Basic developer | Learn everything | At least skim through the first six chapters to learn Delphi and/or C++ syntax, then read the rest of the chapters thoroughly to learn about sets, file I/O, and OOP. Skim the VCL chapters to learn about the differences between Visual Basic’s intrinsic controls and Delphi’s VCL controls, and pay special attention to Chapters 24 to 27 to learn how to build your own components. |
C/C++ developer | Learn C++ | If you already know C/C++, you can start reading the book from Chapter 11 to learn about the VCL framework and the reserved words and constructs specific to Borland’s C++Builder. |
C/C++ developer | Learn Delphi | Skim the Delphi sections of each chapter and read the C++ sections more carefully since the C++ sections usually point out the differences between the two languages. |