Cross-platform software libraries and APIs
Qt Creator IDE and productivity tools
UI Design tool for UI composition
for Qt projects
Digital advertising for UI apps
Usage intelligence for embedded devices
GUI test automation
Code coverage analysis
Test results management and analysis
Software static code analysis
Software architecture verification
The latest version of Qt.
Make the most of Qt tools, with options for commercial licensing, subscriptions, or open-source.
Explore Qt features, the Framework essentials, modules, tools & add-ons.
The project offers PySide6 - the official Python bindings that enhance Python applications.
Qt empowers productivity across the entire product development lifecycle, from UI design and software development to quality assurance and deployment. Find the solution that best suits your needs.
Insight into the evolution and importance of user-centric trends and strategies.
Learn how to shorten development times, improve user experience, and deploy anywhere.
Tips on efficient development, software architecture, and boosting team happiness.
Get the latest resources, check out upcoming events, and see who’s innovating with Qt.
Call cycles during runtime are hazardous. Functions call each other and therefore pose the risk of endless recursion. If a direct cycle occurs, there is a risk the system can crash at any time. While short cycles may be recognized and resolved – even by the developers – during a review, it is virtually impossible a human observer to detect longer cycles when reviewing manually. Axivion Static Code Analysis helps you reliably verify freedom from cycles.
The analysis recognizes cyclical dependencies on different levels. It can identify and monitor not only call cycles (recursions), but also component cycles and include cycles.
Include files often use each other. This produces mutual dependencies between the files and the resulting build problems. In addition, it hinders the developer in understanding the code.
Detecting these kind of cycles too late in the development process, often means there is no simple way to resolve them as the cycle has become part of the intended functionality. Continuous verification prevents this from happening. As these are merely a loop in the call hierarchy for Axivion Statc Code Analysis, they can be easily identified.