25 years ago, your Delphi code was state of the art.
It powered critical systems, delivered real business value, and it still works today.

But here’s the truth no one likes to admit:
🕰️ Legacy Delphi systems age quietly.
⚠️ Old libraries pile up.
⚠️ Risky database queries stay hidden.
⚠️ Technical debt grows — until one day, it’s a serious liability.

I’ve seen enterprises and government agencies with millions of lines of Delphi code. Sometimes even 100M+ lines still running in production. The code works… but no one really knows what’s inside.

That’s why we built the Delphi Legacy Code Risk Assessment Tool.
👉 A scanner designed by Delphi experts, powered by decades of modernization experience.

What it does:
✔️ Scans any size codebase — from 1M to 100M+ lines
✔️ Works across all Delphi versions (Borland → Delphi 13)
✔️ Maps dependencies, units, components, and database integrations
✔️ Exposes obsolete code, unused libraries, risky queries, and hidden debt

For CTOs, architects, and engineering leaders, this isn’t just about clean code.
It’s about security, stability, and modernization clarity.

Your Delphi code might still run.
But is it healthy?

👉 Run a free Legacy Code Risk Assessment today, and find out: https://delphiparser.com/product/code-dependencies-analyzing-wizard-evaluation-edition/

Every few months someone posts, “We’re planning to migrate our old Delphi app - any tips?”
And I always ask the same question: why?

Unless your system is broken beyond repair, migrating just because it’s “old” is often the worst technical decision you can make.
Here’s why.

💰 1. Cost vs. Value

Rewrites are money pits. You’ll spend months (or years) rebuilding what already works — just to end up with the same business logic in a shinier language. The ROI is almost always negative unless your current system is collapsing.

🧩 2. Stability Has Value

Delphi code that’s been running for 20+ years has one key property: it works.
It’s been debugged, battle-tested, and optimized through real use. Throwing that away for a framework still figuring itself out is the definition of risk.

🧠 3. Institutional Knowledge

Your existing code encapsulates years of domain expertise that no documentation can fully capture. Rewriting means relearning — and inevitably, forgetting things that were solved long ago.

⚙️ 4. Performance and Footprint

VCL apps are native, fast, and self-contained. No web stack, no 15 dependencies, no container orchestration. The lighter it is, the less it breaks.

🔒 5. Platform Compatibility

Windows is still backward-compatible. Even Delphi 3 apps often run fine on Windows 11.
Microsoft has done the hard work of keeping your binaries alive — why fight that?

🧭 6. Migration ≠ Modernization

Rewriting code doesn’t modernize your business. If the goal is security, integration, or compliance — you can often get there by incremental updates: patching, isolating components, or adding APIs around the core system.

🧑‍🔧 7. Maintenance Is the Real Challenge

The true problem isn’t Delphi — it’s the loss of people who understand it.
Train new devs. Document the code. Keep one or two Delphi experts on retainer. That’s cheaper, safer, and smarter than rewriting an entire platform.

🕰️ 8. “Because It’s Old” Is Not a Reason

If COBOL still runs banks, Delphi can still run your company.
You upgrade when you must, not when marketing tells you to.

🧭 The Real Question

Don’t ask, “Should we migrate?”
Ask, “What problem are we solving?”
If you can’t name a real, measurable problem, you don’t need a migration — you need maintenance.

Delphi doesn’t need saving. It needs stewardship.
Sometimes the most modern thing you can do… is simply keep what works.

https://delphiparser.com/product/code-dependencies-analyzing-wizard-evaluation-edition/

Transforming Legacy Delphi Codebases into Regulatory-Compliant CycloneDX SBOMs The regulatory clock is ticking. Under the Cyber Resilience Act (CRA), providing a partial or inaccurate Software Bill of Materials (SBOM) isn't just a technical blind spot - it’s a massive legal and compliance risk for enterprise software.

Generic SCA tools and basic binary scaners completely drop the ball when it comes to mature, 20-year-old Delphi codebases. They miss dynamic linkages, get choked up by complex conditional directives ({$IFDEF}), or completely ignore multi-platform Linux architectures (.so).

