{"id":6242,"date":"2019-11-15T12:00:13","date_gmt":"2019-11-15T12:00:13","guid":{"rendered":"https:\/\/www.dyalog.com\/blog\/?p=6242"},"modified":"2019-11-15T14:06:15","modified_gmt":"2019-11-15T14:06:15","slug":"dyalog-19-videos-week-4","status":"publish","type":"post","link":"https:\/\/www.dyalog.com\/blog\/2019\/11\/dyalog-19-videos-week-4\/","title":{"rendered":"Dyalog ’19 Videos: Week 4"},"content":{"rendered":"

Welcome to week 4 of the Dyalog ’19 recordings! This week, Tommy Johannesen of Jersie Data tells us about an interesting application that he has written in Dyalog APL. In the Copenhagen area, many school children are “fed with APL” in the sense that Tommy’s APL system connects the parents of ten thousand hungry children to about 60 vendors of school lunches. The service currently handles about 100,000 users with a system that runs under IIS and uses Dyalog as an ASP.NET implementation language. Each year 10,000 children leave after 10 years at school and another 10,000 enter grade 0; over the 30 years that Tommy has been in business, he has served more than a quarter of a million users.<\/p>\n

\"Tommy

Tommy Johannesen of Jersie Data ApS<\/p><\/div>\n

Peak time is Sunday evening, when parents and children log on to order meals for the coming week. Tommy tells the story of how he has been struggling with a memory leak that caused some user requests to fail when loads grew large; obviously not a good thing! Since upgrading to Dyalog version 17.0 he has been chasing this problem together with John Daintree \u2013 it was not completely solved at the time Tommy was at Dyalog ’19, but I am happy to be able to report that we believe it finally bit the dust in October!<\/p>\n

The other two recordings in week 4 are centred around the topic of source code management. First, Ad\u00e1m Brudzewsky and I introduce the tool called “Link” which is included with version 17.1. Link creates a link (hence the name) between each function (or other “code object”) in an active workspace and a corresponding text file. The namespace structure of the workspace corresponds to the directory structure that the workspace is linked to. Changes made to either side of such a link \u2013 to code in the workspace or to files outside it \u2013 are immediately reflected on the other side.<\/p>\n

\"Paul

Paul Mansour demonstrates Git integration with AcreTools<\/p><\/div>\n

The intention of a tool like Link is to enable the use of source code management systems like SVN or Git to manage source in the form of text files. These source code management systems allow the implementation of many different “workflows”, defined by parameters like how branches are used, how frequently merges are done, and how conflicts are handled. Git allows a lot of freedom, which many small teams (and that includes one-man-bands ?) don’t need. Immediately following the talk on Link, Paul Mansour took the stage at Dyalog ’19 to talk about tools that he has developed to implement a simple but effective Git workflow, suitable for many APL projects.<\/p>\n

Summary of this week\u2019s videos:<\/p>\n