Dyalog APL V18.2 Issue 4 READ ME FIRST

• Summary
• Documentation
• Problems with the LOAD configuration parameter in early 18.2 images

• Issue 4 contains a fix for 021545: After ⎕CT is altered, the first use of ⌈ or ⌊ produce bad results on non-scalars tolerantly equal to integer threshold values.
• The "Start in" field in the Dyalog shortcuts under the Start menu are now populated; the initial directory is now such as "C:\Users\andys\Documents\Dyalog APL-64 18.2 Unicode Files". Note that the "Start in" field in the shortcuts on the desktop are deliberately left blank as this has been the default for many versions.
• In previous 18.2s we announced that if you used ⎕NGET, ⎕CSV, ⎕R, ⎕S or ⎕FIX then any undecodable characters would be replaced with the substitution character U+FFFD (⎕UCS 65533), no matter what the encoding. Following feedback from our beta-testers and further internal discussions we have decided to revert this behaviour to what it was pre-18.2.
• 006165: WIBNI if you could set the colour of the top left corner of a grid
  In 18.2 a Grid object now has the Property CornerTitleBCol;the colour is specified as per FCol etc.
• 018652: ⎕JSON namespaces are not instantiated in calling namespace
  Previously the outermost JSON namespace was always created in #, irrespective of where the call to ⎕ was made. From 18.1.40486 onwards the outermost JSON namespace will be created in whichever namespace the call to ⎕JSON was made.
• 19234:⎕SIGNAL 0 should clear ⎕EXCEPTION too In 18.2 onwards, calling ⎕SIGNAL 0 will clear not just ⎕DMX and ⎕DM, but also ⎕EXCEPTION.
• In the Windows IDE, the order in which you sort the Keyboard shortcuts dialog is now remembered.
• On Windows APL script files (.dyalog) and APL source files (.aplf and others) are now associated with newly installed versions of Dyalog APL. This means for example that if in Windows explorer you right click on a .aplf file, the context menu will show (Edit/Load/Run) and when selected, will use the newly installed version to carry out these functions. The user command ]fileassociations which allows you to select which version to associate these files with has been overhauled so it now supports these filetypes too, will support both local and system wide installations, and will cause a new APL session to appear when it is necessary to run the user command with raised privileges [you will still be prompted to allow this to happen!]. See ]fileassociations -?? for more information.
• We have added 2250⌶ which verifies whether .NET can be used with this instance of Dyalog APL: r←2250⌶0 The result r indicates the state of .NET:
  • r[1]: ¯1|0|1|2: Dotnet not supported|Dotnet not configured|configured to use Core|configured to use Framework
  • r[2]: 0|1: failed or not attempted|loaded
  • r[3]: text vector containing error messages generated during load.

  The intention is that this I-beam is used early on in your APL process, before you attempt to use a .NET call. The I-beam attempts to start the .NET interface and check that is is usuable, and it is silent when doing so, except for populating the result.
  Note:The result of the first call to ⌶2250 is cached: this means that if you alter the state of .NET on the machine, you will have to start a new APL process before the change is noticed.

The 18.2 documentation is included in the installation images and is available online at https://help.dyalog.com/18.2; the PDFs etc can be found at https://docs.dyalog.com/18.2.

This issue of 18.2 should install on Linux environments running both libncurses 5 and 6; and will run on Raspberry Pi O/S Bookworm.

Early releases of 18.2 had a flaw in the handling of the Create event on ⎕SE. That meant that there was a problem when using Link to launch applications directly from a directory containing source files using the LOAD parameter (see Configuration Parameters -> LOAD in the Dyalog for Microsoft Windows Installation and Configuration Guide).

If you installed 18.2.45351 or earlier then if on Windows you are using your own session file (which will always be the case if APL was installed for all users, because a local copy is made on first use), or on any platform if you have created your own modified session and you want to be able to specify

      LOAD=my.directory

then you should do one of the following:

• )load buildse and run UPDATE_182_SESSION
• )load buildse and run BUILD_SESSION <lang> to rebuild your session file from scratch
• Copy the session file in the Dyalog installation directory to the Dyalog directory under your Documents directory

The same applies on Windows if you want to be able to right click on a directory in Windows Explorer in order to Load the contents into APL.

If you do not intend to make use of the LOAD= parameter then you do not need to follow the steps listed above.