We don't sell illusions - We deliver the truth, the whole truth, and nothing but the truth.

To help enterprise environments achieve 100% compliance at scale, we have just pushed a brand-new release to the Delphi Parser SBOM Compliance Engine featuring Automated 3rd-Party Data Vendor Mapping.

What’s New in the Latest Release:

Automated 3rd-Party Data Vendor Mapping: You can now instantly map legacy, 3rd-party component folders (e.g., JEDI/JVCL, Spring4D, DevExpress, TMS) directly into a fully structured, valid CycloneDX SBOM file, removing manual tracking from your pipeline.

Tailored Source Parsing & Mapping: Our compiler-level frontend handles proprietary frameworks, include files ({$I}), and complex conditional configurations to accurately map the exact skeleton of your active code paths.

Pre-configured PE Header & Manifest Scanning: The engine now reads metadata (Component Name, Precise Version, Architecture) directly from compiled binaries (.dll, .exe, .dpk, .so) and root package manifests.

Open-Source & Commercial License Mapping: Automated extraction of license footprints directly into your final CycloneDX report to eliminate compliance vulnerabilities.

Built for the Enterprise CI/CD Pipeline - Whether you run a massive local trunk or complex distributed sub-versions spanning over 10 Million lines of code, the Delphi Parser headless CLI operates silently and flawlessly inside FinalBuilder, Continua, Jenkins, or DevOps pipelines.

Stop guessing what’s hidden inside your legacy binary matrices. When the market has no standard, we build it.

👉 Download the latest release or request an Enterprise Trial/Forensic Architecture Deep-Dive for your team: https://thedelphiparser-fhix1gvbc7.live-website.com/product/delphi-parser-sbom-analyzer-free-edition/

https://blogs.embarcadero.com/14-questions-about-kai-your-guide-to-everything-about-the-new-agentic-ai-assistant-inside-the-ide/

Call me crazy, but is not possible to calculate factorial of 100 in Delphi?

100!

Edit: Thanks all !

The Delphi party is officially over - The hangover? Global cyber regulations.

For the past 30 years, we’ve enjoyed ultimate freedom in Delphi. We copied components, tweaked third-party code (anyone remember RxLib, Indy, or old BDE hacks?), and as long as the system compiled – everybody was happy.

Not anymore.

With global mandates like the EU’s Cyber Resilience Act (CRA) hitting the fan, the era of “Black Box” legacy code is dead. Software vendors, from enterprise giants to small SMBs selling inventory or POS systems, are now legally required to provide a certified Software Bill of Materials (SBOM) for every release.

If you are running millions of lines of legacy Delphi code, you are likely sitting on a regulatory time bomb.

Generic scanners (like DerScanner or cloud-based SCA tools) are completely blind to custom Delphi logic and hidden dependencies. They will either give you a false sense of security or fail your audit completely.

That’s why I built the Delphi Parser SBOM Analyzer.

And because I’m tired of corporate subscription games, I’m launching the Delphi Parser SBOM Analyzer - Professional Edition as Unlimited Lines & Unexpired License.

👉 One-Time Investment: No annual subscriptions, ever.
👉 Unlimited Lines of Code: Handles massive, multi-million line codebases with ease.
👉 100% On-Premise / Air-Gapped: Your source code never leaves your network.
👉 Instant Compliance: Generates machine-readable, certified CycloneDX reports (JSON/XML) ready for your auditors.

If you want to turn your technical debt into a certified asset without burning millions on manual refactoring:

Run it today. Comply tomorrow.

👇 Get the Permanent Professional Deal here:

I want to clear something up that keeps coming back again and again in the Delphi community.

A lot of people think that if companies migrate their Delphi systems to C#, it means Delphi developers will lose their jobs or Delphi itself will somehow “die.”

I think the opposite is true.

Migration actually INCREASES the need for Delphi developers.

Here’s why:

• Most Delphi codebases are huge, messy, and 20+ years old.

• C# devs can’t just pick them up and rewrite them.

• AI tools can help, but they can’t magically understand old business logic.

• The only people who can guide the migration… are Delphi developers.

