Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 8,315 papers for “Legacy code”

Legacy Code

C.A.R. Hoare · Oxford University Research Archive (ORA) (University of Oxford) · 2000

Cited by 0

Vibe code is legacy code

Stephen Turner · Front Matter · 2025

I liked Steve Krouse's essay, "Vibe code is legacy code." It helped crystalize some half-baked thoughts I have on vibe coding. Here's an excerpt.Subscribe now <strong> Maintainability and vibe are inversely correlated </strong> I've been using GitHub copilot and chatbots for code for years, and I've written about them a lot here.

Cited by 0Open access

Vibe code is legacy code

Stephen Turner · Front Matter · 2025

I liked Steve Krouse's essay, "Vibe code is legacy code." It helped crystalize some half-baked thoughts I have on vibe coding. Here's an excerpt.Subscribe now <strong> Maintainability and vibe are inversely correlated </strong> I've been using GitHub copilot and chatbots for code for years, and I've written about them a lot here.

Cited by 0Open access

Testing legacy code

John Arundel · Front Matter · 2024

How do you rescue a legacy codebase that has no tests? Let's look at some techniques for clawing your way back to maintainability, one test at a time.

Cited by 0Open access

Uncovering Legacy Code

van Spaendonck, Philippus Henricus Maria · TU/e Research Portal · 2025

One of the largest and most widespread issues in the IT world is that of legacy software, i.e. code that is no longer understood to the level required to continue its effective and non-erroneous usage. Regaining sufficient knowledge of legacy software systems, and maintaining them is an arduous and costly process. We believe that currently used textual documentation techniques are incapable of properly capturing knowledge on software and insufficient for handling modern day software complexity and are thus the main cause of legacy software. We nominate formal models as the proper replacement of current documentation techniques. Formal models allow us to capture and document software without, far exceeding the expressive capacities of current solutions. Formal models also enable us to automatically reason about the correctness of said software systems. The problem with introducing formal models to capture the vast amount of unmodelled software out there is however two-fold: First, there is simply too much software out there to allow for manually modelling every software component. Second, once a model has been acquired, we must ensure that the model accurately captures the behaviour of the modelled system. This thesis thus consists of two parts: `Extracting understandable models' and `Verifying the correctness of extracted models. 'In the first part of the thesis we introduce the novel SSTraGen tool, which we demonstrate, through a case study, to be capable of automatically extracting formal models from industrial C++ code. We also define the so-called diamond-pattern, which can often be seen in parallel systems, and introduce an algorithm for finding and replacing these patterns patterns towards improving the readability of general models. The second part of this thesis focusses on verifying the accuracy of models with respect to their implementation. Here, the specific contributions are extending the cones-and-foci proof framework towards divergence-preserving branching-bisimulation, speeding up model-based testing using greedy on-the-fly test case selection, and relating the stable failure refinement relation and ioco relation used within model based testing.

Cited by 0Open access

Challenges of legacy code

Mayuri Wagh, Prof. Pavan Malani, Dr. Archana Bendale · Zenodo (CERN European Organization for Nuclear Research) · 2025

Domain code insinuates to out of date or secured source code that remains in utilize insides computer program frameworks in appear abhor toward of its age or require of congruity to advanced movement hones. In show disdain toward of the truth that such code routinely plays a basic allocate in each day commerce operations, it presents differing challenges for engineers and organizations. The consider concludes with recommendations for overwhelming overseeing with of domain frameworks through advanced hones such as refactoring, testing, and disengaged orchestrate.

Cited by 0Open access

Working with Legacy Code

Abhishek Mishra · Apress eBooks · 2017

If you have been for a few years, chances are that you have been brought on to add new features to an existing app with a large code base that has been built over a few years and has been worked on by dozens of developers, most of whom have moved on to other projects.

Cited by 0

LLM-Powered Legacy Code Modernization

Sahil Sanas, Arya Naik, Aditya Veerkar et al. · 2025

Legacy COBOL and C systems are still widely used in industries, yet they are increasingly costly, insecure, and incompatible with modern platforms. Traditional modernization methods, although effective, often require significant time and resources and carry high risks of disruption. This paper proposes a scalable alternative that leverages Large Language Models (LLMs) within a structured multi- agent framework, guided by the “7Rs of Modernization.” The frame- work comprises three agents: an Analysis Agent that interprets and maps legacy code, a Coder Agent that generates modern equivalents, and a Review Agent that validates correctness, security, and compliance through iterative feedback. By automating much of the migration process, the proposed approach enables faster, more transparent, and less risky mod- ernization. It helps enterprises transition from outdated systems to modular, secure, and cloud-ready solutions, offering a cost- effective and future-proof pathway to digital transformation.

