This week’s collection consists of presentations by members of the development team, and concentrates on language features and development tools that the developers are currently designing or already implementing. Many of these features are likely to be in version 20.0 of Dyalog, which we plan to release in early 2025, about a year after version 19.0 becomes available. In other words, there is still time to comment on these ideas and propose changes or additions…please take a look and let us know your thoughts!<\/p>\n
John Daintree presents an update to the design (and prototype implementation) of so-called Token-by-Token (TBT) debugging, which will make it possible to step through code one primitive at a time rather than one line at a time. This promises to be a wonderful teaching tool, and will also help experienced users debug complex expressions \u2013 especially trains and other tacit constructs.<\/p>\n
In the presentation on “Setting and Getting Variable Values”, Ad\u00e1m Brudzewsky proposes extensions that will simplify (and speed up) a number of frequently-occurring patterns, where application code needs to reference or update variables based on arrays containing variable names. At the moment, most solutions require complicated, inefficient, and uncomfortable uses of the execute primitive (which some code scanners might identify as potentially unsafe).<\/p>\n
Ad\u00e1m’s second presentation also proposes ways to simplify frequently-occurring use cases, this time related to a relatively recent addition to the Dyalog language, the key<\/em> operator ( Peter Mikkelsen proposes a new mechanism for making shell commands from Dyalog. Rather than extending the existing mechanism ( The final talk in this block is by Kamila Szewczyk, a student from Saarland University, who was an intern at Dyalog Ltd this summer. In this whirlwind talk, she covers her implementation of a prototype of an APL Array Notation<\/a> deserialiser, which will be available as an I-Beam in version 19.0, and probably used by Link 4.0. When she needed a break from that project, she created internal experimental builds of the interpreter to try out a large number of interesting ideas that are present in other array language implementations, such as automatic numerical differentiation<\/a>, the obverse operator<\/a>, and a monadic inner product<\/a> where, for example, ——————————————<\/p>\n This week’s videos:<\/p>\n Materials for all presentations can be downloaded from the Dyalog ’23 webpage<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" This week’s collection consists of presentations by members of the development team, and concentrates on language features and development tools that the developers are currently designing or already implementing. Many of these features are likely to be in version 20.0 … Continue reading \u2338<\/code>). Similar to an SQL “group by” clause, key<\/em> performs operations on groups of data that are partitioned using key values \u2013 and it suffers from similar issues if you want the results to be in a particular order, or include entries for key values that do not occur in the data which is at hand.<\/p>\n\u2395SH<\/code> and its synonym \u2395CMD<\/code>), which is widely used by existing code bases, Peter proposes a new system function that will manage both binary and encoded input and output, and include features such as whether to error on a non-zero exit code and ways to redirect input and output<\/p>\n-.\u00d7<\/code> computes the determinant.<\/p>\n\n
\u2395SH<\/code> and \u2395CMD<\/code> (Peter Mikkelsen)<\/a><\/li>\n