Book Image

Delphi High Performance - Second Edition

By : Primož Gabrijelčič
5 (1)
Book Image

Delphi High Performance - Second Edition

5 (1)
By: Primož Gabrijelčič

Overview of this book

Performance matters! Users hate to use programs that are not responsive to interactions or run too slow to be useful. While becoming a programmer is simple enough, you require dedication and hard work to achieve an advanced level of programming proficiency where you know how to write fast code. This book begins by helping you explore algorithms and algorithmic complexity and continues by describing tools that can help you find slow parts of your code. Subsequent chapters will provide you with practical ideas about optimizing code by doing less work or doing it in a smarter way. The book also teaches you how to use optimized data structures from the Spring4D library, along with exploring data structures that are not part of the standard Delphi runtime library. The second part of the book talks about parallel programming. You’ll learn about the problems that only occur in multithreaded code and explore various approaches to fixing them effectively. The concluding chapters provide instructions on writing parallel code in different ways – by using basic threading support or focusing on advanced concepts such as tasks and parallel patterns. By the end of this book, you’ll have learned to look at your programs from a totally different perspective and will be equipped to effortlessly make your code faster than it is now.
Table of Contents (15 chapters)

The magic of pointers

Our friend, Mr. Smith, has progressed a lot from his first steps in Delphi. Now, he is playing with graphics. He wants to build a virtual reality app that will allow you to walk through the Antarctica forests. While he’s getting some success, he has problems displaying the correct colors on the screen.

A part of his code is producing textures in Blue-Green-Red (BGR) byte order, while the graphics driver needs them in the more standard Red-Green-Blue (RGB) order. He already wrote some code to fix this problem, but his solution is a bit too slow. He’d like to push a frame or two more from the system, and so I promised that I’d help him optimize the converter. I’m glad to do it, as his problem neatly fits into the story of pointers.

A pointer is a variable that stores an address of some data (other variables, dynamically allocated memory, a specific character in a string, and so on). It is always the same size – 4 bytes on...