analyze-source

To check C source code for AmigaOS portability issues, scan the source tree to identify POSIX headers, system calls, and language features that hinder porting to AmigaOS 3.x. This generates a structured porting report classifying issues for remediation.

Identifying POSIX-specific usage blocking an Amiga port involves analyzing the C codebase to flag system calls and headers incompatible with AmigaOS 3.x. The analysis provides a structured porting report to prioritize remediation efforts accurately.

Yes, the Amiga porting analyzer classifies identified portability issues by tiered guidance according to ADR-008. It categorizes blockers into shim, emulation, or redesign classifications, helping prioritize refactoring efforts across large codebases.

Generate a port-readiness assessment for a large C codebase by running the analyzer across the entire source tree. It targets new port initiatives, flags system incompatibilities, and delivers a reproducible assessment report to stakeholders.

Yes, you can evaluate source code for Amiga 3.x compatibility before starting a new port. The analyzer targets new port initiatives and assesses port-readiness by scanning headers, system calls, and language features across the codebase.

Limitations when scanning C source trees for AmigaOS porting risks include its strict focus on C language features, POSIX headers, and system calls. It targets AmigaOS 3.x specifically and provides tiered remediation guidance rather than automated code fixes.