Using Dyalog’s ⎕JSON for Reliable Data Interchange
Learn how Dyalog’s ⎕JSON function lets you encode and decode JSON without extra libraries, with a worked example, error‑handling tips, and verification steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Dyalog’s ⎕JSON function lets you encode and decode JSON without extra libraries, with a worked example, error‑handling tips, and verification steps.
Goal: ascertain if Dyalog APL releases memory obtained from erased arrays back to the operating system while the session remains active, given that ⎕WA may show recovery while OS process size stays elevated. Uncertainty: documentation notes that the interpreter may retain freed space in its internal heap for reuse, but does not specify when or if that heap i
Determine whether Dyalog APL Free Edition can be used for a low‑traffic commercial web service without violating the license. The free edition documentation states it is intended for learning and non‑production experimentation, allows unlimited code execution, and limits concurrent user sessions, but does not explicitly define the boundary between non‑commer
Goal: Determine whether a pending ⎕DL delay in Dyalog APL’s GUI edition is cancelled when the user closes a MsgBox window, or whether the delay always runs to completion before the alert is displayed. Constraints: The interaction between ⎕DL and asynchronous GUI events is not fully documented; behavior may differ across Windows, macOS, and Linux ports, and r
After moving an application from Dyalog 16.0 to 18.0, I need to reconcile how ⎕SQL handles transaction control. My understanding is that auto-commit versus explicit transaction behavior changed across that boundary, and write operations that previously appeared atomic may now commit partial state before a failure surfaces to the application. The concrete goa
When defining a function whose name contains a space or punctuation, Dyalog APL raises Error 2000: Invalid function name. This error highlights the language’s strict naming rules, which must be respected even when a function is later redefined. During a zero‑downtime migration of a small application, the REPLACE statement is used to swap a function’s definit
The :Save command writes a binary workspace (.ws) that captures the current state of all defined functions, variables, and namespaces, enabling a developer to restore the exact environment later. However, the workspace file does not embed the Dyalog interpreter version or the precise set of loaded DLLs. When a workspace created on a newer interpreter is load
Goal Ensure that deployment failure logs contain legible Unicode characters when diagnosing issues in Dyalog APL. Constraint The documentation does not specify whether ⎕LOGFILE writes UTF‑8 independently of the host console code page or inherits it, leaving uncertainty about how non‑ASCII error messages are recorded. Questions Does ⎕LOGFILE always encode log
In Dyalog APL Server (DAS) 22.12, administrators can enforce password expiration via the PasswordPolicy section of server.cfg . The documentation states that expired passwords prevent new logins, but it does not specify what happens to sessions that are already established when the expiry date passes. This ambiguity is critical for least‑privilege security m