It felt like putting on an old leather glove.
He wasn’t a programmer for money anymore. He was a custodian. The city’s water purification grid, installed in 2009 and never upgraded, still ran on a distributed control system written entirely in Object Pascal. Its heart was a single executable compiled by that exact version of RAD Studio. CodeGear RAD Studio 2009 -Update 1-4- 12.0.3420.21218.1
The city’s new IT director, a young woman named Jenna who spoke only in cloud-native buzzwords, had declared the old system “legacy debt” and tried to patch a security hole by replacing a core DLL with a “sanitized” version compiled in a modern Lazarus environment. The result wasn’t a crash. It was a corruption . Pumps in Sector 7 ran at 400% pressure. Valves in Sector 12 refused to close. Digital ghosts of uninitialized pointers flickered across the main terminal. It felt like putting on an old leather glove
He looked at the splash screen one last time. CodeGear RAD Studio 2009 - Update 1-4 - 12.0.3420.21218.1. Not the fastest. Not the newest. But for one more night, it was the most important compiler on Earth. The city’s water purification grid, installed in 2009
“We can’t rewrite forty thousand lines in an hour,” Jenna whispered, watching the pressure gauges spike.
“No,” Aris said, plugging the dusty drive into a pristine Windows XP machine he kept in a Faraday cage. “The original RTL—the Run-Time Library—had a specific quirk. The TList.Sort method in Update 4 uses a non-stable QuickSort. Update 3 used Merge Sort. Every compiler after 12.0.3420.21218.1 changed the memory alignment for ShortString from 1-byte to 4-byte. The DLL you replaced expects pointers to be misaligned by three bytes.”
He injected a single inline assembly block into the GetWaterFlow function:
