============================================================================
A-Shell Release Notes Version 6.5.1647.1 (22 Sep 2018)
============================================================================
1. AUI_EVENTWAIT refinement: static 'buttons' (i.e. static controls with 
the MBF_KBD flag set so they act like clickable buttons) are now compatible
with the EVW_EXCDFOCUS flag if the MBF_TABSTOP flag is also set. 

2. AUI_EVENTWAIT enhancement: a new flag -- EVW_BGFOCUS (&h01000000) -- 
has been added as an alternative way to highlight static text controls that
have the eventwait focus. Instead of underlining the text (as with 
EVW_ULFOCUS), it makes the background color slightly lighter. (This 
probably only makes sense with static 'buttons' that have colored 
backgrounds. Note that if the control is too light, it will be darkened
instead.

3. DYNLIB.SBR bug fix: The DCOP_UNLOAD operation wasn't fully removing the
library from memory. For some libraries (such as the DigitalPersona 
fingerprint library), this might have caused it to misbehave when initialized
for a second time during the same A-Shell session.

============================================================================
A-Shell Release Notes Version 6.5.1647.0 (21 Sep 2018)
============================================================================
1. Compiler (edit 879) language extension: dynamic function calls.
These are function calls that are dynamically bound (i.e. resolved) at 
runtime rather than at compile time.

To define a function that can be dynamically bound, insert the new keyword
"dynamic" in front of the Function keyword in the functino definition.

    Dynamic Function Fn'Foo(...)
        ...
    EndFunction

Tagging a function for dynamic binding like this does not interfere with
traditional statically bound calls to the function; it simply opens up the
additional possibility of dynamic binding.

To call the function with dynamic binding, use one of the new system 
functions DYNFUNC() or DYNFUNC$() ...

    DYNFUNC(funcname,arg1,...,argN)   ! numeric function
    DYNFUNC$(funcname,arg1,...,argN)  ! string function

These are analogous to the XFUNC() and XFUNC$() system functions (used to
dynamically call external functions implemented as SBX modules), except
that here the target function is part of (i.e. compiled within) the current
program. As with XFUNC()/XFUNC$(), the first argument (funcname here) is
a string expression resolving at runtime to the name of the function to 
call.

Examples:

    a$ = DYNFUNC$("Fn'Foo$",arg1,arg2)

    n = 27
    f$ = "Fn'Foo" + str(n) + "$"
    call DYNFUNC$(f$,arg1,arg2,arg3)

    ? DYNFUNC(Fn'Get'FuncName$(x),arg1,arg2)

The first example calls the string function Fn'Foo$(arg1,arg2)
The second calls a string function Fn'Foo27$(arg1,arg2,arg3)
The last calls a function whose name is returned from Fn'Get'FuncName$(x).

A new BASIC error code, 72 (undefined dynamic function) has been defined
and added to the ERRMSG.xxx files. It will be triggered by an attempt to
to dynamically call a function which is not declared dynamic within the
current program.

Note that in all cases, the choice of DYNFUNC() vs DYNFUNC$() determines
whether the function is expected to return a string or numeric value. Since
the type of a function is determined by the presences of a "$" suffix, 
the presence or absence of the suffix on the DYNFUNC keyword should agree at
runtime with the name of the target function. In other words, use DYNFUNC()
to call numeric functions, and DYNFUNC$() to call string functions. (Neither
the compiler nor the runtime system will complain if you mix types, but
the results are likely to disappoint.)

Compatibility: RUN / SBX modules with Dynamic functions declared are fully
compatible with earlier versions of A-Shell. But an attempt to call them
from within an A-Shell session earlier than 6.5.1647.0 will generate an
unsupported function error (35).

2. Compiler (edit 880) language extension: use of ellipsis (...) in 
argument lists to facilitate passing arguments through a wrapper function.
An example will make this more clear. Consider the following function:

   Function Fn'DynFunc$(fn$ as s260:inputonly, ...) as s0
       on error goto trap
       Fn'DynFunc$ = dynfunc$(fn$, ...)
       exitfunction
   trap:
       if err(0) = 72 then             ! if function not found
           Fn'DynFunc$ = .NULL         ! set result to null
           resume endfunction          ! and return with no error
       else
           resume endfunction with_error   ! else pass error through
       endif                           
   EndFunction

The function serves as a wrapper to the underlying dynfunc$() call; it adds
value trapping the function-not-found error and returning .NULL instead.
The ellipsis mechanism eliminates what would otherwise be a sticky problem -
we have no idea how many parameters will be passed, so there is no good way
to code the dynfunc$() call. With the ellipsis mechanism, the "..." in the
dynfunc$(fn$, ...) call is replaced by the actual parameters corresponding
to the ...in the Fn'DynFunc$() call, allowing us to pass them through without
knowing anything about them.

3. Compiler (edit 881) - Support .fn (case INsensitive) within a function as
an alias for the function name variable. For example...
 
    Function Fn'Foo(a as b2) as f6
        .fn = a**2           ! equivalent to Fn'Foo = a**2
    EndFunction

Note that the $ suffix is not used here; the .FN alias applies to both
string and numeric functions.

4. Compiler (edit 882) - Various fixes/refinments:

- The dynfunc mechanism now allows for retrieval of function return type 
information (see MX_DYNFUNC below).

- TRACE.PRINT statements with the (level) and/or (level,tags) option were
throwing bogus syntax errors for variations that weren't errors.

5. New MIAMEX sub-function MX_DYNFUNC (193) for DYNFUNC-related utilities.

   xcall MIAMEX, MX_DYNFUNC, op, funcname$, status, type$, size

where:

   op (num) [in] 
       Opcode. Currently only one opcode supported (1), which returns 
       existence, type, and size info for the specified dynamic function.

   funcname$ (str) [in] 
       Name of the function to inquire about. Case sensitive. Must be 
       tagged with the Dynamic keyword for it to be visible.

   status (signed int) [out]
       Returns 1 if found, 0 if not found, <0 for errors

   type$ (str) [out]
       Returns the type of the function, which could be an internal type
       e.g. ("B", "S", "X", "F", or "I") or a DEFSTRUCT type.

   size (num) [out]
       Returns the length in bytes of the function's return value.
 
6. AXL library for Windows (Libxl.dll) updated from 3.7.2 to 3.8.3 -
       several bug fixes and refinements, primarily to XLXS support.

7. Runtime bug fix: passing an iterator evaluating to "" as a parameter 
to a function was in some cases generating a bogus error 63 (parameter 
type mismatch).

============================================================================
A-Shell Release Notes Version 6.5.1646.6 (15 Sep 2018)
============================================================================
1. Compiler refinements/fixes (edit 879) -

- Revise compilation of ds.field(x) and ds.@fname$(x) to allow for better
  runtime error detection and handling. Incorrect use of ds.@fname$(x) in 
  place of ds.@fname$(x)(y) can now be trapped at runtime (error 71 - 
  undefined dynstruct member).  Any programs using DYNSTRUCT must be 
  recompiled!

- Improve robustness of file-based MX_DYNSTRUCT DYNOP_DEF

- Disable the auto-tracing (activated by ++PRAGMA TRACE_BEGIN) of MAP
  statements with initializers, as this was leading to spurious errors.

- Fix spurious compiler error on IF <expr> RESUME <label>. 

- Fix problem with ++PRAGMA TRACE_BEGIN appearing to have no effect after
  a previous ++PRAGMA TRACE_BEGIN at the same nesting level.

2. Improved runtime error detaction of DYNSTRUCT references (enabled by
the compiler refinement above. 

3. Many internal refinements to support Dynamic Function linking (although
still not ready to release).

4. TRACE.PRINT bug fix: attempting to display certain control characters in
the trace window was indirectly resulting in partial trace messages appearing
on the main screen.

============================================================================
A-Shell Release Notes Version 6.5.1646.5 (11 Sep 2018)
============================================================================
1. ORDMAP bug fix - close segfault loophole left open by 1646.4.

============================================================================
A-Shell Release Notes Version 6.5.1646.4 (10 Sep 2018)
============================================================================
1. LOGFIL: file hook bug fix: the 'squeeze' algorithm was outputting an 
extra byte for successive runs of 63 nulls or spaces, causing problems for
routines trying to parse the log file.

2. XTREE AutoFilter bug fix: Under some dataset conditions, the CB filter
dialog was going off the rails and crashing the client.

3. ORDMAP bug fix: close loophole through which it was possible that a
value of "" assigned to an ORDMAP with value type varx by way of an X0
variable was resulting in random garbage characters when retrieving the
value.

4. DYNSTRUCT refinement: the MX_DYNSTRUCT DYNOP_INFO operation now returns
in the deftype field the name of the applicable structure for structure 
fields.

============================================================================
A-Shell Release Notes Version 6.5.1646.3 (07 Sep 2018)
============================================================================
1. XFUNC() bug fix - the expression stack was being inadvertently reset at
the start of an XFUNC() or XFUNC$() call. Introduced in 6.5.1645.2.

============================================================================
A-Shell Release Notes Version 6.5.1646.2 (06 Sep 2018)
============================================================================
1. XTREE AutoFilter bug fix: CB-style range filtering was only considering the
first character of the upper end of the range, i.e. as if aaa-bbb was actually
aaa-b*.

2. XTREE AutoFilter bug fix: columns with cformat "s" (where the first 
character references a list definition) were not working properly when 
AutoFilter was enabled.
============================================================================
A-Shell Release Notes Version 6.5.1646.1 (04 Sep 2018)
============================================================================
1. Compiler/language refinement (edit 877) - change syntax for indirect
deferred dynstruct references from ".." to ".@". For example:        ds.@fname
      ! fname contains name of member (was ds..fname)     ds.fname        !
fname is name of member

Samples and related support files in SOSLIB and EXLIB updated accordingly.

============================================================================
A-Shell Release Notes Version 6.5.1646.0 (31 Aug 2018)
============================================================================
1. MX_DYNSTRUCT enhancement (compiler edit 876) : The DYNOP_DEF operation now
supports reading the structure definition from BASIC source files in addition to
strings. To specify a source file instead of a source string, prefix the
dsdef$ parameter with an "@", e.g.

    dsdef$ = "@exlib:fhooktst5.bp[908,50]"
    xcall MIAMEX, MX_DYNSTRUCT, DYNOP_DEF, status, dsdef$, fields, &
        dsname$, errmsg$

++include files are supported, so this gives you the ability to use any
DEFSTRUCT within an existing program for a dynamic structure definition.
It also makes it much easier to dynamically compile DEFSTRUCTs that rely
on DEFINEs, DEFTYPEs, and nested DEFSTRUCTs (since in the string version,
you have to include all of the dependent definitions in your string).

Note that as with compiler edit 875, this patch only affects dynamic
structure compilation, and thus won't affect traditional program 
compilation (i.e. doesn't require an update to the standalone compiler).

2. MX_DYNSTRUCT enhancement: DYNOP_INFO field definition array expanded
to include array extents and deftype names (if applicable). 

3. INFLD new TYPE code "|#" disables the automatic display of "0" in a
numeric field when nothing entered.

============================================================================
A-Shell Release Notes Version 6.5.1645.3 (29 Aug 2018)
============================================================================
1. XTREE bug fix/refinement: column width optimization logic now takes into
account the autofilter button width. Note: requires update to verson 7.5.2.1
of the SftTree_IX86_U_75.dll.

2. Memory allocation bug fixes related to MX_DYNSTRUCT. Note that this 
involved an edit to the internal compiler, causing its version to increase
to 875, but the change does not affect normal program compilation.

3. Bug fix/refinement to the expression handler to automatically convert
number dynstruct members to string format when they occur within 
expressions believed by the compiler to be of type string. In particular
this fixes issues with statements like the following (where ds..fname$
refers to a numeric variable)...

    trace.print ds..fname$
    print "ds..fname$=["+ds..fname$+"]"

============================================================================
A-Shell Release Notes Version 6.5.1645.2 (28 Aug 2018)
============================================================================
1. Major bug fix to expression handler (introduced in 1645.0 or .1); 
caused mixed-mode IF statements to fail to evaluate properly.

============================================================================
A-Shell Release Notes Version 6.5.1645.1 (28 Aug 2018)
============================================================================
1. Minor fixes related to dynamic structures. (To be documented...)

============================================================================
A-Shell Release Notes Version 6.5.1645.0 (27 Aug 2018)
============================================================================
1. Compiler (edit 873) language extension: dynamic structures. (To be 
   documented...)

2. Compiler (edit 874) bug fixes/refinements:

- Fix problem with CASE SYMBOL1...SYMBOL2 (introduced in edit 870)

- Report any dynamic (S,0 or X,0 variable within a DEFSTRUCT as an error.

- Reset default trace level to 0 (was 99 as of edit 871).

3. XTREE bug fix:  Holding down the up or down arrow key to rapidly 
move between editable cells in a column was in some cases allowing the 
selection bar to get out of sync with the cell currently being edited.

4. XTREE refinement: Slight aesthetic improvements to the handling of 
the alternate selection bar during cell editing when the XTRSEL_EDIT_KEEP
option is combined with a gradient version of the selection bar, i.e.
XTRSEL_STY_ALL_GRD).

============================================================================
A-Shell Release Notes Version 6.5.1644.1 (23 Aug 2018)
============================================================================
1. Compiler (edit 872) bug fix/refinement: the overall length of a ++PRAGMA
statement was being incorrectly limited to 50 characters (mainly affecting
TRACE_BEGIN). The new limit is 600 characters, with a max of 512 for the
TRACE_BEGIN token-list (4th argument).

============================================================================
A-Shell Release Notes Version 6.5.1644.0 (22 Aug 2018)
============================================================================
1. ++PRAGMA TRACE_BEGIN enhancement: a fourth (optional) parameter has been 
added in which you can specify a list of tokens to be traced. If specified, 
only lines containing one of those tokens (or variables) will be auto-
traced. For example:

    ++PRAGMA TRACE_BEGIN (0,"tag1","$#","qty,TOTAL,sku")

Following the above pragma, only lines containing "qty", "TOTAL", or "sku"
will be auto-traced. Notes:

- The token matching is case sensitive, and 'whole word' oriented. So
the above would not match the line "qty_1 = QTY / TOTAL2". However, the 
token XXX in the pragma list will match XXX$, XXX(Y), and XXX.Y.

- Tokens will also match anywhere in the source line (i.e. within string
literals and even comments).

- The trace token filtering is handled entirely by the compiler.

2. ++PRAGMA TRACE_BEGIN enhancement: TRACE_BEGIN / END blocks can now be
nested to 38 levels. Any unterminated TRACE_BEGIN block will be automatically
terminated at the end of each source file module (so to trace an entire
include module, you could insert just the ++PRAGMA TRACE_BEGIN at the top).

3. TRACE_DEBUG bug fix: Statements of the form...

       IF <EXPR> XCALL SBRNAM,PARAMS

... were incorrectly attempting to trace SBRNAM as a variable
(typically leading to an unmapped variable error). The problem did not
happen if there was a "THEN" prior to the "XCALL".

4. XTREE refinement:  XTR'SELECTAREA bit XTRSEL_EDIT_KEEP now works with
the other XTRSEL_SEL_xxx (selection bar styles), preserving the entire
selection bar display during editing. For example,

    XTR'SELECTAREA = XTRSEL_AREA_ANY or XTRSEL_STY_ALL or XTRSEL_EDIT_KEEP

will leave selection bar highlighting the entire row during editing. Note
that this is a visual change from the prior interpretation, in which 
XTRSEL_EDIT_KEEP acted like XTRSEL_STY_CELL1 during editing (highlighting
just the first cell on the row). To get the old behavior, 'OR' the two
together, i.e. XTRSEL_EDIT_KEEP or XTRSEL_STY_CELL1.

Also note that in the case of gradient selection style, the style is
temporarily changed to the normal selection bar during editing and then
changed back to the gradient style during selection.

5. AUI_IMAGE enhancement: TIF files using JPG compression are now supported
provided they are single page.

============================================================================
A-Shell Release Notes Version 6.5.1643.0 (15 Aug 2018)
============================================================================
1. New MIAME.INI OPTIONS value:  OPTIONS=XTAUTOFILTER
Automatically sets the XTF2_AUTOFILTER flag for all XTREE calls.
May also be queried and set via the MX_GETOPTIONS/MX_SETOPTIONS call
using the new options symbol/flag GOP2_XTAUTOFILTER (&h40000000).

Note that in the ATE environment, the flag is passed from the server to
the client. (It could also be set independently on the clients.)

2. File hook bug fix: the HFE_PRE_OPEN hook for random files wasn't passing
the recsize field in the hook environment structure. 

============================================================================
A-Shell Release Notes Version 6.5.1642.2 (15 Aug 2018)
============================================================================
1. AUI_EVENTWAIT bug fix: when exiting with down arrow (and EVW_VAREXIT),
the ctlid (last focused control) was being set incorrectly one control to 
the right (as if there had first been a right arrow).

2. Compiler (edit 869) internal refinement to support the possibility of
dynamically compiling defstructs at runtime.

3. Compiler (edit 870) refinement: eliminate the ambiguity surrounding a
defined symbol XXX when .XXX is an internally defined symbol (e.g. .TRUE).
The problem was that the XXX was getting translated independently of the dot,
resulting in unexpected results. For example assuming DEFINE TRUE = 1, a
subsequent reference to .TRUE was returning .1 (substituting TRUE for 1 
independent of the dot) rather than -1 (the built-in definition of .TRUE).
Attempts to define symbols with leading dots are now considered errors, 
and references to symbols with leading dots consider only the dot version.

============================================================================
A-Shell Release Notes Version 6.5.1642.1 (10 Aug 2018)
============================================================================
1. AUI_CONTROL bug fix/refinement: scaling of images in buttons with both
text and images was excessively limited by MBF2_PIXCOORDS or MBF2_PIXSIZE.

============================================================================
A-Shell Release Notes Version 6.5.1642.0 (07 Aug 2018)
============================================================================
1. File hook enhancement: a new file-based file hook handler option may now
be specified by setting the MX_FILEHOOK handler parameter to LOGFIL:fspec
where fspec is the AMOS- or native-style file spec for the hook log file.
Intead of calling an SBX for each hooked event, it writes an event record
to the log file. 

The potential advantages of the LOGFIL: handler over the original SBX: 
handler are:

- It separates (and optimizes) the part of the operation that is time
sensitive (the event handling itself) from the part which isn't  (the final or
back-end processing of the event records, whether for auditing, replication to
remote databases, or simply archival). The time sensitive part event handling
part is considerably faster than the SBX: event handlers, creating less drag
on the application.

- It is easier to implement, since the handler itself requires no programming
or debugging. You still need to write some code to process the log file
created by the handler, but there is typically little time sensitivity for
that.

- It allows for multiple hook processes per file without any additional 
impact on the application's real-time performance, since the logs can be
processed multiple times by multiple processes any time later.

- The log files can be processed on remote machines, either by writing the
log files to a network-mounted directory, or transferring them to another
machine for final processing.

Three new flags have been added to the ASHINC:HOOK.DEF to support new 
options associated with the new handler:

    Hook flag symbol     Value    Meaning
    ----------------  ----------  ---------------------------------------
    HFF_TIMESTAMP     &h00000060  Include timestamp in log for each event
    HFF_SQZ_ENV       &h00080000  'squeeze' env rec (LOGFIL: hooklogs)
    HFF_SQZ_DATA      &h00100000  'squeeze' data recs (LOGFIL: hooklogs)

The timestamp uses the following structure (HOOK.DEF) :

    defstruct ST_HOOK_TIMESTAMP 
        map2 date,b,4           ! separated date format
        map2 msecs,b,4          ! milliseconds since midnight
    endstruct

Each event record in the hook log file consists of the following fields, 
most of which are equivalent to the parameters passed to the SBX version
of the hook, and each of which is preceded by a prefix byte (represented
below as [hex value]) to help ensure correct/synchronized/adaptable
interpretation of the log. Note that some of the fields come in raw or
'squeezed' versions, depending on HFF_xxx flags passed to MX_FILEHOOK
(described in further detail below).

  [&h80]<version>         - start event prefix followed by version (currently 1)
  [&h82]<timestamp>       - (optional) timestamp, ST_HOOK_TIMESTAMP
  [&h83]<env>             - uncompressed hook env, ST_HOOK_ENV
  [&h84]<squeezed env>    - 'squeezed' version of hook env
  [&h85]<prerec>          - uncompressed prerec (rec deleted or prior to update)
  [&h86]<squeezed prerec> - 'squeezed' version of prerec
  [&h87]<rec>             - uncompress rec (updated record)
  [&h88]<squeezed rec>    - 'squeezed' version of rec
  [&h8A]<app msg>         - msg from app with HOOKOP_APPEVENT (max 256 chars)
  [&h8F]                  - event record terminator

The timestamp field is included if the HFF_TIMESTAMP (HFF_TIME or HFF_DATE)
flag is set in the MX_FILEHOOK call.  

The env (environment) field (ST_HOOK_ENV, identical to the environment 
passed to the SBX handler) is always included; either in raw format (default)
or, in 'squeezed' format if the HFF_SQZ_ENV flag was passed to MX_FILEHOOK.

The prerec and rec fields are included under the same conditions that they
would be passed to the SBX form of the hook. By default they are in raw
(binary) format but may be 'squeezed' if the HFF_SQZ_DATA flag was passed to
MX_FILEHOOK when the hook was established.

The app msg field is only present MX_FILEHOOK is called to send an app-defined
message to the hook.

The 'Squeezed' format is an A-Shell-specific lightweight data compression
scheme designed explicitly for typical data records. These are typically too
small for other compression algorithms (32 bytes to maybe 4K), and because of
the most common data storage formats used in fixed length records are likely
to have consecutive runs of nulls, spaces, zeroes, and/or brackets ("]"). The
'squeezed' format reduces all such consecutive runs of 3-63 bytes to 2 bytes.
The penalty is that individual bytes of value &hDD (221) are also encoded into
2 bytes. So the worst case scenario would be a record where every other byte
is &hDD, which would be 50% larger in the 'squeezed' format than the raw. But
that is an exceedingly minute likelihood; in the vast majority of cases, the
'squeeze' will result in a significant reduction in the log file size.

A new SOSFUNC: module, FNFHOOKLOG.BSI, provides a convenient function, 
Fn'Hooklog'Read'Event(), which is able to split out an event record from the
log (whether squeezed or not), into the various fields.

A new EXLIB: test/demo program, FHOOKTST4.BP[908,50] has been added to 
illustrate both initializing a LOGFIL: hook handler but also reading from
the log created, producing a CSV file representation.

2. XTREE bug fix/refinement: The AutoSum footer function (=SUM) wasn't
working correctly with columns using a Mask specification.

3. XTREE auto-filtering refinement: when the CB filter dialog would have
resulted in only a few single or double-character options, it converts to
a set of 20 fixed range options. (This is likely to be revised again soon
to add a variable-range option.)

============================================================================
A-Shell Release Notes Version 6.5.1641.3 (03 Aug 2018)
============================================================================
1. More XTREE auto-filtering bug fixes / refinements:

- The combination of XTF_MSEL, XTF_EDITABLE and XTF2_AUTOFILTER was leading
to column data shift when unfiltering.

- The checkbox filter dialog will now group the choices by the first 2 
characters if that seems applicable. (This approach is still experimental
and is likely to change again before settling down.)

============================================================================
A-Shell Release Notes Version 6.5.1641.2 (03 Aug 2018)
============================================================================
1. XTREE auto-filtering bug fixes / refinements:

- date filtering wasn't always working correctly

- maximum number of checkbox options in the CB filter expanded from 10 to 20.

============================================================================
A-Shell Release Notes Version 6.5.1641.1 (02 Aug 2018)
============================================================================
1. Miscellaneous XTREE auto-filtering bug fixes / refinements.

============================================================================
A-Shell Release Notes Version 6.5.1641.0 (01 Aug 2018)
============================================================================
1. Compiler (edit 868) language enhancement - PRIVATE variables and 
++PRAGMA PRIVATE_BEGIN / _END blocks may now be used in the main source
module to limit the scope of those variables to just that source file.

Note that this enhancement entirely handled by the compiler; there is no
issue with backwards or forwards runtime compatibility (even under AMOS).

2. XTREE auto-filtering fixes and enhancements:

- Implement a calendar filter, which now becomes the default for date columns.

- Add an activation checkbox to the RANGE, PATTERN, and CALENDAR filter 
dialogs to simplify clearing just that column's filter.

- Add a caption bar to the filter dialogs so they can be dragged around
(useful when the initial position covers something you want to see).

- Fix problems with the RANGE filter for dates when only specifying a 
two-digit year.

- Change the column header icon used to indicate that the column has been 
filtered to the "violeta dot".

- Date columns can now be filtered with the CB filter type (but you have to
specify the Filter=CB coldef option, since the default is the CALENDAR type).

- Fix several misc bugs in the filtering, especially involving dates and
trees with 'totals' data lines.


============================================================================
A-Shell Release Notes Version 6.5.1640.0 (23 Jul 2018)
============================================================================

1. XTREE enhancement: auto-filtering. This is a mechanism, similar to that
available in Windows Explorer or Excel, by which the user can click on a
special button in the column header to access an automatically-generated 
dialog of filtering options, which can then be used to temporarily remove
(hide) some of the items from the tree.

The feature is enabled by setting the XTF2_AUTOFILTER (&h00800000) bit in
the FLAGS2 member of the FLAGS structure/parameter. Currently it is limited 
to array-based trees.

At the simplest level, the filtering is entirely a client-side affair,
auto-configured by XTREE and controlled by the user, invisible to the 
application, and lasting only for the life of the tree. Items remaining 
in the tree retain their original physical record/row numbers so that 
selecting or editing a specific item appears the same the application 
regardless how many other items had been filtered out.

Filter types/options: There are four different types of filters (including
'none') which are automatically selected based on the column attributes, or
which can be manually select by means of these Advance Coldef Options:

    Filter=CB   
    Filter=RANGE
    Filter=PATTERN
    Filter=NONE

The CB (checkbox) filter is the most automatic of the filter types. Each time
you bring it up, it analyzes the data currently in the column and reduces it
down to a set of up to 10 checkbox options which are either complete values
(e.g. Red, Green, Blue), starting characters (e.g. R, G, B), or ranges of
starting characters (e.g A-D, E-G, H-Q, R-). The user can select one or more
of the options to filter out all the others. There is also a "select all"
option to bring the previously filtered items back.

The RANGE filter prompts for from/to values and works for numbers and 
dates/times. (In the case of dates/times, the from/to values can be in 
any of the formats supported by the sort logic.) 

The PATTERN filter is essentially just a string character match, case 
insensitive, and position independent. (The pattern "oo" will match "Oolong 
Tea", "COOKIES", "foo", etc.)  Currently the emphasis is on simplicity; 
wildcards or regex expressions are not supported but may be added later 
depending on feedback.

The NONE option prevents any filter from being assigned. Otherwise, if
no Filter type is specified, XTREE will choose one (or none) based on the
column attributes. 

Columns with a filter option other than NONE will have a check-mark 
button at the right edge of the column header. (So filtering requires
that the headers be visible.) Columns with active filter criteria applied
will display a strange symbol to the left of the column title meant to
represent filtering. (This symbol takes the place of the old up/down sort
indicators, which have been moved to the top edge of the column header.)

When multiple columns have filter specifications, they are combined 
with the "AND" operation. For example, if you filter the name column
to include just the names starting with A and F, and also the price
column to include just the range from $9.99 to $39.99, then only those
rows which meet both criteria will remain visible. You can remove the 
filter from one column (for a checkbox filter, click "Select All"; for
the other types, enter an empty pattern or range). Or you can remove
the filters from all the columns by clicking on the "clear" button in 
any column's filter dialog.

On multi-level trees, filtering only applies to the top level, and all
the dependents are filtered along with the top-level parent.

Application Filtering: The application can participate in the filtering
operation by defining a "filter status" column (1 character wide), using
cformat code "0" (zero). Typically you would want to hide such a column by
also specifying the "H" code. Once defined, the application can pre-filter
(i.e. hide) rows, prior to call XTREE to load them into the tree, by setting
the column to "1". (A space or "0" is treated as visible.)

Note that this is similar to the LoadOptions=NoRowIf# capability (see
6.5.1627.0), except that rows filtered by a "0" column can be unfiltered by
the user, whereas rows filtered out by the NoRowIf# cannot.

The application can also be notified of the visibility state of each row on
exit from the tree, by adding the cformat code "U" to the column. In this case
the field must also appear in the answer array and will be set by XTREE to "0"
for visible and "1" for filtered out (invisible). On re-entry into the tree in
XTROP_RESELECT mode, any changes made by the application to the filter state
column in the answer array will be applied to the tree (i.e. hiding or
unhiding rows). Note that except in the XTF2_ANSEQDATA case (where the answer
and data arrays have the same format, or are actually the same), the filter
state column is positioned with the checkboxes, i.e. after the drag-drop and
multi-select fields, but before any editable text fields.

For the XTROP_REPLACE operation, rows are first loaded from the data array and
are then updated based on the answer array. In the case where there is an
updatable filter status col (0U) and rows had been filtered out during the
previous editing session, this will result in all of the rows being first
added (because the data array is not updated by the filtering operation), and
then the filtered-out rows will be removed during the answer array load.
(There is nothing wrong with this two-step approach other than inefficiency;
if you have very large trees, it would be more efficient to transfer the
updated filter status indicators from the answer array back to the data array
before reloading the tree with XTROP_REPLACE.)

The XTRA5 sample program (in 908021 of the EXLIB) has been updated to 
illustrate various auto filter features. (You need to enter '1' to the
auto-filter prompt when running it.)

2. UNIX bug fix: close a rare timing loophole during shutdown of a session in
which it was possible for an event handler to try to read the jobtbl.sys file
after it had already been closed. This resulted in "!RLOCK" error messages in
the log which, at the very least, alarming, and in some cases the job may have
ended up in a zombie state instead of cleaning exiting. (Same patch as in
6.4.1558.0)

3. SYSTAT.LIT 3.2(131) closes a timing loophole in which it would report
as zombies or phantoms jobs that were actually just in the process of 
shutting down normally.

4. APEX bug fix: when changing printers in the printer selection dialog,
if the printers had different resolution, the auto-pitch font was not being
recalculated, resulting in it getting larger or smaller according to the
ratio of the resolutions. (Same patch as in 6.4.1558.0)

5. UNIX refinement: unknown signal interrupts arriving during a wait on a 
record lock now abort the lock wait. These are usually indicators of the
session breaking down anyway; aborting the lock wait makes for a cleaner 
exit. (Same patch as in 6.4.1558.0)

6. APEX bug fix/refinement: the print-as-intended button now acts the same
as the print dialog button when the intended printer is PROMPT. (The  
differences between the two operations make sense in the case where the 
application requested a specific printer, but was only causing confusion
in the case where the application was leaving it to the user. Same patch
as in 6.5.1640.0.)

7. Debug window tracing bug fix: indented lines (now standard to represent
call nesting) were failing to convert the $# macro to the line number.

============================================================================
A-Shell Release Notes Version 6.5.1639.6 (16 Jul 2018)
============================================================================
1. XTREE (server-side) bug fix: close a (long-standing) segmentation fault
loophole when a very large tree array is replaced with an empty one.

============================================================================
A-Shell Release Notes Version 6.5.1639.5 (14 Jul 2018)
============================================================================
1. XTREE (server-side) bug fix: certain fatal errors weren't being passed
to the application (introduced in 1633.1).

2. Close GPF/segfault loophole in runtime handler for statements of the 
form:

    $map(var$)[x;y] = z

(Problem was introduced in 1639.0).

Note that the auto-expansion logic (see 1639.0.8) does not apply to the 
above situation where the destination variable is an element of a collection.
Also, if the target collection element is .NULL, no the assignment does 
nothing. (The element remains null afterward.)
============================================================================
A-Shell Release Notes Version 6.5.1639.4 (13 Jul 2018)
============================================================================
1. ATE server-side bug fix: close loophole in routine waiting for an ATE
response, which allowed the wait to be aborted by certain extraneous signals 
(leading to spurious response timeout errors).

============================================================================
A-Shell Release Notes Version 6.5.1639.3 (03 Jul 2018)
============================================================================
1. Runtime refinement: various minor aesthetic improvements to the tracing
output.

2. Compiler bug fix (edit 864) - A DIMX array defined locally to a routine
and then passed by reference to another routine was incorrectly getting
deallocated return from the lower routine.

3. Compiler refinement (edit 865) - Add private functions to the tags 
file (for the benefit of APN and the Go To Definition script).

4. Compiler bug fix (edit 866) - Fix some minor aesthetic problems with 
the auto tracing mechanism.

5. Runtime bug fix/refinement:  Comparing a dynamic X variable (or fixed
single byte X variable) containing "" with a string containing was ""
failing in some cases.

6. AshExplorer.exe (version 1.0.0.7) now included in A-Shell/Windows 
and ATE release packages. This standalone utility is similar to a cross
between the File Open dialog (see MX_GETOFD) and Windows Explorer, and
is useful within an application when you want to allow the user to browse,
preview, and possibly use the default open operation on selected files,
but without necessarily waiting on the user, and without giving the user
too much flexibility to go wandering (as would otherwise be the case with
Windows Explorer). Launch via HOSTEX.SBR or MX_SHELLEX, with zero or more
of the following commmand line options:

     ASHEXPLORER.EXE {switches}

Switches:

    /START,folder-or-fspec

	Specifies the starting folder, and optionally the file to select
	for preview. Default is current directory.

    /FILTER,"descr | wildcardlist {| descr | wildcardlist}..."

 	Provides a filter specification to limit the files shown, using
	the same syntax as in MX_GETOFD. Each wildcardlist is a semi-colon
	delimited list of filename wildcards, e.g. *.jpg;*.png;XX*.bmp.
	Quoting the entire argument is recommended; do not incude spaces
	within any wildcardlist. For example:

	/FILTER,"Images | *.jpg;*.png | Docs | AB*.pdf;XY*.docx"

    /TITLE,title

	Specifies the title for the dialog box that appears. String must
	be quoted if it contains spaces.

    /CANCEL,label

	Specifies the label for the cancel/exit button (default="Exit").

    /MAX{IMIZE}

	Maximize the dialog.

    /MAXBTN

	Add a Min/Max/Normal button to the dialog caption bar.

    /NOADDRESS

	Remove the address (aka URL) line from the dialog. Useful when
	you want to confine the user to a single directory and/or there
	is no reason to reveal the address of the directory being viewed.

    /NOCHANGEDIR

	Don't allow browsing outside of the initial directory.

    /NOFILEPROMPT

	Remove the "File name: " prompt and edit box that otherwise 
 	appears beneath the list of files, where the user could type
	the name the file to select.


============================================================================
A-Shell Release Notes Version 6.5.1639.2 (26 Jun 2018)
============================================================================
1. Tracing refinement: remove limit on individual output message length when
outputting to the terminal or to a specific file (see SET TRACE OUTPUT below).
Previously the limit was 800 bytes. Note that the compiler still imposes a
limit of 16K per statement, and the debug message window and ashlog.log 
outputs impose much smaller limits of their own.

2. Compiler bug fix (edit 863): trace statements involving more than one
comma-delimited term, of which at least one was a quoted string constant,
where being formatted in a confusing way.

3. SET.LIT 1.2(163) refinement: eliminate some trace messages left in 
while testing the tracing related enhancements in SET.LIT 1.2(162).

============================================================================
A-Shell Release Notes Version 6.5.1639.1 (25 Jun 2018)
============================================================================
1. AUI bug fix - click strings using the prefix chr(7)+chr(250) were not
being recognized by XTREE. (Problem introduced after 6.5.1627)

============================================================================
A-Shell Release Notes Version 6.5.1639.0 (24 Jun 2018)
============================================================================
1. New A-Shell/Windows command line switch: -ntts
This has the same effect as adding OPTIONS=NTTS to the miame.ini file,
but is much more convenient in situations where you need that feature for
just a couple of sessions (such as for services).

2. Compiler/language (edit 861) and runtime tracing enhancement: 
syntax for the xxxxxx.PRINT and xxxxxx.PAUSE statements (eg. TRACE.PRINT, 
DEBUG.PAUSE) expanded to support a debug level, selection tags, multiple 
expressions, and automatic labeling of traced variables.

    <TRACE|DEBUG>.<PRINT|PAUSE> {({level},{tags})} expr1{,expr2,...,exprN}

The optional (level, tags) clause may be used to specify the minimum debug
level needed to activate this trace, and/or a list of tags that can be used
for selecting or filtering which of these statements is enabled at runtime.
If not specified, the default level is 0 for TRACE.xxx and 1 for DEBUG.xxx.
Tags, if specified, must be in the form of a string literal (quoted) 
comma-delimited list of case (not case sensitive). Some examples:

    debug.print "var1"=var1
    trace.print (1) "var1"=var1
    debug.print ("beta,i/o,2.0") var3,var4
    trace.pause (27,"fn'foo,alpha") "total="+totx

The first example demonstrates the prior syntax and the fact that the new 
clauses are entirely optional.

The second example uses the new clause to specify a debug level of 1, which
makes the trace.print equivalent to debug.print (illustrating that the only
difference between trace.xxx and debug.xxx is the default debug level). It 
also illustrates that you can specify just the level without the tags 
argument.

The third example illustrates the use of a tags list without an explicit level
(which defaults to 1 for debug.print). It also illustrates the use of multiple
values (i.e. a comma delimited list of values, as allowed in a normal PRINT
statement). Although not obvious from the syntax, another enhancement in this
release is that any variable appearing by itself as a term in the expression
list will automatically be prefixed by a label indicating the name of the
variable being traced. In other words, if var3=30 and var4="foo", then the 
trace will look something like: "var3=[30], var4=[foo]". Note that these 
automatic print labels are only created for variables that appear as    
terms by themselves in the list of expressions to trace.

The last example shows the case where both a level (27) and a set of tags
"fn'foo,alpha" are specified. Note that the totx in the expression list will
not get an automatic label because it is already part of a string expression.

Backwards compatibility note: while the new tracing capabilities do rely
partly on updates to the runtime system, programs using the new syntax and
compiled with the new compiler will remain compatible with older runtimes.
(The output will not be as pretty, and the level and tags arguments will
display at the end of each output line, but they won't otherwise interfere.)

3. Tracing enhancement: new macro $L may be inserted in the trace message
to display the current location counter (as a six digit hex number, matching
the format used in the LSX file).

4. Tracing enhancement: SET.LIT 1.2(162) now supports expanded DEBUG 
options in order to take advantage of the expanded trace statement options:

    .SET DEBUG ?                       ; show syntax options
    .SET DEBUG <level>                 ; set debug level
    .SET DEBUG MIN <level>             ; set minimum debug level
    .SET DEBUG TAGS {+}tag1,...,tagn   ; set tags to select/filter traces
    .SET DEBUG OUTPUT <dest>           ; specify where trace output goes

The standard SET DEBUG <level> command is unchanged, except that the 
maximum has been increased from 9 to 2^31. Note that except for programs
which explicitly map a variable named DEBUG, the runtime system will
recognize DEBUG as a special system variable whose value is that specified
by the SET DEBUG <level> command.

The DEBUG MIN option allows you set a minimum level, such that only those
trace/debug statements specifying a level >= the DEBUG MIN level and <=
the DEBUG level will be activated. The idea here is to allow different 
developers to set exclusive ranges so that they can easily enable their
own debug traces independent of others'. Or to use different ranges for
different modules (although the tags might be more suited for that).

The DEBUG TAGS option allows you to specify a list of tags (comma delimited)
to be matched up with the tags in the actual trace/debug statements for the 
purposes of filtering which will be enabled. Tags are not case sensitive. 
If the list starts with "+", then individual traces will be enabled if
they meet the debug level criteria OR they contain a matching tag. Otherwise
statements to be enabled must match both criteria, i.e. satisfy the level 
AND match one of the tags.  Note that setting the DEBUG TAGS list to "" is 
equivalent to a wildcard matching all tags. But within the trace/debug 
statements themselves, and empty tag list matches only an empty DEBUG TAGS 
list.

To select statements by level without regard to tags, set the DEBUG TAGS
to "". To select statements by tags without regard to level, specify a 
DEBUG TAGS list starting with "+". (To exclude traces that don't contain
matching tags, use the DEBUG and/or DEBUG MIN levels to make sure that they
won't match up with any of your traces. For example, if all of your trace
statements are of the form DEBUG.xxx, instead of TRACE.xxx, or all of them
explicitly specify a non-zero level, then just use SET NODEBUG to make sure
that none are selected on the basis of the debug level. Alternatively, set
the DEBUG MIN level higher than the DEBUG level.)

Note that all TRACE.xxx and DEBUG.xxx statements automatically have a
special tag associated with them that matches the current program name, 
so to select only traces for that program, use the technique just described
with SET DEBUG TAGS +program.

The DEBUG OUTPUT option controls where the trace/debug output messages go.
Options are:
    $WIN - debug message window (default for GUI environment)
    $TTY - main screen (default for text environment)
    $LOG - A-Shell main log file (ashlog.log)
    $NULL - no output
    $SBX:sbxnam - redirect to specified sbxnam.SBX
    <fspec> - an output filespec to output to a file

5. Compiler enhancement (included in edit 861) : new ++PRAGMAs to support 
enhanced tracing:

   ++PRAGMA TRACE_BEGIN   {optionlist}
   ++PRAGMA TRACE.END     {optionlist}
   ++PRAGMA TRACE.OPTIONS {optionlist}

TRACE_BEGIN and TRACE_END may be used to bracket a section of code for 
which automatic TRACE.PRINT statements will be generated after each
program statement. Each auto-generated trace will consist of two lines:
first the source code, then the trace of the variables in that statement. 
Note that not all statements will be traced; primarily it is limited to
those statements which operate on variables. Also note that the trace
generally occurs after the statement execution, which means that function 
and procedure call statements show up in the trace output after the 
routine returns. IF statements are an exception in that they get traced
prior to execution (so you can see the IF statement regardless of whether
the condition is true or false).	

TRACE_BEGIN / TRACE_END blocks cannot be nested, but a TRACE_BEGIN doesn't
necessarily require a corresponding TRACE_END (the end of the source code
will imply as much). This allows you to simply insert a ++PRAGMA TRACE_BEGIN
anywhere in a program, including the very top, to trace everything from 
that point on.

The TRACE_OPTIONS pragma only establishes default options for subsequent 
manually typed xxxxx.PRINT and xxxxx.PAUSE statements (except for those 
which already include their own explicit options).

The optionlist, which is optional in all three cases, consists of:

    (dbglvl, tags, prefix)

Each field is itself optional, although in order to specify a subsequent
field, you must specify the prior ones. The parentheses are optional
if only the dbglvl field is specified; otherwise they are mandatory.

dbglvl sets the debug level for the statement; the higher the level, the
higher the corresponding DEBUG system variable must be in order to activate
the statement.

tags is a quoted literal string consisting of comma-delimited symbols to
be associated with each xxxxx.PRINT or xxxxx.PAUSE statement. 

prefix is a quoted literal string which, if specified, is inserted at the 
start of each xxxxx.PRINT / xxxxx.PAUSE statement, typically used to specify 
macros like $#, $T, $P, $L, etc. It comes in handy in situations where you 
already have a lot of xxxxx.PRINT statement in the program, but are having
trouble identifying them in the trace output. Rather than manually modifying
each statement to include additional contextual identifiers, you could 
simply specify ++PRAGMA TRACE_OPTIONS (0,"","$L") to insert the location
counter into each trace.

For all three PRAGMAs, the optionlist establishes the default options for
subsquent manual or auto-generated xxxxx.PRINT statements. 

6. COMPIL.LIT/OCMPIL.LIT/COMPLP.LIT  1.1(135) enhancement - support /NOTRC 
switch to ignore all trace related statements during compilation (++pragma 
TRACE_xxx, TRACE.xxx, DEBUG.xxx).  

7. Compiler enhancement (edit 862) - support the /NOTRC option (or -notrc
when using the standalone compiler executable).

8. Language runtime refinement: when an assignment is made to a substring
(aka slice) of a dynamic variable, the variable is now expanded as needed
for the referenced slice to be part of the variable. For example:

    map1 var,x,0
    var[9;3] = "foo"
    print var[9;3]

Previously, the print statement would have printed nothing, because the 
assignment statement would have had no effect, since the variable var
was not long enough for the [9;3] slice to be applicable.

Now, it will be expanded (with leading bytes filled with spaces for string 
type variables or nulls for X type variables) so that the print statement
will always display "foo".

This brings the behavior more into line with the expectation for dynamic
variables (which are normally expanded as needed during assignment 
statements). But the slice assignment has always been a very special case.

============================================================================
A-Shell Release Notes Version 6.5.1638.0 (12 Jun 2018)
============================================================================
1. New function MX_SRCHPATH (191) to search for a file in the system path:

    xcall MIAMEX, MX_SRCHPATH, FILE$, FOUNDPATH$

where:

    FILE$ (str) [in] - filename to search for (no wildcards or directory)
    FOUNDPATH$ (str) [out] - returns "" if not found, else the full path.

The search path is system dependent, but normally includes the current 
directory, the directory from which the A-Shell executable was loaded, plus
all the directories included in the PATH environment variable. 

One use would be to check whether a particular external command exists
before attempting to launch it via HOSTEX.SBR.

============================================================================
A-Shell Release Notes Version 6.5.1637.4 (12 Jun 2018)
============================================================================
1. XPUTARG bug fix: putting a null string ("") to an uninitialized dynamic
variable was generating a spurious error 3. (Introduced in 1635.1)

2. INPUT CSV #CH, ARY() refinement: an empty element is now added to the 
end of the array if the input data ends with a comma. So for example, the
following data line will return ARY() with an extent of 3 (with the last
field empty):

    one,two,

Note that it is still the case that an empty line will return an array with
a zero extent.

============================================================================
A-Shell Release Notes Version 6.5.1637.3 (11 Jun 2018)
============================================================================
1. INPUT CSV bug fix: null fields were being ignored when inputting into 
a base array. For example, if the data contained...

    field1,,field3

... the following statement ...
  
    input csv #ch, ary()

--- was ignoring the null second field and loading the third field (field3)
into ary(2).

2. Compiler (edit 860) bug fix: compiler was failing to flag a syntax error
for WRITECD and WRITETD statements lacking a comma or semicolon between 
each field. For example:

    WRITECD #CH, A, B  C

This was mostly likely to occur accidentally when the statement was broken
on to multiple lines. The result was that all the fields would be output, 
but there would be a missing delimiter in the output line matching the 
location of the missing comma in the input line.

Note that probably this should be applied to all forms of PRINT statements,
but a space between PRINT arguments has long been treated equivalently to
a semicolon, which might actually be the understanding and desired 
behavior for some programmers, so we're going to leave it that way for the
traditional PRINT statements.

============================================================================
A-Shell Release Notes Version 6.5.1637.2 (08 Jun 2018)
============================================================================
1. INPUT CSV bug fix: when inputting into an X type variable, quoted fields
were ending up with a spurious quote character on the end. This was 
mainly an issue when inputting into a dynamic array reference (see 1629.0)
since it requires use of the X type; otherwise string or numeric types 
would mostly likely be used.

============================================================================
A-Shell Release Notes Version 6.5.1637.1 (04 Jun 2018)
============================================================================
1. XTREE bug fix: The RGBfgbg foreground color was not properly overriding 
the default red foreground for negative values in numeric columns.

============================================================================
A-Shell Release Notes Version 6.5.1637.0 (03 Jun 2018)
============================================================================
1. XTREE enhancement: footer text (XTR'SHOWFOOTER) may now include embedded
CRLF line breaks in order to show multiple lines (same idea as for headers).
For example:

    coldef += "1~15~Header::> Footer1" + chr(13)+chr(10)+"Footer2#~~"

2. XTREE bug fix: columns with cformat "BC" (see 1636.0) were in some cases
causing subsequent columns to display with unwanted/unexpected colors.

3. GDI printing enhancement: the x,y coordinates in all //GDI directives 
may now be optionally be expressed relative to the current cursor   
position by prefacing the coordinate value with "+" or "-". For directives
with more than one x,y pair (such as //RECTANGLE or //POLYGON), any 
relative coordinates are treated as relative to the prior coordinate on
the same axis. Some examples:

    //;absolute coordinates - from (100,200) to (300,400) ...
    //RECTANGLE,100,200,300,400

    //;relative coordinates - from 50 units above the current x,y cursor,
    //;extending 200 to the right and 75 down
    //RECTANGLE,+0,-50,+200,+75

Notes:

* While mathematically N is the same as +N, within the context of GDI
  directives, they are all strings, allowing the +N to be recognized 
  and treated differently than N (i.e. as relative rather than absolute).

* To preserve backwards compatibility, those directives that intepreted 
  -1,-1 as the current position will continue to do so.

* The //IMAGE directive continues to support negative right and bottom
  coordinates as indicating width and height. (Fortunately, there is no
  particular need for negative widths or heights, so nothing is lost by
  treating negative and positive relative right and bottom coordinates the
  same here.)

4. MX_GETENV bug fix: when retrieving the entire list of environment 
   variables into a dynamic string, the last several characters were  
   being truncated. (Same patch as in 6.4.1557.6)

5. Tracing bug fix: certain traces were causing interference with other
   operations returning string values. For example, the MALLOC trace was
   causing MX_GETENV to return the terminal device instead of the correct
   value. (Same patch as in 6.4.1557.6)

6. KILL.LIT 2.2B(126) works around a problem in which a loophole in 
   MX_GETENV (see above) might cause it to hang.

============================================================================
A-Shell Release Notes Version 6.5.1636.0 (26 May 2018)
============================================================================
1. XTREE enhancement: new Advanced Coldef Option RGBfgbg provides capability
to specify foreground and background colors for individual cells. The 
setup is similar to that for the cformat code B, whereby the first space of
the cell is reserved for an optional code that references an RGB color,
except that in this case, the color reference is to a pair of RGB colors 
(foreground and background). 

There are three parts to configuring this capability:

a) Add the cformat code "BC" to the column definition, which signifies that
the first byte of the column data is reserved for the color index character
(A-Z,a-z) or blank to indicate the standard/default color. Note that although
"BC" may be seen as a sort of combination of the individual B and C codes,
the interpretation of the combined "BC" code completely replaces their
individual meanings.

b) Define a set of RGB values associated with index characters using RGBfg
and/or RGBbg clauses, in the usual way, e.g. RGBbg=50,100,150,A. These 
colors and their associated index codes may or may not be used for other
purposes in the tree, but they are needed in order to define the color pairs
used by the "BC" columns.

c) Specify one or more RGBfgbg clauses which associate a new color index 
code in the same A-Z,a-z range, with a pair of individual color index codes:

    RGBfgbg=fgbg(fg,bg);fgbg(fg,bg)...
e.g.
    RGBfgbg=A(A,B);f(Z,q);r(M,);P(,p);Z(,)

Each RGBfgbg clause can contain one or more fgbg(fg,bg) tuplets separated 
by semicolons. Each tuplet starts with a mandatory index character 
(A-Z,a-z) which will be used to refer to the combined fg/bg color pair.
The fg and bg codes representing the foreground and background colors are
each optional (although the comma is mandatory); if omitted, that part of 
the color pair reverts to the default.

Note that although the individual RGB index characters and the combined
FG/BG index characters both occupy the same range (A-Z,a-z), they refer
to different tables of colors. So you can have 52 individual colors 
associated with an index character, and in addition, up to 52 combined
pairs associated with an index character. For a given index character,
XTREE knows whether to refer to the individual or combined color table
by the context, e.g. if the column definition contains "BC", then it will
refer to the combined color table, whereas if it contains only "B" or "C"
then it would refer to the individual table. However, if you have fewer 
than 26 of each type of color index  you may want to use upper case for 
one type and lower for the other, just to reduce confusion. 

For example:

    coldef += "0~0~x~H~RGBbg=50,100,150,A~RGBbg=75,125,175,B~~"
    coldef += "0~0~x~H~RGBfgbg=A(A,B);B(B,A);C(A,);D(,B);z(,)~~"

The first line defines two individual RGB colors, indexed as A and B.
The second line defines five fg/bg pairs, indexed as A, B, C, D, and z.
(We only partially followed the advice just given to separate the two
types of indices by upper and lower case.)  

The combined fg/bg index character A refers to foreground color A
(50,100,150) and background color B (75,125,175). Combined fg/bg index 
character B refers to the same pair, but with foreground and background
refersed. The combined fg/bg index character C refers to the A foreground 
color with the default background color. D refers to the default foreground
color with background color B. And z is equivalent to " " since both the 
foreground and background colors of the pair are omitted, i.e. set to
default.)

A new sample program XTRAFGBG has been posted to the EXLIB (908021) to 
illustrate the new feature.

2. Relax restriction on passing a locally defined dimx array to func byref.

3. ATSD.EXE 6.4.111 fixes issue with bogus "demo mode" and "license expired"
message in the log file.

4. Compiler bug fix/refinement (edit 859) - the starting key in a FOREACH
statement may now be any kind of expression. Previously, it only allowed
a simple variable or a literal string or numeric constant. And in the 
case of the numeric constant, although neither the compiler nor runtime
complained, the value wasn't being converted to string before treating it
as a key, so the resulting starting point of the FOREACH loop was not as
expected. 

As of this compiler release, any kind of expression that could appear on
the right side of an assignment statement is allowed, including numeric
expressions. But be advised however that in the case of a numeric value,
the decimal point and any digits to the right of it are dropped, e.g.
1.9 is treated as "1". If you really want to use a starting key of 
something like "1.9", then you should explicitly format it using a mask.

5. Bug fix/refinement: attempts to open a file with an empty ("") filespec
now generate BASIC error 32 (invalid filename). Previously it treated the
filespec as ".DAT", which is a legal filename and would have worked for 
OUTPUT or APPEND (thus covering up an application bug).

6. HTTP.SBR enhancements/refinments. (Note these are all actually contained
within the ASHNET 1.11.162 library update and are not actually dependent on
any particular A-Shell version) -

- Support secure protocols TLS 1.1 and TLS 1.2 in HTTP.SBR via the new flags:

    XHTTPF_SSL_TLS11   &h01000000   ! TLS 1.1 (or higher)
    XHTTPF_SSL_TLS12   &h02000000   ! TLS 1.2 (or higher)

- Fix problems with the ashnet.log file (XHTTPF_DEBUG) not getting written
  or released under some circumstances.

- Remove 100 character limit on header lines included at the top of the 
  request (using XHTTPF_HDRBODY). Maximum length is now unlimited (useful
  when headers include lengthy signatures or digests).

- Append a connection failure code to the XHTTPF_GETSTSTXT return string,
  as well as the ashnet.log file to assist with debugging failed connections.
  Codes are:

    0 = success

    Non secure connections:
    1 = empty hostname
    2 = DNS lookup failed
    3 = DNS timeout
    4 = Aborted by application.
    5 = Internal failure.
    6 = Connect Timed Out
    7 = Connect Rejected (or failed for some other reason)
    50 = HTTP proxy authentication failure.
    98 = Async operation in progress.
    99 = Product is not unlocked.

    Secure (SSL/TLS) :
    100 = TLS internal error.
    101 = Failed to send client hello.
    102 = Unexpected handshake message.
    103 = Failed to read server hello.
    104 = No server certificate.
    105 = Unexpected TLS protocol version.
    106 = Server certificate verify failed (the server certificate is expired or the cert's signature verification failed).
    107 = Unacceptable TLS protocol version.
    109 = Failed to read handshake messages.
    110 = Failed to send client certificate handshake message.
    111 = Failed to send client key exchange handshake message.
    112 = Client certificate's private key not accessible.
    113 = Failed to send client cert verify handshake message.
    114 = Failed to send change cipher spec handshake message.
    115 = Failed to send finished handshake message.
    116 = Server's Finished message is invalid.


============================================================================
A-Shell Release Notes Version 6.5.1635.1 (17 May 2018)
============================================================================
1. Parameter passing refinement: when passing expressions to/from functions
and SBX subroutines, if the target is type X, use a physical rather than 
logical transfer. This matches the behavior of assignments, and closes a
loophole that previously occurred when the source expression was of the
form VAR[x;y] or VAR[x,y] where VAR was of type X. Previously the transfer 
was being terminated at the first null even when the target variable was of 
type X.

Note that this change affects all variations of XGETARG and XPUTARG, as well
as implicit parameter passing to functions/procedures, potentially changing
the runtime behavior of existing compiled programs, but only in cases where a
string or non-numeric expression is passed to an X type variable. Given the
narrow range of situations affected, and our belief that the new behavior is
more in line with how programmers thought that it had been working all along,
not to mention the fact that it is now consistent with the assignment
statement logic, we feel that the upside of the change overwhelms the
downside. Nevertheless, at least for now, we are not treating it as a bug 
fix and therefore not planning to retrofit into the stable 6.4 release.
Programmers concerned about whether this might affect them are advised to do a
global source code search for occurrences of "[" within an XCALL or func/proc
call parameter list, as well as within any "PUTARG" statement and then check
to see whether the receiving variable is of type X and whether you are 
counting on the expression being terminated by the first null.


============================================================================
A-Shell Release Notes Version 6.5.1635.0 (13 May 2018)
============================================================================
1. New GDI //SETTRANSFORM GDI printing directive transforms the coordinate
space to rotate, translate, shift and/or stretch the output. Syntax:

    //SETTRANSFORM,m11,m12,m21,m22,dx,dy

where: 

    m11,m12,m21,m22 are floating point multipliers

    dx,dy specify a reference point in twips (1440/inch)

The effect of the //SETTRANSFORM directive is to tranform every point
(x1,y1) in the original coordinate space to a new point (x2,y2) based 
on the following formulas:

    x2 = (x1 * m11) + (y1 * m21) + dx
    y2 = (x1 * m12) + (y1 * m22) + dy

Note that the transformation is independent of SETMAPMODE and affects all
subsequent output, with the exception of //METAFILE.     

Some examples:

    //;mirror about horizontal axis at y=7920 (5.5" down)
    //SETTRANSFORM, 1, 0, 0, -1, 0, 15840

    //;mirror about vertical axis at x=6120 (4.25"over)
    //SETTRANSFORM, -1, 0, 0, 1, 12240, 0

    //;rotate 180 around point 4.25" over, 5.5" down (8.5x11 center)
    //SETTRANSFORM, -1, 0, 0, -1, 12240, 15840

    //;shrink horiz 25%, stretch vert 50%, shift down 1" and right .5"
    //SETTRANSFORM, 0.75, 0, 0, 1.5, 720, 1440

2. CRYPTO.SBR enhancement (ASHNET 1.11.160) : New opcode to create HMACs
(Hash-based Message Authentication Codes), commonly used for signing web
service requests. They combine a hash/digest algorithm (e.g. SHA256) with a
cryptographic key (typically pre-shared between sender and receiver) to both
verify data integrity of a message and authenticate the sender.

syntax:
    xcall CRYPTO, CRYPTOP_HMAC, status, src, decoding, dst, encoding, &
        cflags, cipher, key {, keybits, cmode, padding, cbsrc}

where:
    CRYPTOP_HMAC is the new opcode (7)

   src and decoding specify the source message and decoding, as with other
        opcodes.

   dst and encoding specify the destination for the output of the function.
        Typically it is encoded using base64 or hex so as to make it easily
        insertable into a web document. The destination length is independent
        of the source length and instead is determined by the hash function
        (e.g. SHA256 results in 32 bytes raw, 43 for base64, 64 for hex).

   cflags are used as for the other opcodes

   cipher should be set to CRYPTO_CIPHER_NA (0)

   key is as for the CRYPTOP_ENCODE operation

   keybits may be set to 0 if the key is encoded in a text format; otherwise
       it should specify the number of bytes in a binary-format key.

   mode should be set to one of the following to specify the hash function
       to use (default CRYPTO_MODE_SHA1):

        Symbol                 Value    Description
	---------------------- -----    ------------
	CRYPTO_MODE_SHA1        20	HMAC-SHA1
	CRYPTO_MODE_SHA256      21  	HMAC-SHA256
	CRYPTO_MODE_SHA384      22  	HMAC-SHA384
	CRYPTO_MODE_SHA512      23  	HMAC-SHA512
	CRYPTO_MODE_MD2         24  	HMAC-MD2
        CRYPTO_MODE_RIPEMB128   26  	HMAC-RIPEMB128
        CRYPTO_MODE_RIPEMB160   27  	HMAC-RIPEMB160
        CRYPTO_MODE_RIPEMB256   28  	HMAC-RIPEMB256
        CRYPTO_MODE_RIPEMB320   29  	HMAC-RIPEMB320

    cbsrc is the same as for other opcodes.

Example:

    ++include ashinc:crypto.def

    map1 text$,s,0,"The quick brown fox jumps over the lazy dog"
    map1 key$,s,64,"key"
    map1 hmac$,s,132
    map1 status,i,4

    ! generate HMAC-SHA256 for text$ using key$
    xcall CRYPTO, CRYPTOP_HMAC, status, text$, "", hmac$, "hex",  &
          CRYPF_NONE, CRYPTO_CIPHER_NA, key$, 0, CRYPTO_MODE_SHA256
    ? "hex encoded hmac-sha256: ";hmac$

============================================================================
A-Shell Release Notes Version 6.5.1634.4 (04 May 2018)
============================================================================
1. XCALL parameter passing bug fix: a routine used by external libraries
(e.g. libashmysql, etc.) for passing floating point values back
to the application was failing to properly handle certain F4/F6/F8 
conversions. The only known ramification was in FETCHR_FIELDS variation of
the SQLOP_FETCH_ROW operation of ASQL, following the 6.5.1628.0 update.

Note that the complete fix also requires updating the libashmysql module to 
version 1.4.143 and/or the libashodbc module version 1.4.112.

============================================================================
A-Shell Release Notes Version 6.5.1634.3 (23 Apr 2018)
============================================================================
1. INMEMO bug fix: passing a literal 0 for the channel was generating a 
link error. (Broken in 1628.0)

2. XTREE refinement for external buttons: clicking on an external button to
simulate a keystroke (for example, using a floating keypad) now works better
with XTREE. (Previously it may have caused XTREE to exit rather than 
processing the key as if it had been entered from the keyboard.)

============================================================================
A-Shell Release Notes Version 6.5.1634.2 (20 Apr 2018)
============================================================================
1. AUI_WINDOW bug fix: querying a non-existent window was crashing A-Shell

============================================================================
A-Shell Release Notes Version 6.5.1634.1 (17 Apr 2018)
============================================================================
1. AUTLOG.SBR bug fix: floating point return parameters were not being 
updated properly. (Problem introduced in 6.5.1628.0 with the revisions to
the XCALL parameter passing mechanism.)

============================================================================
A-Shell Release Notes Version 6.5.1634.0 (16 Apr 2018)
============================================================================
1. APEX rendering of JPG images containing line drawings and text is now
substantially improved. 

============================================================================
A-Shell Release Notes Version 6.5.1633.5 (15 Apr 2018)
============================================================================
1. ATE/ATSD AUXLOC printing refinement: a server-side printer init file 
containing DEVICE=PROMPT: will now be interpreted as DEVICE=AUXLOC:xxxxxx
(where xxxxxx is the printer init file name), rather than 
DEVICE=AUXLOC:PROMPT: as it was before. Also, on the client side, ATE will
look for an existing ASHCFG:PROMPT.PQI or SYS:PROMPT.INI in the case of
DEVICE=PROMPT:.  Both changes make it somewhat easier for the application
to supply printer-independent configuration options in the printer init 
file that work even when the user selects a different printer from the 
Windows printer dialog.

============================================================================
A-Shell Release Notes Version 6.5.1633.4 (15 Apr 2018)
============================================================================
1. XGETARGSBX bug fix: was failing to support arrays passed byref.

============================================================================
A-Shell Release Notes Version 6.5.1633.3 (04 Apr 2018)
============================================================================
1. ATE refinement: client-side IATIMEOUT handler now recognizes screen 
output and other server-client messages as activity.

============================================================================
A-Shell Release Notes Version 6.5.1633.2 (30 Mar 2018)
============================================================================
1. XTREE print preview bug fix/refinement: extend the logic of the 1626.2 
for the problem truncating the last character of some columns in the print
version so that it also applies to the headers and footers. And, fix the
problem where the headers became corrupted after exiting from the print
preview display. (Same patch as 6.4.1557.2)

2. SCALE bug fix: .IFELSE() function return value was getting upscaled twice.
(Same patch as 6.4.1557.2)

============================================================================
A-Shell Release Notes Version 6.5.1633.1 (27 Mar 2018)
============================================================================
1. XTREE bug fix: failing to specify the FILIDX parameter for file-based 
mode was causing XTREE to crash.

2. XTREE bug fix: an error trap (Basic error #69) intended to handle an
otherwise sticky ATE communication error was inadvertently being triggered for
certain unrelated conditions.

============================================================================
A-Shell Release Notes Version 6.5.1633.0 (11 Mar 2018)
============================================================================
1. Collections enhancement: writable iterators. You can now update the value
of an element in a collection via direct assignment to the iterator. For
example, the following foreach loop updates the value of each element by
appending "-updated" to it:

    dimx $foo, ordmapm(varstr;varstr)
    ...
    foreach $$i in $foo()
        $$i += "-updated"
    next $$i

Notes:

- This technique works with all collection types (ORDMAP, ORDMAPM, MLIST).

- In the case of ORDMAPM, it is the only way to change the value of an
existing element for which are there are duplicate keys. 

- In the case of ORDMAP, the direct assignment to the iterator in the above
example would be equivalent to ...

        $foo(.key($$i)) += "-updated"
        
... except much faster, since the key lookup, deletion, and re-addition 
steps are all eliminated.

- In the case of MLIST, it eliminates the need for the .ref($$i) function,
(which is now effectively deprecated).

- The iterator is only writeable when it appears on the left side of the 
equals sign in an assignment statement. In all other cases, particularly 
when passing an iterator as an argument to a function, it remains read-only.

2. Compiler bug fix (edit 858) - very long FOR statements were potentially
failing to compile correctly due to an overflow, without triggering a 
compiler error.

3. ATE-related improvements to handling of SIGHUP. Any call to AUI_EVENTWAIT,
XTREE, XTEXT, INFLD, or any ATE command requiring a response, now trigger
error 250. (Previously, some of these operations were not being treated as
input, causing delays or complications with an otherwise clean exit.)
============================================================================
A-Shell Release Notes Version 6.5.1632.0 (07 Mar 2018)
============================================================================
1. XTREE enhancement: new PopupMenu commands:

    $CBSETX - same as $CBSET but sets xtr'xvalidate bit &h08
    $CBRSTX - same as $CBRST but sets xtr'xvalidate bit &h08
    $CBUNDOX - same as $CBUNDO but sets xtr'xvalidate bit &h10

These new variations of the checkbox set, reset, and undo commands resolve
a problem with the standard ones involving ambiguity over the possible 
interpretations of the xtr'validate = 3 that they return.

============================================================================
A-Shell Release Notes Version 6.5.1631.4 (06 Mar 2018)
============================================================================
1. XTREE bug fix: xtr'xvalidate was being returned as 2 rather than 3 in 
case where a cell change occurred and a checkbox was checked on.

============================================================================
A-Shell Release Notes Version 6.5.1631.3 (03 Mar 2018)
============================================================================
1. (Windows) Fix GPF in auxiliary SBX interface used by APEX and print 
filters.

============================================================================
A-Shell Release Notes Version 6.5.1631.2 (02 Mar 2018)
============================================================================
1. Eliminate license expiration warnings for background jobs. (They were 
not helpful and possibly harmful).

2. Close some ATE-related loopholes related to AUXLOC printing, serial
passthru, and unexpected network disconnects.

============================================================================
A-Shell Release Notes Version 6.5.1631.1 (01 Mar 2018)
============================================================================
1. ISMROK.SBR bug fix: the last two parameters (IDX'BLK'SIZ and IDX'TYPE)
were not being returned correctly.

2. Compiler bug fix (edit 857) - The /PX logic was failing to recognize
a call to a function that was specified as the initializer to a MAP 
statement, thus opening up the possibility that the function would be 
removed (leading to a function-not-found error).

============================================================================
A-Shell Release Notes Version 6.5.1631.0 (23 Feb 2018)
============================================================================
1. XTREE enhancement: Auto-Sum column footers. To create a footer that shows
the column total (and auto updates as cell values change), set the footer
text to "=SUM". For example:

    coldef += "20~10~Qty::=SUM~#E~~
    coldef += "30~12~| Weight::| =SUM~#E~~

Note that as illustrated in the second example, the optional header/footer
alignment code ("| " for centering) precedes the "=SUM". Typically is isn't
necessary to specify an alignment code for the footer though, as the =SUM
option will automatically use the same alignment as the column being summed.

Also note that the footer in question here appears at the bottom of the 
grid during display and editing operations, not to be confused with the 
Advanced Coldef Option "Footer=" which defines a page footer for printing.

2. XTREE enhancement: Automatically fill in a target cell based on the 
contents of a source cell using a lookup table. This is similar to the
combo/list/substitution capability defined with ListX and CellListX and
enabled by cformat "l" or "ll", except that the description appears in a
separate column from the code (no need for a combo/dropdown box), and the list
of code,description pairs is file-based rather than embedded in the coldef.

The feature is intended for data-entry cases where the user is entering codes
that you want to provide immediate visual confirmation of by looking them up
in a table and displaying the corresponding description. It fills the gap
between small lists (where a combo box might make more sense) and very large
or complex database lookups (where only an exit to the application would make
sense). Between those two extremes (say, lookup tables between 50 and 50
thousand entries), providing the table to XTREE once and letting it do
the lookups internally will be much faster and more convenient (especially in
the ATE case where the turnaround time to exit and re-enter might be a
significant fraction of a second, enough to slow the data-entry operation).

For example, in a tree used to key in GL transactions, you might use this
technique to echo the account description in a non-editable column when the
account code is entered. 

Setup requires two new Advanced Coldef Options:

    FileListX=idx,fspec	
    LookupX=idx,targetcol

FileListX defines the table and associates it with an single character idx
code in the range of A-Z or a-z. Note that the idx shares the same space 
with the ListX and CellListX lists, so must be unique relative to them.
(In fact, combo and list substitution columns, i.e. cformat "l" or "ll", 
may refer to lists defined by FileListX just as they can for CellListX.)

The fspec can be an AMOS or native spec (from the client perspective). In
the case of ATE, the search path will automatically include the %ATE%\Cache
and %ATE%\PermCache directories, and it is up the application to transfer
the file from the server if necessary. 

Tip: you may want to use the Fn'FileAgeDiff() function in the FNFILEAGE.BSI
module of the SOSLIB to determine when your FileListX file becomes out-of-date
relative to the data file it was extracted from. And for ATE, the ATEAPX.SBX
routine will be handy for syncing the file to the client.

The file should be formatted as follows:

    code,description
    code,description
    etc.

As with the List{X} and CellList{X} lists, if the first character of the 
first code is neither an alphabetic character or a numeric digit, it is 
assumed to be the delimiter; othewise the delimiter is assumed to be the 
comma. However, unlike the other lists types, here the descriptions may
may be quoted if they contain the delimeter. (So standard two-column 
CSV files should be acceptable.)

To associate the list with a source and target column, add the LookupX=
clause to the coldef entry for the source column (i.e. the column containing
the code), specifying the idx used in the FileListX definition, and the
target column (where the description will be echoed). 

The lookup and fill operation is performed automatically whenever the source
column is edited and changed. If there is no match for the code, the
description will be blank. When loading data into a tree, the lookup will be
performed only if the target column is blank. (Chances are that the
application already knows the descriptions associated with the codes being
loaded into the tree, so it is probably more efficient for it to specify them
rather than force XTREE to look each one up.) 

Note that if you want the looked-up descriptions to be returned to the 
app with the answer array, use the "U" code for the description column.

3. Minor refinement to AUXLOC printing: if the ATE client fails to respond
to the server's request for an acknowledgment prior to the start of the 
auxiliary port printing operation, the operation is aborted (with a note
in the ashlog). This eliminates the rare but ugly scenario where a failing
network connection or unresponsive ATE client results in a stream of 
printed 'garbage' on the screen.

4. VUE (edit 371) refinement: maximum supported line length now takes into
account the longest line in the entire file being loaded. To this we add
4K, but in no case will the line length limit be less than 8K. Previously
it only looked at the first 100 lines, and then added 1K, with an overall
minimum limit of 4K.

5. Compiler bug fix (edit 856) - close a loophole that was allowing the
compiler to go into an infinite loop in certain obscure cases involving
unterminated literal strings with conditional compilation blocks.

============================================================================
A-Shell Release Notes Version 6.5.1630.1 (22 Feb 2018)
============================================================================
1. Further SCALE bug fixes:

- Conversions between floating point and non-floating point variable types 
during XPUTARG operations where not adjusting for SCALE.

- XPUTARG now tolerates anomalies in the scaling of the argument number 
(see compiler edit 855 below).

2. Compiler (edit 855) SCALE bug fix: XPUTARG literal argument numbers and 
literal .EXTENT index numbers were not being scaled in the RUN file. (The
updated run-time system will now handle it either way.)

3. File hook bug fix: The HFE_ISAM_DEL and HFE_ISAM_ADD hooks had 
unnecessary dependencies on each other and on the HFE_ISAM_WRITEx hooks
causing them to be ignored unless all were set. Now they can all be 
enabled independently.

============================================================================
A-Shell Release Notes Version 6.5.1630.0 (19 Feb 2018)
============================================================================
1. XCALL SQL enhancement: SQLOP_FETCH_ROW now supports fetching a row into
an ordmap:

    dimx $rowmap, ordmap(varstr;varx)
    ...
    cmdhdr.opflags = FETCHR_ROWMAP
    xcall SQL, SQLOP_FETCH_ROW, cmdhdr, $rowmap()
    foreach $$i in $rowmap()
        ? "Column name: ";.key($$i);", value: ";$$i
    next $$i

Requirements / Comments:

- Requires libashmysql library 1.4.142+

- Related opflags added to SQL.DEF:
    FETCHR_ROWMAP  (&h0010)  - return row as an ordmap
    FETCHR_ORGNAME (&h0020)  - Add to use org_name instead of name for key
    FETCHR_TBLNAME (&h0040)  - Add to prefix name with table name:

- If a column name is blank (possibly because it is an expression), a name
  will be generated of the form "expr-#" (1,2,3...)

- The ordmap(varstr;varx) format will handle any field type. Text fields
  will appear as they are stored in the database. Numeric and other formatted
  field types will be converted to the standard display representation (same
  as for the FETCHR_ROWSTR and FETCHR_ARRAY formats). BLOB fields will be
  encoded, and automatically decoded when assigned to a suitable variable 
  type.

2. APEX refinements: 

- Reinstate support for the ashico1::xxx icons in APEX.CFG.  (Support had
been dropped in 6.5.1617 when switching to the new *_i22b.png icons.)

- If the new icons are not found, it reverts to the old icons.

- Installer now renames the old APEX.CFG to APEX.OLD before updating it.

- The Preview Preferences button has been added back to the toolbar. (It
is also available from the main window Settings menu.

- New spooler switch: SPSW_NOSAVESTATE (&h02000000) stops APEX from saving
the user state on exit. (This might be useful when preview unusual documents
to avoid making any correspondingly unusual state adjustments (zoom, etc.)
become the default for the next normal document.

============================================================================
A-Shell Release Notes Version 6.5.1629.1 (16 Feb 2018)
============================================================================
1. MX_XCBDATA bug fix: the XCBGET and XCBPUT operations were only working
correctly if there were no intervening function or procedure calls. 
(Bug introduced in 6.5.1628). 

Note that MX_XCBDATA is limited to SBX parameters (not function/procedure
parameters), and has been deprecated since the introduction of the XGETARG*
and XPUTARG statements.
============================================================================
A-Shell Release Notes Version 6.5.1629.0 (15 Feb 2018)
============================================================================
1. New language feature: INPUT CSV into a dynamic array.

Syntax:

   DIMX ary(n), X, 0, auto_extend   
   ...
   INPUT CSV #ch, ary()

The above syntax is equivalent to...

   INPUT CSV #ch, ary(1), ary(2), ...

... where the number of array elements specified is automatically adjusted
at runtime to the number of fields on the line.

Requirements / Comments:

- Compiler edit 854+ (and runtime 6.5.1629.0+)

- The ary() must be allocated with DIMX, and must be of type X.  

- The array element size doesn't have to be 0 (i.e. dynamically sized),
  but if not, individual fields may be truncated as needed.

- For auto_extend arrays (highly recommended), the extent will be set to
  the number of fields input, with 0 indicating none (probably EOF).

- In the case of a non auto_extend array, any fields on the input line 
  beyond the fixed extent of the array will be discarded.

See the SOSFUNC:FNCSVUTL.BSI module for an example of using INPUT CSV
into an array to convert each line of a CSV file into an ordmap.

============================================================================
A-Shell Release Notes Version 6.5.1628.2 (13 Feb 2018)
============================================================================
1. Fix SCALE bug in .EXTENT when the index # is explicitly specified in the
program. 

2. Fix XCALL trace to show the unscaled argument values.

============================================================================
A-Shell Release Notes Version 6.5.1628.1 (11 Feb 2018)
============================================================================
1. Clean up various inconsistencies in the SCALE system. SBXs now inherit
the scale of the caller, overriding any SCALE specified in the SBX. (There
is no longer any point in specifying SCALE within an SBX.)

2. Compiler (edit 853) bug fixes:

- XPUTARG @PARAM was not working properly with SCALE.

- Compiler now properly complains about a dangling comma at the end of a
function/procedure parameter list. (Previously such superfluous commas were
ignored, but introduced doubt as to what the compiler was thinking.)


============================================================================
A-Shell Release Notes Version 6.5.1628.0 (09 Feb 2018)
============================================================================
1. Redesign the runtime mechanism for passing parameters to subroutines, 
functions and procedures to accomplish multiple goals:

- Eliminate the prior hard limit of 128 maximum parameters. (The runtime
system now has no limit; see below for compiler limits.)

- Reduce memory overhead for typical routines, especially in the case of
highly nested functions.

- Eliminate nearly all cases of internal subroutines that required a
specific parameter to be passed as F,6, improving efficiency but especially
flexibility (and eliminating a source of bugs for unsuspecting programmers.)
Subroutines that previously required F,6 (or in some cases other F,4 or F,8)
parameters that now allow any suitable numeric type:
ACCEPN, COMMON, FLOCK, RENAME, SLEEP, ANYCN, DSPLY, MMENU, PRINT, RDATE, 
STENO, BLOCKS, CISAM, INFLD, LAPSED, MX_FINDNEXT, MX_ROUND, MX_USRIO, 
PRTCHK, SIZE, TCPX, ACCESS, DATES, SERCH, SBRC, BOX1C, DYNLIB. 

2. Compiler (edit 852) enhancement: increase maximum length of a single line
of source code (including continuations) from 3K to 16K. Also increase the
limit on the number of xcall / function / procedure parameters from 128 to
1024. 

3. Compiler (edit 851) bug fixes:

- /PX was not properly handling ENDFUNCTION statement with line numbers.

- /P and /PX were not properly handling UNDEF statements.

- Built-in macros ABC_CURRENT_MODULE$ and ABC_CURRENT_ROUTINE$ were in some
  case returning garbage.

4. PRTXLS.SBX 2.0(207) bug fix: passing the APEX license was in some cases
crashing the Linux version.

============================================================================
A-Shell Release Notes Version 6.5.1627.1 (09 Feb 2018)
============================================================================
<Special interim update of "CX" version for pre-Vista compatibility>

1. WS2003/XP compatibility fix: image DLLs were failing to load due to use
of a runtime option not recognized by the older Windows versions.

2. Compiler edits 851 and 852 (to be documented with 1628.0)

3. DYNLIB bug fix: param types 'z' (char*) and 'Z' (const char*) were 
incorrectly converting empty strings ("") to NULL. (Only 'V' should do that.)

============================================================================
A-Shell Release Notes Version 6.5.1627.0 (01 Feb 2018)
============================================================================
1. XTREE enhancement: new Advanced Coldef Options:`

- LoadOptions=NoRowIf# 
- LoadOptions=NoRowIf!

These two options are similar in concept to the like-named ExportOptions 
(see 6.5.1626.0 below) except that they apply to the operation of loading 
data into the tree. The NoRowIf# option skips rows with a numeric value # 0,
while NoRowIf! skips rows with a numeric value of 0. (Typically the column
is defined as a one character #, but could also be a checkbox.)

The intended usage would be for a situation where you repeatedly displaying
items from a large array, but with varying filtering such that each 
iteration of the display may show different items from the set.
Rather than have to maintain two separate arrays (one with all of the items 
and one with just those to display), you can just add a column to the array 
to indicate (with 0 or 1) whether to display the item.

Notes:

- Only supported with Array Mode (not file or CSV mode).

- Only applies to opcodes XTROP_CREATE and XTROP_REPLACE.

- Purely a client-side feature; no special support or version requirements 
  on the server side.

- Removing items from a tree, by resetting the value of the LoadOptions 
  column and then doing an XTROP_REPLACE, is similar to using XTROP_DELSEL,
  but the LoadOptions approach is somewhat more flexible (particularly in
  its reversibility), and probably easier to use.

- In the ATE environment, using the LoadOptions technique to add or remove
  a small number of rows is particularly efficient due to optimization of
  the XTROP_REPLACE operation when only a few rows are changed.

- See the sample program, TSTXFLTR2.BP[908,76] in the EXLIB for an example.

============================================================================
A-Shell Release Notes Version 6.5.1626.3 (30 Jan 2018)
============================================================================
1. AUI_IMAGE bug fix: the IMGOP_DISPLAY function was failing to take into
account the presence of the top status line, resulting in the image display
being approximately one row higher than requested when the status line is
visible.

============================================================================
A-Shell Release Notes Version 6.5.1626.2 (30 Jan 2018)
============================================================================
1. XTREE row indexing patch. (Re-entry into trees without the dragdrop or 
sortable flags was in some cases failing to set the caret to the correct
row.)

2. XTREE print/preview refinement:  workaround a bug in the underlying 
print preview library which was, in some display environments, truncating
the last character(s) of a each cell. (The workaround involves appending a
few spaces to the end of each cell just before the preview and then 
removing them on return.)

============================================================================
A-Shell Release Notes Version 6.5.1626.1 (29 Jan 2018)
============================================================================
1. XTREE row indexing patch (superseded by 1626.2)

============================================================================
A-Shell Release Notes Version 6.5.1626.0 (28 Jan 2018)
============================================================================
1. XTREE enhancements: new values for the ExportOptions Advanced Coldef 
Directive:

- ExportOptions=No : Causes the associated column to be excluded from 
exporting. (Applies to real columns only.)

- ExportOptions=Yes : Causes the associated column to be included in the
export, regardless of whether the column is hidden in the display view.
Note that hidden columns will be output according to their physical position
in the coldef. (Applies to real columns only.)

- ExportOptions=NoRowIf# : Causes the entire row to be excluded from the
export if the value of the corresponding column is not zero (or in the case
of a checkbox or radiobutton cell, is checked / set). This would 
typically be used with an editable checkbox column to select rows to include
or exclude from the export. (Applies to real columns only.)

-ExportOptions=NoRowIf! : Opposite of NoRowIf#, i.e. excludes the row from
the export if the column value is zero (or unchecked).

-ExportOptions=PhyOrder : Causes the order of the columns in the export to
be based on the physical order they are defined in the coldef, rather than
the display order (which is otherwise the default). (This option affects
all columns, regardless of the column that it is specified with. Also note
that the the option can be abbreviated to ExportOptions=Phy (any additional
characters are ignored).

2. XTREE export refinement: checked checkboxes and set radiobuttons are now
exported as numeric values. Unchecked or unset checkbox and radiobuttons 
continue to be output as blanks. (Previously the exported value was always 
blank.)

3. XTREE export enhancement: you may now export directly to XLS rather than
tab or comma delimited, using the new PopupMenu system command:

    $EXPCSV2XL{:inispec}

$EXPCSV2XL is like $EXPCSV except that after creating the CSV file (which
is named %TEMP%\XTREE##.CSV where ## is the job number), it calls CSV2XL.SBX
to convert it to XLS. If no inispec is specified, the default INI file for
CSV2XL will be XTRCSV2XL.INI (with the search patch consisting of the 
current ppn, [p,0], and BAS:. If no XTRCSV2XL.INI is found in any of those
locations, is uses the standard BAS:CSV2XL.INI file. 

If the inispec is specified (AMOS or native format, may include %ENV% vars)
then is uses that filespec without any search path.

Unlike the $EXPCSV and $EXPTSV options, there is no "+" variation to 
open the file after creating it. Instead, this is determined by the CSV2XL
initialization file Launch option.

As with the other export options, you can enable it globally by adding:

    SBR=XTREE_EXPCSV2XL

to the MIAME.INI. (In the case, there is no option for the INI file, which
will always be the XTRCSV2XL.INI, using the search patch specified above.)

4. Compiler (edit 850) bug fix: the patch in edit 848 (see below) for ++IFMAP
and /PX now works for /P as well as /PX.

============================================================================
A-Shell Release Notes Version 6.5.1625.1 (25 Jan 2018)
============================================================================
1. Compiler (edit 849) bug fix: default function and procedure parameter
values were not being respected in calls where no named parameters were
specified. (Problem was introduced in compiler edit 847.)

============================================================================
A-Shell Release Notes Version 6.5.1625.0 (24 Jan 2018)
============================================================================
1. ATE-related server-side enhancement: .msi packages are now supported 
along with .exe files in the A-Shell startup search for updates from the 
%MIAME%/atesetup directory.

2. Compiler (edit 848) bug fixes / refinements:

- Passing a named lblref reference to a function without prefixing the 
name with @ was compiling but failing to actually pass the parameter.

- ++IFMAP and ++IFNMAP now work as expected with /PX. Previously, since 
++IF conditionals are processed during the initial pass but MAP statements 
are not, a function that was only referenced within a block of code 
conditioned on a seemingly true ++IFMAP would get shaken out out of the 
tree, resulting in a function-not-defined error. This is now resolved.

Note that ++IFMAP <var> only applies to global variables (not local or
private variables).

3. Runtime bug fix for spurious subscript out of range errors when passing
array base references to functions. (This was a side effect of the 
6.4.1556.7 patch which worked for XCALLs but not functions.)

============================================================================
A-Shell Release Notes Version 6.5.1624.3 (23 Jan 2018)
============================================================================
1. Compiler (edit 847) bug fixes related to indirect/lblref functions:

- Indirect procedures are now supported as well as functions. (Previously,
attempts to use indirect procedures may have resulting in undefined 
reference compiler errors.)

- Indirect functions/procedures, , i.e. LBLREF parameters, can now be 
passed by name (as expected). The actual function name being passed must 
be prefixed by the "@", just as it would when using standard ordered 
parameters. The parameter name can optionally be prefixed with @".  

For example, assuming a function defined as...

  Function Fn'Foo(@callback() as lblref) ...

... any of the following syntaxes is supported:

  call Fn'Foo(@callback=@Bar())  ! @name=@routine
  call Fn'Foo(callback=@Bar())	 ! name=@routine
  call Fn'Foo(@Bar())            ! @routine (ordered param)

============================================================================
A-Shell Release Notes Version 6.5.1624.2 (19 Jan 2018)
============================================================================
1. Apply all 6.4 patches thru 1556.7

============================================================================
A-Shell Release Notes Version 6.5.1624.1 (17 Jan 2018)
============================================================================
1. Apply all 6.4 patches thru 1556.5

============================================================================
A-Shell Release Notes Version 6.5.1624.0 (13 Jan 2018)
============================================================================
1. Compiler (edit 845) STRSIZ-related refinements:

- In the absence of an explicit "as s#" clause, string arguments to functions
  and procedures, as well as the return value of a string function, now 
  defaults to s0 (i.e. dynamic, unlimited) instead of the current STRSIZ.

- STRSIZ 0 now sets the default string size to dynamic, as would be expected.
  (Previously it set the default string size to a fixed length of zero, i.e.
  making it impossible for any unmapped string variable to hold a value.)

- SWITCH and CASE arguments are no longer limited by the current STRSIZ. 
  (Previously the compiler would complain about it you were forced to 
  actually change the STRSIZ to accommodate them, which was not very
  programmer-friendly.)

Note that all of the above are purely compiler adjustments, i.e. they change
the resulting RUN programs, which are backward compatible as least as far
back as 6.0.

2. Compiler (edit 846) .CLEAR enhancement:  .CLEAR ARY() now supported for
all types of arrays. (Previously it only applied to collections.) The 
details of the clearing operation depend on the nature of the array being
clear (described in further detail below).

Warning: using .CLEAR with any array type other than a collection (e.g.
ORDMAP) requires that runtime version 6.5.1624 or above. Otherwise it will
generate an Unsupported function error.

3. Runtime enhancement to support new .CLEAR ARY() options:

- For traditional MAPped arrays, as well as for DIMX arrays without the 
  AUTO_EXTEND attribute, .CLEAR ARY() simply clears the contents of the
  array without affecting its structure. This applies to both single
  and multi-dimensioned arrays. The end result is exactly equivalent to
  iterating through all of the array elements and setting each to null 
  (except easier to code and faster to execute).

- For DIMX arrays with the AUTO_EXTEND attribute, the extent of the first
  dimension of the array is reset to 0. This is similar to resizing the 
  array to 0 using REDIMX except that the array remains defined and ready 
  to receive new elements (via auto-extension). Note that for multi-
  dimensional arrays, dimensions beyond the first retain their original 
  extents (necessary for re-using the array since only the first dimension 
  is subject to auto-extension).

4. INSTR(spos,subject,pattern,flags) bug fix: When one of the INSTRF_xxx
flags was specified, the spos was being applied to the pattern rather than
the subject. (No problem if spos=1, but likely causing failure of the search
otherwise.) (Same patch as 6.4.1556.4).

5. CSV2XL.SBX bug fixes and enhancement:

- 2.1(215) fixes a problem with failure to properly set formats when
  the //XL,AddSheet directive was specified with both srcbook and dstbook
  arguments set to the same file.

- 2.1(216) fixes a problem with the //XL,SetCol directive failing to 
  properly recognize the numfmtid=NUMFMT_TEXT option (possibly leading to
  cells meant to contain text showing up as 0 in the target spreadsheet if
  first 20 rows of data were not representative of the remainder of the 
  rows for the affected column).

- 2.1(217) enhances the //XL,AddSheet directive by adding a new optional
  parameter "deletefirst", e.g.

    //XL,AddSheet,srcbook=x.xls,dstbook=x.xls,sheetname=test,deletefirst

  If the deletefirst parameter is specified and the specified sheet already
  exists, it will first be deleted before being re-added. Otherwise, the 
  default is, and has been, to just overwrite the existing sheet with the 
  new data. (This could result in a mixture of new and old data if the CSV 
  data contains fewer rows or columns than the existing sheet data.)  

6. (Windows) Remove static dependencies on ODBC32.DLL, ODBCCP32.DLL, 
NETAPI32.DLL, RPCRT4.DLL, IPHLPAPI.DLL, DNSAPI.DLL, OLEAUT32.DLL, 
CRYPT32.DLL, COMCTL32.DLL, WININET.DLL, WS2_32.DLL. These standard Windows 
libraries and now loaded dynamically if and when needed. (No change in 
outward behavior, except possibly to shave a few nanoseconds from the 
initial launch, and to delay any errors caused by missing DLLs to the 
point where they are really needed.)
============================================================================
A-Shell Release Notes Version 6.5.1623.1 (22 Dec 2017)
============================================================================
1. Fix bug (introduced in 1623.0) causing spurious error 63 when passing a
collection element to an SBX.

============================================================================
A-Shell Release Notes Version 6.5.1623.0 (20 Dec 2017)
============================================================================
1. Compiler (edit 844) and runtime enhancement: Collections can now be 
passed by reference in an XCALL to an SBX. On the calling side, the syntax 
is the same as for passing a DIMX array of structures, i.e. just specify 
the collection name with an empty set of parentheses, e.g.

    dimx $coll, ordmap(varstr;varstr)
    ...
    xcall MYSBX, $coll(), ...

The receiving side is also similar to that for receiving a DIMX array of
structures, i.e. you must first declare the receiving array with a variation
of the DIMX statement including the BYREF clause, e.g.

    dimx $locoll, ordmap(varstr;varstr), byref

Then use XGETARG or XGETARGS to receive the collection...

    xgetargs $locoll(), ...
or
    xgetarg 2,$locoll()

See the new MAPDIR.SBX and associated TSTMAPDIR.BP test program in [907,45] 
of the SOSLIB for a useful working example.

2. Apply 6.4 patches from 1556.2

============================================================================
A-Shell Release Notes Version 6.5.1622.0 (03 Dec 2017)
============================================================================
1. XTREE enhancement: CellList id codes can now include both upper and lower
case characters, extending the total range from 26 (a-z) to 52 (a-z, A-Z).

============================================================================
A-Shell Release Notes Version 6.5.1621.3 (30 Nov 2017)
============================================================================
1. Apply all 6.4 patches thru 1556.1

2. Compiler bug fix (edit 842) - When using the /LF switch without /M, 
certain ++EXTERN ARRAY() statements for DIMX and ORDMAP arrays were 
generating spurious errors (unmapped variable, or mismatched type/size).

============================================================================
A-Shell Release Notes Version 6.5.1621.2 (26 Nov 2017)
============================================================================
1. Compiler bug fix (edit 840) - certain references to a collection indexed
by an array of structures, e.g. $coll(struct(i).member), within a foreach
loop, were resulting in a spurious error on the NEXT $$i statement at the
bottom of the loop.

2. Compiler bug fix (edit 841) - the standalone UNIX compiler was failing
to process the -b and -l switches correctly. It was also failing to fold
++INCLUDE filenames to lower case if the compiler wasn't running from a
directory mapped to a MIAME DEVICE.

============================================================================
A-Shell Release Notes Version 6.5.1621.1 (23 Nov 2017)
============================================================================
1. Apply all 6.4 patches thru 1556.0

============================================================================
A-Shell Release Notes Version 6.5.1621.0 (14 Nov 2017)
============================================================================
1. DYNLIB.SBR enhancement: new param type ">" may be used to identify an
indirect output string parameter, i.e. one that the underlying function 
treats as the pointer to the actual output, rather than the output itself. 
For example, in the following C function, the output parameter pstring will 
actually receive the address of the output string:

    void getstring(char **pstring);

To call such a function with DYNLIB, you would use the following method:

    map1 buffer,s,0            ! dynamic ok, or size sufficient for output
    dlctl.opcode = DCOP_CALL
    xcall DYNLIB, dlctl, "getstring(>)v", buffer

The ">" parameter code will cause DYNLIB to copy the actual output string
to the buffer parameter (rather than copying its address).

Warning: this feature is dangerous in that has to trust both the signature
and the underlying library routine to output a valid address pointer; 
any discrepancy will likely cause a segmentation fault!

2. DYNLIB.SBR enhancement: new opcode DCOP_DEREF (4) "dereferences" a
pointer to return the value pointed to. Using the getstring() function in
the previous example, if it was called with the parameter signature "p"
instead of ">", to get the address directly, you could then get the value
as follows:

    map1 buffer,s,0
    map2 address,b,4

    dlctl.opcode = DCOP_CALL
    xcall DYNLIB, dlctl, "getstring(p)v", address   ! get ptr into address
    
    dlctl.opcode = DCOP_DEREF
    xcall DYNLIB, dlctl, address, buffer  ! copy string pointed to by address
                                          ! into buffer

This can be useful in dealing with functions that return a structure 
containing pointers to strings, rather than the strings themselves. 
But any time you are dealing with direct pointers like this, you run the
risk of a segmentation fault if there is any discrepancy between the 
expected and actual parameters or behavior of the underlying function.

3. AG_XFUNC refinement: The string containing the argument list was 
previously used in place, but since the area is within the terminal 
system output buffer, it was subject to possible corruption by other 
functions that use the output system. This could have interfered with 
the operation of XGETARG(S). For example, in the following SBX code,
the second XGETARG might have returned incorrect information due to 
potential sharing of the same buffer space with DEBUG.PRINT:

    XGETARG 1,ARG1
    DEBUG.PRINT "ARG1 = "+ARG1
    XGETARG 2,ARG2

This patch eliminates the danger of such a conflict.

4. MX_FSPEC bug fix: a previous refinement in 6.5.1611 related to the 
introduction of the FSPECNATIVE option had the side effect of causing 
command lines containing both spaces and filespecs with [p,pn] components
to be parsed incorrectly. This was primarily an issue for LIT commands
such as DO.LIT which often have complex argument lists containg a mixture
of filespec-related tokens.

============================================================================
A-Shell Release Notes Version 6.5.1620.1 (07 Nov 2017)
============================================================================
1. XTREE SelChgExit fix/refinement: SelChgExit was not working when 
navigating between editable cells with the the keyboard. (Clicking with
the mouse was triggering the SelChgExit, except on an editable cell in the
first row.)  Note however that in the case of cell editing validation, the
validation exitcode is likely to take precedence over the SelChgExit.

2. XTREE refinement: the force popup bit in the XTR'XNAVMASK field (&h040) 
is now always cleared on exit. Previously there were cases where it might 
be set, causing an unexpected popup on the next reentry unless the 
application cleared the bit.

============================================================================
A-Shell Release Notes Version 6.5.1620.0 (06 Nov 2017)
============================================================================
1. Compiler enhancement (edit 838): new statement DEFALIAS allows aliases
to be defined for the names of functions and procedures:

   DEFALIAS <routine-alias>() = <real-routine>()

This can be a useful code management technique for isolating lower level
changes or variations in routines (due to differences in versions, 
implementation, etc.) from the higher level application. For example,
an application may have many different discount calculation routines based
on the type of discount, some of those might be effectively the same.
Rather than forcing the higher level code to know which discounts are 
effectively the same, or forcing you to maintain redundant routines which
differ only by name, you can use DEFALIAS to create aliases. For example, 
the following statement would cause any subsequent references to the 
function Fn'Senior'Discount(qty,gender) to be converted into references to
the function Fn'AARP'Discount(qty,gender) ...

   DEFALIAS Fn'Senior'Discount() = Fn'AARP'Discount()

Notes:

- Currently this applies only to functions and procedures (not GOSUBs)

- The empty set of parentheses is mandatory for both the alias and the
  real routine name. Currently the alias only affects the name; the 
  arguments are passed through without change.

- This is purely a compiler-level mechanism and does not require any
  runtime support (i.e. is backward compatible to all runtimes).

2. Compiler bug fixes (edit 839):
  
- Symbol definitions passed on the command line using /C:sym=value 
  were being ignored during the first pass of the /P and /PX processing.

- The compiler macros ABC_CURRENT_ROUTINE$ and ABC_CURRENT_MACRO$ were 
  in some cases creating an additional spurious macro "A" which might 
  have caused a spurious syntax error for a variable "A".

============================================================================
A-Shell Release Notes Version 6.5.1619.1 (02 Nov 2017)
============================================================================
1. Relax runtime restriction on passing a DIMX X0 array byref to an XCALL.

============================================================================
A-Shell Release Notes Version 6.5.1619.0 (31 Oct 2017)
============================================================================
1. DYNLIB.SBR enhancement: now supports up to 4 dynamic libraries 
simultaneously. (Previously it could only handle one at a time.)

============================================================================
A-Shell Release Notes Version 6.5.1618.1 (25 Oct 2017)
============================================================================
1. Apply all 6.4 patches thru 1555.6

============================================================================
A-Shell Release Notes Version 6.5.1618.0 (15 Oct 2017)
============================================================================
1. TCPX.SBR enhancement: support for new optional parameter sockary() to
manage an array of sockets. When specified, the syntax becomes:

   xcall TCPX,opcode,status,buffer,sockidx,flags,timer,hostname,sockary(1)

Argument 4 (normally sockport) is now interpreted as the index into the 
sockary, rather than the socket itself. (As in the normal case, the 
TCPOP_ACCEPT calls expects the 4th argument to be the port to listen on.)

The sockary() parameter should be an array of up to 1025 ST_SOCKARY 
structures, defined (in SOSFUNC:FNTCPXARY.BSI) as:

    defstruct ST_SOCKARY
        map2 socket,b,3    ! socket value
        map2 ready,b,1     ! TCPOP_CHECK sets this to 255 if ready
    endstruct
    
The last element of this array must be zero! (This is how TCPX identifies
the end of the array.) In most cases an application would have no need to 
access this array directly. If you do want to access it directly, you should. Instead, use the utility functions in 
use the utility functions in SOSFUNC:FNTCPXARY.BSI to provide isolation from
possible changes in the structure.

The main advantage of using the sockary() method is that it by setting
the sockidx parameter to 0, TCPX will perform certain operations (mainly 
TCPOP_CHECK and TCPOP_CLOSE) on the entire set of open sockets in the array, 
rather than just one socket at a time. 

For TCPOP_CHECK, if sockidx is zero, TCPX will wait on all of open sockets
until one of them is ready to read from (subject to the time limit set by
the timer parameter). If there is a socket ready, it will return sockidx
set to the index into the array for that socket, so that a subsequent 
TCPOP_READ will read from that socket. If multiple sockets are ready to
read from, TCPX will use a round-robin scheme so as to not unduly favor
those sockets near the start of the array. It will also return the status
parameter set to the number of sockets that are ready, allowing the 
application (optionally) to read from them all by scanning the sockary()
for those with the ready flag set. (This may or may not be preferable to
just calling TCPOP_CHECK again and relying on it to return the sockidx of
the next ready socket.)

For TCPOP_CLOSE, if sockidx is zero, TCPX will close all of the open sockets,
and return status set to the number that were closed.

For TCPOP_READ, if sockidx is zero, it will read from whichever socket is
available, although this is probably not useful except in very particular
cases.

2. Apply all 6.4 patches thru 1555.4

3. LIBASHTLS.DLL refinement (now 1.2.210):  Refresh/relink with the latest 
GnuTLS library version 3.6.0. For convenience, copies of the GnuTLS binary
download packages can be found in http://www.microsabio.net/dist/other/gnutls.

============================================================================
A-Shell Release Notes Version 6.5.1617.0 (22 Sep 2017)
============================================================================
1. APEX toolbar design refresh: rearrange the icons to make the grouping
somewhat more logical and replace all of the icon images for a more 
consistent style.

2. INFLD enhancement: new Type code ||` (vertical bar, vertical bar, grave)
forces unconditional destructive CR (in text mode only).

3. (ATE enhancement) - AM62 emulation

4. Apply all 6.4 patches thru 1555.1

============================================================================
A-Shell Release Notes Version 6.5.1616.0 (07 Sep 2017)
============================================================================
1. Apply all 6.4 patches thru 1554.7

2. Compiler enhancement (edit 834) - Support .ARGTYP(@arg) and .ARGSIZ(@arg).
Concept is similar to that used for XPUTARG @arg (i.e. @arg is treated
essentially as a macro for the argument number corresponding to the argument
arg as defined in the function/procedure definition or as retrieved in an
SBX using XGETARG(S).) No change to the runtime system required.

============================================================================
A-Shell Release Notes Version 6.5.1615.0 (31 Aug 2017)
============================================================================
1. XPUTARG bug fix: outputting from an I variable to an F4 or F6 from within
a function or procedure was not working. (Same as 6.4.1554.5)

2. <sync up to several recent 6.4 patches>

============================================================================
A-Shell Release Notes Version 6.5.1614.0 (10 Aug 2017)
============================================================================
1. Enhancement to JOBTBL job status tracking: current location counter is
now being tracked. See JSTAT.LIT update below.

2. JSTAT.LIT 3.2(111) enhancement: status now shows PC location counter for
target job, vastly improving the ability to track the activity of the target
even if it is running a program without many line numbers (provided you have
the LSX file for the target program).

============================================================================
A-Shell Release Notes Version 6.5.1613.0 (10 Aug 2017)
============================================================================
1. Compiler edit 831 refinement: relax limitations on XPUTARG @VAR to allow
the same parameter number to be associated with multiple variables, provided
that the VAR the XPUTARG @VAR statement is never associated with more than a 
single parameter #. For example:

    XGETARGS ONE,TWO,THREE
    XGETARG 2,DOS           ! TWO and DOS now both associated with #2
    ...
    XPUTARG @TWO            ! Now allowed (e.g. 2,TWO); previously not

============================================================================
A-Shell Release Notes Version 6.5.1612.4 (08 Aug 2017)
============================================================================
1. INPUT CSV bug fix: failure to de-quote last field on line if there were
trailing spaces after the last quote.  Also fix problems with inputting
quoted fields into variables zero or one byte larger than the dequoted data.

2. Bug fix: clean up issues related to ISAM file hooks and native specs.

3. Bug fix: main window background color wasn't always being restored after
darkening it during a blocking child process.

============================================================================
A-Shell Release Notes Version 6.5.1612.3 (07 Aug 2017)
============================================================================
1. APEX refinement: support SEPARATOR lines in the APEX.CFG file to add
a little space between groups of custom extension buttons. And add a small
space to separate the print/find/preferences from the first custom button.

============================================================================
A-Shell Release Notes Version 6.5.1612.2 (06 Aug 2017)
============================================================================
1. PRINT.LIT 3.3(129) - auto-logs user into ASHCFG: if not already logged
in. (Solves problems with filespec conversion when printing without a login,
as may occur in APEX.)

============================================================================
A-Shell Release Notes Version 6.5.1612.1 (04 Aug 2017)
============================================================================
1. Migrate 6.4 patches 6.4.1553.5 thru 6.4.1553.7

============================================================================
A-Shell Release Notes Version 6.5.1612.0 (29 Jul 2017)
============================================================================
1. APEX refinement: custom buttons can now use PNG format.

============================================================================
A-Shell Release Notes Version 6.5.1611.0 (21 Jul 2017)
============================================================================
1. Migrate all 6.4 patches 6.4.1552.2 thru 6.4.1553.4

============================================================================
A-Shell Release Notes Version 6.5.1610.1 (07 Jul 2017)
============================================================================
1. SORTIT.SBR bug fix - specifying an array by its first element, e.g.
ARRAY(1), was not working for arrays of F4, F6, or SCALE'd F8. (Note that
other data types were not affected, nor were arrays of structures, nor 
were arrays passed by means of a higher-level unformatted variable.)

2. OPTIONS=FSPECNATIVE bug fix - wildcard processing within LIT commands
was generally failing to match any files when the FSPECNATIVE option was set.

3. ERASE.LIT 3.4(131) now disables the confirmation prompt when running 
from a submitted task under UNIX (just as it does for CMD files).

============================================================================
A-Shell Release Notes Version 6.5.1610.0 (05 Jul 2017)
============================================================================
1. Windows UI Enhancement: add Scrollback menu item to toggle visibility of
the vertical scroll bar. (Same as CTRL+SHFT+UP.)  

New internal menu identifier IDM_SCROLLBACK = 160 added to ASHELL.DEF.

2. New GUI interface command: AG_SCROLLBACK (109) allows program to hide,
show, or toggle the vertical scrollback bar. Syntax:

    ? TAB(-10,AG_SCROLLBACK);op;chr(127);

where op is 0 (or empty) to disable (hide) the vertical scroll bar, 1 to 
enable (show) it, and -1 to toggle it. There is no response.

3. AGCMD.LIT 1.0(105) enhanced to support AG_SCROLLBACK, e.g.

    .AGCMD AG_SCROLLBACK -1         ; toggle 
    .AGCMD AG_SCROLLBACK 1          ; show/enable
    .AGCMD AG_SCROLLBACK 0          ; hide/disable

4. Scrollback-related enhancements to LIT commands: the following commands
now make the scroll bar visible if the environment supports it (A-Shell/Win
or ATE client 6.5.1610+) and the output of the command causes the screen 
to scroll:
    COMPIL.LIT 1.1(134) 
    DIR.LIT    3.3(162)
    DUMP.LIT   1.0(107)
    SET.LIT    1.2(161)
    SYSTAT.LIT 3.2(180
    TYPE.LIT   1.0(112)

5. DATES.SBR bug fix: opcode 3 (DTOP_DAYSAFTER) was failing to handle the
negative case properly, returning a large positive number instead of a 
negative number if date1 was before date2. (Problem was introduced around
6.3.1516). Same as 6.4.1551.7

============================================================================
A-Shell Release Notes Version 6.5.1609.0 (03 Jul 2017)
============================================================================
1. XTREE enhancement: new Advanced Coldef Option:

    ExportOptions=<options>

where <options> is a comma-delimited list of options related to the export
function. Currently the only two options defined are:

    Code  (applies to ListX or CellListX columns, causing the code rather 
          than the description to be exported to the CSV.)

    Descr (default) - export the description rather than the code.

As with most other Advanced Coldef Options it can be associated with a
zero-column in order to make it the default for all other columns.

============================================================================
A-Shell Release Notes Version 6.5.1608.0 (29 Jun 2017)
============================================================================
1. Language enhancement (compiler edit 828) - expand XPUTARG @argname 
mechanism (see 1607.0) to work for SBXs. This is similar to the 
XPUTARG @argname enhancement for functions (edit 825, 6.5.1607). Except that
while that enhancement useed the function or procedure definition to 
associate argument names with their ordinal numbers, this one uses the 
combination of previously seen XGETARGS, XGETARG and XGETARGSBX statements.

To avoid the potential for misunderstandings or ambiguity, the use of the
XPUTARG @argname syntax will only be supported if there is a perfect 
one-to-one relationship between argument names and ordinal numbers, based
on the XGETARG* statements seen previously at compile time. In other words,
if one argument variable is retrieved from different argument numbers in
separate XGETARG* statements, or one argument number is retrieved into 
multiple variables, the XPUTARG @argname syntax will generate an "undefined
or ambiguous argument" error.

============================================================================
A-Shell Release Notes Version 6.5.1607.4 (21 Jun 2017)
============================================================================
1. SCALE bug fix: F,8 variables returned from XCALL routines were not being
scaled properly when the SCALE feature was enabled. (Same as 6.4.1551.3)

2. ATE/XTREE bug fix: the last byte of the answer array was getting 
truncated under certain ATE optimization scenarios, primarily when the 
answer array was too small to benefit from compression. (Same as 6.5.1551.2)

3. Compiler bug fixes (edit 827) -

- Compiling with /P or /PX was resulting in spurious "undefined argument"
errors in some cases when using the new XPUTARG @arg syntax. (See 6.5.1607.0)

- When compiling with /PX and /LF, unreferenced functions and procedures 
ending with a two-part 'END' token (e.g. "End Function" or "END PROCEDURE") 
were only writing the "END" to the LSX file, causing problems if the LSX
was later compiled.

- The "{shaken out by /px}" line in the body of such routines in the LSX
file is now properly commented out, allowing the LSX to be re-compiled 
without the /PX switch.

============================================================================
A-Shell Release Notes Version 6.5.1607.3 (21 Jun 2017)
============================================================================
1. MX_OCVT bug fix: starting in 6.5, the hex version was returning 8 digits
(with leading zeroes), instead of removing the leading zeroes by default.

============================================================================
A-Shell Release Notes Version 6.5.1607.2 (21 Jun 2017)
============================================================================
1. Command line processing bug fix: the ashell command line arguments -ba
and -bc were not being processed correctly, possibly resulting in a switch
argument being included in the dot prompt startup command. This was 
particularly noticeable in SUBMIT when using the /BC or/BA switch with a 
buffer name that also matched a CMD or DO file name, but could have had a
variety of effects outside of the SUBMIT context. (Same patch as 6.4.1551.1)

============================================================================
A-Shell Release Notes Version 6.5.1607.1 (20 Jun 2017)
============================================================================
1. SUBMIT.LIT 3.3(157) fixes a bug which caused the list function to abort 
under some circumstances with an "Error -1 reading job table".

2. INPUT LINE bug fix: it was incorrectly removing leading/trailing 
quotes (like INPUT should, but not INPUT LINE). (Problem was introduced in 
1548.9; same patch as 6.4.1551.0)

3. DYNLIB.SBR Linux bug fix: output parameters (using the "p" signature) 
were not being properly converted to I variables. (same patch as 6.4.1551.0)

============================================================================
A-Shell Release Notes Version 6.5.1607.0 (20 Jun 2017)
============================================================================
1. Language enhancement (compiler edit 825) - XPUTARG now supports the 
ability to reference the parameter to be returned by its name rather than 
by its number, using the following syntax:

    XPUTARG @arg {=<expr>}	

where arg must be one of the arguments in the function's (or procedure's)
formal parameter list. When identifying the parameter this way, the <expr>
becomes optional, defaulting to the parameter's current value.

Identifying the parameters by their names has two advantages over using
the parameter numbers: 1) it makes for more self-documenting code, and 
2) it eliminates the need to adjust the XPUTARG statements if you add, 
delete, or rearrange the function parameters (thus eliminating a source of
bugs).

For example:

    function fn'foo(arg1 as f6, arg2 as b4) as i2
        ...
        xputarg @arg1           ! new: same as xputarg 1, arg1
        xputarg @arg2=arg1*7    ! new: same as xputarg 2, arg1*7
        xputarg arg2,arg1*7     ! old: value of arg2 is arg # to return
        xputarg 2, -1           ! old: return -1 for 2nd arg
    endfunction

Note the difference between the 2nd and 3rd xputarg statements above (with and
without the '@'). In the former, we pass the value arg1*7 back for the
argument whose name is arg2 (the second argument). In the latter, we evaluate
arg2 and use that as the argument number to pass the arg1*7 value back to.

2. Compiler bug fix (edit 826) - the maximum source code length of a 
function declaration was incorrectly set at about 512 instead of 3072
like all other source lines.

============================================================================
A-Shell Release Notes Version 6.5.1606.2 (15 Jun 2017)
============================================================================
1. INFLD GUI bug fix: the parentid parameter was being truncated at 28 
characters, causing truncation and subsequent errors when passing both the 
child and parent control ids in alphanumeric form. The new limit allows for 
two control names each with a maximum length of 24 characters (which is the 
system control name limit).

============================================================================
A-Shell Release Notes Version 6.5.1606.1 (14 Jun 2017)
============================================================================
1. (Linux) Remove circa-2003 patch to USING logic which counteracted a bug
in a Linux library routine from that era, which was causing a slight 
downward bias in rounding with USING MASK operator. That bug has long since
been resolved, resulting in the Linux USING MASK rounding behavior having a
slight upward bias compared to the Windows version. Now they are the same.
(Same patch as 6.4.1550.8)

2. (Linux) EFS workaround to ease difficulty of updating from pre 6.1.1379
if using the default encryption key. (Add SBR=EFS1379 to MIAME.INI) (Same
patch as 6.4.1550.7)

============================================================================
A-Shell Release Notes Version 6.5.1606.0 (09 Jun 2017)
============================================================================
1. AG_WALLPAPER enhancement: new opcode flags added for dialog wallpaper:

       +8  expand image to fit dialog
       +16 stretch (distort) as needed to fit

Previously, dialog wallpaper only supported opcode 0, in which case the
image was tiled as needed to fit the dialog. 

2. Compiler (edit 824) bug fixes:

- Certain DEFSTRUCT arrangements were generating absurd numbers of bogus
syntax errors. 

============================================================================
A-Shell Release Notes Version 6.5.1605.1 (03 Jun 2017)
============================================================================
1. Compiler (edit 823) bug fixes: 

- The DEFSTRUCT/MAP1 enhancement added in compiler edit 821 was generally 
not working for ++include files. 

- Illegal dot within a MAP or DEFSTRUCT variable name wasn't being reported.
============================================================================
A-Shell Release Notes Version 6.5.1605.0 (30 May 2017)
============================================================================
1. Compiler (edit 822) language enhancement (new shortcut operators):

    VAR |= expr    ! equivalent to VAR = VAR or (expr)
    VAR &= expr    ! equivalent to VAR = VAR and (expr)	

Similar to the existing combo operations (+=,-=,*=,/=), these are just
syntactic shortcuts to simplify common statements, in this case, those
involving setting and clearing bits in a flags variable.  For example:

To set specified bits:
    FLAGS |= XTF_MODELESS           ! FLAGS = FLAGS or XTF_MODELESS
    FLAGS |= XTF_LEFT or XTF_RIGHT  ! FLAGS = FLAGS or (XTF_LEFT or XTF_RIGHT)

To clear all but specified bits:
    FLAGS &= XTF_MODELESS           ! FLAGS = FLAGS and XTF_MODELESS

To clear specified bits:
    FLAGS &= NOT XTF_MODELESS       ! FLAGS = FLAGS and not XTF_MODELESS

Notes: 

- As with the other combo operations, these are transplants from the
  C language.

- When setting / clearing bits in a flags variable, it is almost always 
  better to use the bitwise operators (AND,OR) instead of the arithmetic
  operators (+-), since the former are idempotent (i.e. can be used 
  redundantly without changing the result).

- This is purely a compiler enhancement and has no effect on runtime 
  compatibility for the compiled programs. (So you may want to use
  this version of the compiler even if continuing to use the 6.4 runtime.)

============================================================================
A-Shell Release Notes Version 6.5.1604.0 (30 May 2017)
============================================================================
1. XTREE enhancement: new Advanced Coldef Options for radio/checkbox 
state-specific background colors:

     RGBbg0=r,g,b
     RGBbg1=r,g,b
     RGBbg2=r,g,b

These act similarly to other RGBbg* options, except here they only affect
radio buttons and checkboxes, causing the specified background color to be
applied according to the state of the cell (0=cleared, 1=set, 
2=indeterminate). 

Notes:

- The effect is immediate. (No need to exit / reload the tree.)

- It only applies to cells that have a visible checkbox or radio button.

- It applies equally whether the cell is enabled or disabled.

- Unlike the generic RGBbg= clause, there is no optional index parameter. 

- When combined with other RGBbg clauses that affect the same column, the 
  new state-specific versions take precedence. For example, if a checkbox
  column has the following options ...
   
          RGBbg=200,200,200~RGBbg1=255,200,200~

  ... then the cells containing a checkmark (state=1) will get the
  RGBbg1 value, while all the other cells (clear, indeterminate, or 
  no checkbox) will use the standard RGBbg value.

See EXLIB [908,21] sample program XTRA6 for an example.

============================================================================
A-Shell Release Notes Version 6.5.1603.1 (29 May 2017)
============================================================================
1. ISAMA record locking bug fix - the conversion of the record locking 
system to support 64 bit ISAMA record numbers wasn't working properly,
resulting in spurious record-not-locked errors.

============================================================================
A-Shell Release Notes Version 6.5.1603.0 (25 May 2017)
============================================================================
1. Compiler enhancement (edit 821) - A DEFSTRUCT may now include a MAP1
statement (as the first member of the structure). The result is equivalent
to the combination of the DEFSTRUCT (without the MAP1) and the contained
MAP statements (including the MAP1) without the DEFSTRUCT. This is useful
when migrating legacy code from traditional MAP1-style structures to 
DEFSTRUCT-style structures, eliminating the need to either convert them all 
at once or to maintain parallel versions of the structure layouts.
(Eliminating the need to maintain parallel copies of mapped structure 
layouts was, after all, one of the primary motivations for the DEFSTRUCT
concept in the first place.)  

For example, say you have a common include file with this record layout:

    MAP1 CUST             ! mapped customer record
        MAP2 ID,S,8
        MAP2 NAME,S,30
        ...

The equivalent structure definition and mapped instance would be:

    DEFSTRUCT ST_CUST	  ! customer structure
        MAP2 ID,S,8
        MAP2 NAME,S,30
        ...
    ENDSTRUCT
    MAP1 CUST,ST_CUST	  ! mapped instance of customer structure

The only problem with the above is that all existing references any of the
members of the CUST record would need to be converted (e.g. from ID to
CUST.ID, etc.) If you didn't want to go through all your programs at once,
you instead could leave the traditionally mapped CUST record intact and 
rename the new structure version, i.e.

    DEFSTRUCT ST_CUST	  ! customer structure
        MAP2 ID,S,8
        MAP2 NAME,S,30
        ...
    ENDSTRUCT
    MAP1 SCUST,ST_CUST	  ! mapped instance of customer structure

Now you would have two equivalent record layouts, CUST (ID, NAME, ...) 
SCUST (SCUST.ID, SCUST.NAME, ...). The main problem with that, aside from
the resulting lack of syntax consistancy, is that if you modify the layout,
you have to remember to modify both versions (the MAP1 CUST version and 
the DEFSTRUCT ST_CUST version).  

This new compiler enhancement eliminates that problem by using a single
set of MAP statements to generate both the structure definition and the 
traditional mapped variable definition, i.e.

    DEFSTRUCT ST_CUST
        MAP1 CUST
            MAP2 ID,S,8
            MAP2 NAME,S,30
            ...
    ENDSTRUCT
    MAP1 SCUST,ST_CUST	  ! mapped instance of customer structure

Now the traditional record variable CUST and the new structure version SCUST
are guaranteed to always have identical formats.

Note that this is purely a compiler enhancement and has no effect on 
runtime compatibility for the compiled programs. (So you may want to use
this version of the compiler even if continuing to use the 6.4 runtime.)

============================================================================
A-Shell Release Notes Version 6.5.1602.0 (24 May 2017)
============================================================================
1. INFLD GUI enhancement: The warning bubble that otherwise appears in 
password fields when the CAPS LOCK key is on is now suppressed for fields
with the fold upper case ("^" or "|u") type code. It may also be suppressed with
the new type code "||p".  (The first part of this also implemented in 1550.5)

2. XTREE drag-drop multi-level enhancement: when dragging a parent item 
whose children are all collapsed, the entire set (parent + children) is
now dragged as a single unit. Previously the hierarchical levels were 
ignored and each item was dragged irrespective of its level. 

Note the following:

a) This only applies when the children are collapsed (not visible). If 
they are expanded (visible), then the behavior reverts to ignoring the
levels and treating each item independently.

b) Even though the parent/child group may be moved as a unit, depending
on where it is dropped, it may still disrupt and/or merge with existing
parent/child groups. For example, if the parent is dropped between two
children of another group, the target parent/child group will be split,
with the children above the drop point remaining with their prior parent,
and the children below the drop point joining the parent/child group being
dropped. (The question of whether to limit the legal drop points to avoid
this kind of side-effect is under review.)

c) Moving a parent/child group does not affect their absolute levels in
the hierarchy. An item at level x will remain at level x, regardless of 
where it is moved to. In other words, a parent cannot be converted into
a child of another parent via drag-drop. The application could implement
such an effect though, by detecting the drop via the Advanced Coldef 
Option DropExit=###, using the SELECTION and ORG'ROW fields in the answer
array to identify the items that were moved and where they were moved to,
and adjusting the level fields up or down before re-entering the tree with
XTROP_REPLACE.

d) There is currently no Undo operation for drag-drop (although again,
the application could implement this by reloading the tree contents from
a previously saved copy of the data array).

Developers are therefore urged to exercise caution when implementing 
drag-drop, expecially in conjunction with multi-level trees.

3. XTREE drag-drop multi-select enhancement: XTF_MSEL and XTF_DRAGDROP
may now be combined, allowing the user to select and drag multiple items
at a time. 

Notes:

a. As in the single-select, multi-level case, if a parent item with
collapsed children is dragged, then all of its children are dragged along
with the parent. All of the warnings listed above for the single-select
multi-level case apply here as well, the possibilities for chaos becoming
more exacerbated by the possibility of dragging a heterogenous collection
of individual and multi-level items in one operation.

b. Non-contiguous items may be dragged as a group; they become contiguous 
at the drop point.

4. XTREE enhancement: XTF2_ANSEQDATA may now be used with XTF_MSEL and/or
XTF_DRAGDROP. This requires that the data array elements start with the 
special SELECTION, and if applicable, ORG'ROW, fields as would be required
in the answer array (see XTF_DRAGDROP topic for details). The remaining 
fields in each data array element can be laid out in any order, as is 
normally the case with the data array and with XTF2_ANSEQDATA. The 
following examples may help clarify this:

    defstruct ST_XTDATA_AM    ! data elements with ANSEQDATA and MSEL
        map2 SELECTION,S,1    ! (mandatory) selection flag
        <remaining fields in any order>
    endstruct

    defstruct ST_XTDATA_AD    ! data elements with ANSEQDATA, DRAGDROP
        map2 ORG'ROW,S,4      ! (mandatory) drag/drop cross reference
        map2 SELECTION,S,1    ! (mandatory) selection flag
        <remaining fields in any order>
    endstruct

The layout requirements for the combination of multi-select and drag-drop
is the same as for drag-drop alone.

============================================================================
A-Shell Release Notes Version 6.5.1601.0 (20 May 2017)
============================================================================
1. Migrate 6.4 patches thru 6.4.1550.4

============================================================================
A-Shell Release Notes Version 6.5.1600.0 (06 May 2017)
============================================================================
1. (Linux) Begin internal changes to support 64 bit executable. The ashell
executable is usable, but lacks several features, including support for 
collections. It does however support MSODBC/Linux for connecting to SQL
Server (which is only available in 64 bit version.)

2. (Linux) ASQL ODBC connector 1.4.111 64-bit preliminary release.