Beyond the core APL language, tools are provided both at the language-level (for example, system functions) and as tools written in APL for general programming, system interaction and interoperation, and application development tasks.
Most tools listed here are supplied and maintained by Dyalog Ltd, including tools in our GitHub repositories (see Dyalog on GitHub for assistance getting started with GitHub).
Tools from external GitHub repositories are maintained by their owners.
Tools marked with * are not included with installations of Dyalog. Instructions for obtaining these tools are in their documentation.
Tools marked with † are available as repositories under Dyalog-Labs on GitHub. These are experimental tools which, although Dyalog Ltd will respond to logged issues, are not subject to the same support guarantees as other tools produced by Dyalog Ltd.
Write, run and debug Dyalog applications using the Integrated Development Environment (IDE) for Microsoft Windows.
The recommended IDE for non-Windows desktops or for Windows developers who need to debug code running on remote systems, including WSL.
Remotely connect to an interpreter over a network on any platform.
Link keeps APL source in text files synchronised with the contents of the active workspace, allowing you to select freely between the editors built into the Dyalog IDEs or external editors in tools like VS Code, and also use source code management tools and coding agents on live applications.
User commands are tools that are available at any time, in any workspace, as extensions to the Dyalog development environment. In addition to the user commands that are built into Dyalog, you can add your own, written in APL.
Run Dyalog and deploy applications using Docker containers.
Jupyter kernel for Dyalog APL. Create, render and interact with Dyalog Jupyter notebooks.
Expose APL applications as JSON or REST web services.
Cross-platform utility for communicating with WebSocket servers.
Wraps Dyalog component files in a client/server framework, for enhanced security and performance. DFS is licensed separately from Dyalog. Don’t forget to remove uae-toc-hide-heading
⎕CSVRead data from CSV files and text as APL arrays; write APL arrays to CSV format and files.
⎕MAPHandle very large data volumes by memory-mapping files to virtual APL arrays.
Example workspace with functions to load and save data from SQL, CSV, Microsoft Excel, and XML data sources.
To load loaddata.dws, enter the following within a Dyalog Session: )LOAD loaddata
⎕NAInterface to compiled libraries (.dll, .so, .dylib, .a), for example, those written in C/C++.
Interface to LAPACK and FFTW to compute eigenvalues, eigenvectors, and Fast Fourier Transforms.
The .NET interface supports .NET and Microsoft .NET Framework.
Create and use instances of .NET classes. Define new .NET classes in Dyalog that can be used from other .NET-supporting languages, for example, C#.
Automate Microsoft Office automation and interact with COM/ActiveX objects embedded within applications from Dyalog.
Automate the use of web browsers using Selenium WebDriver.
Create cross-platform graphical user interfaces. GUI object for rendering HTML, CSS and JavaScript using the Chromium Embedded Framework.
&) is a lightweight method to launch “green threads” for doing multiple time‑consuming (but not compute‑heavy) tasks in parallel. Execute code in parallel CPU threads on one or more machines.
The .NET Task class can be used directly from Dyalog through the .NET interface.
Template for running a Dyalog application as a Microsoft Windows service.
Exchange code between Dyalog and other APL systems.