Static Analysis of APL for Tooling and Compliance
summary
Dyalog presents a static-analysis pipeline that parses APL with the Co-dfns parser to produce a tree/vector model, runs rule-based searches that find exact code patterns (e.g. prototype-induced empty-array bugs and tainted-data flows across two distinct indexing sites), and emits CI-friendly rules and patches for mechanical refactors (some tacet→defun rewrites). It already integrates with SonarQube integration and can output audit artifacts for security, migration and compliance, with known limits around undecidable analyses.
AI-written summary · about
chapters (6)
- 0:00What is static analysis?
- 5:01A concrete example
- 9:30Analysing the Co-dfns parser output
- 19:03Adapting to a specific application
- 23:26A static analysis tool for APL notation
- 28:24Questions
related talks
15mAutomatic Synthesis of Data-Flow Analyzers
58mThe Intersection of Architecture and Implementation
01h 06mOn-The-Fly Verification via Incremental, Interactive Abstract Interpretation wi...
19mVerifying Dafny Contract Integrity
26mDetecting and Mapping Code Defects Introduced by Generative AI Using CodeLogic & Neo4j
42mContemporary Automatic Program Analysis
15mStatic Detection of Silent Misconfigurations with Deep Interaction Analysis
31mCooperative Specification via Composition Control