Cited by 0Open access

LAMMPS as a Legacy Code.

Plimpton, Steven J. · OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information) · 2017

Abstract not provided.

Cited by 0Open access

LucaDeSiena/MuRAT: Legacy MuRAT3.0 Code

Luca De Siena, mreissuf, Yi Zhang et al. · Zenodo (CERN European Organization for Nuclear Research) · 2026

What's Changed Update README.md by @LucaDeSiena in https://github.com/LucaDeSiena/MuRAT/pull/40

Cited by 0Open access

LucaDeSiena/MuRAT: Legacy MuRAT3.0 Code

Luca De Siena, mreissuf, Yi Zhang et al. · Zenodo (CERN European Organization for Nuclear Research) · 2026

What's Changed Update README.md by @LucaDeSiena in https://github.com/LucaDeSiena/MuRAT/pull/40

Cited by 0Open access

Upcompiling legacy code to Java

Fässler, Urs · Repository for Publications and Research Data (ETH Zurich) · 2012

This thesis investigates the process of “upcompilation”, the transformation of a binary program back into source code. Unlike a decompiler, the resulting code is in a language with higher abstraction than the original source code was originally written in. Thus, it supports the migration of legacy applications with missing source code to a virtual machine. The result of the thesis is a deeper understanding of the problems occurring in upcompilers. To identify the problems, we wrote an upcompiler which transforms simple x86 binary programs to Java source code. We recover local variables, function arguments and return values from registers and memory. The expression reduction phase reduces the amount of variables. We detect calls to library functions and translate memory allocation and basic input/output operations to Java constructs. The structuring phase transforms the control flow graph to an abstract syntax tree. We type the variables to integers and pointers to integer. In order to optimize the produced code for readability, we developed a data flow aware coalescing algorithm. The discovered obstacles include type recovery, structuring, handling of obfuscated code, pointer representation in Java, and optimization for readability, to only name a few. For most of them we refer to related literature. We show that upcompilation is possible and where the problems are. More investigation and implementation effort is needed to tackle specific problems and to make upcompilation applicable for real world programs.

Cited by 0Open access

Perl Medic: Transforming Legacy Code

Peter Scott · CERN Document Server (European Organization for Nuclear Research) · 2004

Cure whatever ails your Perl code! Maintain, optimize, and scale any Perl software... whether you wrote it or not Perl software engineering best practices for enterprise environments Includes case studies and code in a fun-to-read formatIf you code in Perl, you need to read this book.-Adam Turoff, Technical Editor, The Perl Review.Perl Medic is more than a book. It is a well-crafted strategy for approaching, updating, and furthering the cause of inherited Perl programs.-Allen Wyke, co-author of several computer books including JavaScript Unleashed and Pure JavaScript.Scott's explanations of complex material are smooth and deceptively simple. He knows his subject matter and his craft-he makes it look easy. Scott remains relentless practical-even the 'Analysis' chapter is filled with code and tests to run.-Dan Livingston, author of several computer books including Advanced Flash 5: Actionscript in ActionBring new power, performance, and scalability to your existing Perl code!Today's Perl developers spend 60-80% of their time working with existing Perl code. Now, there's a start-to-finish guide to understanding that code, maintaining it, updating it, and refactoring it for maximum performance and reliability. Peter J. Scott, lead author of Perl Debugged, has written the first systematic guide to Perl software engineering. Through extensive examples, he shows how to bring powerful discipline, consistency, and structure to any Perl program-new or old. You'll discover how to: Scale existing Perl code to serve larger network, Web, enterprise, or e-commerce applications Rewrite, restructure, and upgrade any Perl program for improved performance Bring standards and best practices to your entire library of Perl software Organize Perl code into modules and components that are easier to reuse Upgrade code written for earlier versions of Perl Write and execute better tests for your software...or anyone else's Use Perl in team-based, methodology-driven environments Document your Perl code more effectively and efficientlyIf you've ever inherited Perl code that's hard to maintain, if you write Perl code others will read, if you want to write code that'll be easier for you to maintain, the book that comes to your rescue is Perl Medic.On the Web SiteDownload all of the book's sample code from .

Cited by 0