Posts

With Time, All Software Goes South. AI-Written Software Gets There Faster

-
There is no better feeling than creating a brand new code repository. For a brief moment, you will have a nice, clean slate without bugs of any sorts, without hacky workarounds, with none of the sauceless spaghetti and half-baked features you never managed to fully write and maintain, but which eventually turn your codebase into a technical debt obstacle course. But that joyous feeling does not last too long. Bit by bit, and sometimes by leaps and bounds, that nice, clean codebase will start to go south, acquiring some, if not all, of the dreadful issues every developer fears. This kind of deterioration is inevitable. No matter what you do, no matter how careful you or your team are, the growing complexity will take its toll. Yes, the more careful and experienced you are, the slower the decline, but anyone claiming they have a perfect codebase is either delusional or has never worked with large-scale systems in production. At some point, small bugs and issues accumulate, the archite...
Post a Comment
Read more

Excessive Collection Locking

-
As soon as you step into writing multithreaded code, you will need to work with collections in a thread-safe manner. While Delphi provides some basic thread-safe collections for its own use in the RTL and visual frameworks, those are usually not enough. So you will either end up using some third-party thread-safe collection library, or you will be insipired to roll out your own. Making thread-safe collections is not a very complicated task, but if you are not careful, you can easily end up using locking patterns which will look fine at first glance, but can cause excessive locking when used. You will get thread safety, but running at a snail's pace. Considering that modern computers are powerful enough, such code can still run at an acceptable speed, and you might not even notice that you are burning CPU cycles in vain. Thread-safe Collection To implement any thread-safe collection, you will need a lock. While there are many different lock types we can use based on particular n...
Post a Comment
Read more

Delphi 13.1 Update: Windows Arm64EC compiler

-
Image
The Delphi 13.1 update has just been released. One of the most significant new features in this update is the new 64-bit Windows ARM EC compiler. With ARM taking a strong foothold in desktop, laptop, and tablet computers, this is an additional Windows platform which can no longer be ignored. Now, if there is one thing that Microsoft does well, it is compatibility support for existing applications. Which means even your existing 32-bit and 64-bit Intel-based Windows applications will run on the Windows ARM OS. With that in mind, having a Windows ARM compiler at this time may not seem like a mission-critical feature, but this compiler still represents an extremely important milestone in Delphi's evolution. There are several reasons for that. First of all, Delphi developers are primarily Windows developers. Even if we support other platforms, Windows is and will always be our turf. Because Windows ARM EC supports both the VCL and FMX visual frameworks, no matter what kind of Delphi...
Post a Comment
Read more

Using atomic operations to achieve thread safety

-
Atomic operations are ones which can be executed on otherwise-unprotected shared data as a single indivisible step, where no other thread will be able to compromise the consistency of either that shared data or the operation itself. In other words, even for operation logic consisting of multiple, compound operations—steps—being atomic means that all those steps will run as an unbreakable whole on the shared data, and multiple threads will not be able to interfere with each other. Most fundamental atomic operations are actually implemented on the hardware level, and rely on specific CPU instructions to ensure atomicity, but some can also be implemented in higher level code with the help of those atomic primitives. Because hardware support is needed for the most fundamental primitives, atomic operations will be limited to simple data types commonly up to a size of a pointer. Support for atomic operations for larger data sizes—double pointers or even more—is hardware-dependent, and Del...
Post a Comment
Read more

CodeRage 2025: Multi-threaded programming: two problems, you now have

-
Image
 It is a CodeRage season.  Join me next Tuesday, December 2, at 20:00 GMT for my session "Multi-threaded programming: two problems, you now have" and find out how to avoid some common problems when writing multi-threaded code in Delphi applications. Register now!
Post a Comment
Read more

Delphi 13 Florence: 64-bit IDE debugging experience

-
Image
Anyone who has ever debugged a 64-bit application in Delphi, especially one that involves multiple threads, has probably experienced disconnected session issues, or the IDE not showing watch values, or simply getting non-responsive in the middle of a debugging session. The new 64-bit IDE and its LLDB-based debugger provide a solution to such problems. You may no longer have to sprinkle your code with logging code that is otherwise not needed; nor will you have to waste hours trying to catch some error, only for Delphi to die on you when you are two lines of code away from discovering the problem. However, it is not all that peachy. Namely, LLDB has its own quirks. First of all, it is dog slow. It is slow when evaluating breakpoints, it is slow when handling exceptions (even ignored ones), it is slow when it stops at a breakpoint and shows local variable values. The more powerful computer you have, the better the experience will be. While there is still plenty of room for improveme...
Post a Comment
Read more

Universal storage for Delphi procedural types

-
Delphi's procedural types fall into three categories: standalone procedures and functions, methods, and anonymous methods. The variables that can store those types are all different, both in their memory size and their nature. Further differences between various procedural types come from the number of parameters they have and their types, as well as whether they return some result—whether they are functions. Those differences have an impact on how they are invoked, but not on their storage—the variables and their memory layout. Two procedural types will be compatible with each other, if they are of the same category, have the same calling convention, have the same number of parameters (including the return value or lack of it). and those parameters and return value are of the same types and declared in the same order. The declared parameter names can be different, and don't affect this compatibility. Declaring any of those procedural types has some common parts: a type iden...
4 comments
Read more