These migrations take years, sometimes decades.
And during that entire time, companies depend on Delphi experts who actually understand the system they’re trying to replace.

So no — moving to C# doesn’t kill Delphi.
If anything, it guarantees steady Delphi work for a very long time and makes Delphi skills more valuable, not less.

I’m pro-Delphi, and I genuinely believe this is good for the community.
Instead of fearing migration, we should see it for what it is:

A long-term job opportunity that only Delphi developers can fill.

Hi everyone,

Quick question for anyone managing security compliance and SBOMs for Delphi projects:

Is there an active, dedicated Delphi CVE repository or vulnerability feed out there? one that tracks RTL, VCL, commercial, and open-source third-party components (both legacy and modern)? Or is everyone forced to rely on generic scanners pulling from NIST NVD/OSV, and then manually filtering through a sea of irrelevant false-positives to keep auditors happy?

Why we're asking: With new regulatory frameworks like EU CRA (Cyber Resilience Act) and DORA enforcement timeline approaching (late 2027), machine-readable SBOMs and automated VEX justifications are transitioning from "nice-to-have" to a mandatory legal requirement for software vendors.

To address this, we are finalizing the development of our new Delphi Parser VEX Defender - a dedicated security and compliance pipeline built specifically for the Delphi ecosystem.

How the pipeline works:

1. AST-Based SBOM: Generates a clean CycloneDX SBOM from your actual Delphi source code (uses, DFM, .dproj), eliminating non-existent dependencies and text-matching guesswork.

2. Multi-Source CVE Aggregation: Continuously pulls raw vulnerability feeds from NVD, OSV.dev, GHSA, and vendor security bulletins.

3. Centralized & Local Security DB: Aggregates and indexes a dedicated database (available both via central server and as a local offline DB for air-gapped environments) mapped directly to Delphi components, VCLs, and native C/C++ DLL wrappers.

4. Automated Noise Reduction: Filters out ~99.9% of non-relevant false positives (Java, .NET, Linux-only, or non-native threats) before they pollute your reports.

5. Deep AST & Call-Graph Reachability: When a relevant vulnerability is identified, the engine analyzes your Delphi source code (uses, DFM, .dproj, and AST call graphs) to verify whether the vulnerable code path is actually reachable and executed in your application.

6. Auditor-Ready SBOM & VEX: Automatically generates clean CycloneDX SBOMs and compliant VEX (Vulnerability Exchange) JSON files (not_affected / code_not_reachable).

Before we finalize our aggregation pipeline, we’d love to ask the community: Are there any Delphi oriented security archives, vendor bulletins, or community-driven lists we should integrate into our database?

Would love to hear how your teams are preparing for CRA/DORA compliance today!

We already have Python, JavaScript, and a hundred others. So why MIMERCode?

Because the world changed. Large Language Models now generate code every day — inside chatbots, inside automation pipelines, inside tools that non-programmers use to build things. And the languages those LLMs target were designed decades ago, for humans typing at keyboards. They are full of ambiguity, implicit behavior, and silent failure modes that LLMs stumble over constantly.

MIMERCode was designed with three goals:

1. Readable by everyone. Plain English keywords. No semicolons. No invisible whitespace rules. Every block closes with end. A business analyst can read MIMERCode and understand what it does.

2. Writable by AI (and humans). The syntax deliberately matches what LLMs already know from Python and JavaScript. F-strings, slicing, dictionaries, lambdas — they all work the way an LLM expects. Case-insensitive keywords mean True, true, and TRUE all work.

3. Secure by design. Contracts validate data at boundaries. Channels sandbox all I/O. Sensitive fields are sealed automatically. There is no way for code — human or AI-generated — to silently access files, networks, or databases without explicit permission.

4. Selfcontained. Everything needed to make advanced selfcontained command line tools, web servers and even full featured fluent stunning looking GUI applications.

my exams is in a week and I really need to pass(im very lost as my teacher isnt great. does anyone have any advice?

Hi i just wanna ask if a for loop runs 7 times to get 7 random numbers. How do i get each random number apart from the loop to process? PLS help me