1. XCALL AMOS now supports another optional argument to control whether it runs within the current process as a true subroutine or in a newly created child process. Overall syntax is now:
XCALL AMOS, CMD {,QUIET'FLAG {,PROCESS-FLAG}}
if QUIET'FLAG is specified as anything other than a null string or a numeric 0, then the subroutine will run "quietly" (i.e. with no screen output.) This was always the case, although previously even null strings and numeric zero values worked.
PROCESS'FLAG can optionally be specified as a numeric 0, 1 or 2. 0 is the same as if it wasn't specified at all, in which case the AMOS_RUNSBR setting (set in the MIAME.INI or via SET.LIT) controls whether the subroutine will operate within the current process or not. If PROCESS'FLAG=1, this forces the subroutine to act as if the AMOS_RUNSBR flag had been set. If PROCESS'FLAG=2, this forces the subroutine to act as if the AMOS_RUNSBR flag had not been set.
Note that there are certain specific commands that AMOS.SBR always executes within the current process (like LOG, VUE, and SET) and others that it always executes in a separate process (like CMD/DO files). Using PROCESS'FLAG does not change this. It only has the effect of temporarily setting the AMOS_RUNSBR option one way or the other.
(This borders on an enhancement rather than a fix and thus might have been pushed off to 4.9, but was needed to work around an esoteric problem in a particular application just now being rolled out, so it was squeezed in here. Fortunately, the implementation was very simple and thus is unlikely to introduce other problems, unless you were previously relying on being able to send even a null or zero for the QUIET'FLAG.
2. XCALL STRIP and XCALL TRIM with no argument no longer crashes.
3. (UNIX) ashlog.log is now copied to corelog.# (# = 0 to 19) in the case of a segmentation fault.
4. (UNIX) Errors occurring during the creation or deletion of directories are now logged to ashlog if TRACE=BASERR.
5. (LINUX) Several fixes were implemented in the TRSRCH.SBR routine (applicable only to a single developer).
6. (WINDOWS ATS) Garbage characters were appearing in pick lists, message boxes and INMEMO boxes in certain emulations when running via the A-Shell Telnet Service (ATS).
