Please enable JavaScript to view this site.

A-Shell Development History

1508.0.9

Bug fix / refinement, XTREE/ATE: in the case described above, the ATE-side log was registering a warning message about buffer sizes. The warning and the underlying issue have been cleaned up. Same as 6.2.1425.6.

1508.0.8

Bug fix / refinement, XTREE/ATE: when using file mode for a multi-selection tree, previously it was transmitting the entire answer parameter. Now it transmits only the number of bytes needed for the specified rows. (Server side.) Same as 6.2.1425.6.

1508.0.7

Bug fix / refinement, FLOCK: the memory allocation for the FLOCK cache now registers the name "FLKCACHE" in the log, which is useful when debugging memory handle use with the MALLOC TRACE. Close a memory leak whereby the cache was needlessly reallocated if FLOCK called within an SBX. Same as 6.2.1425.7.

1508.0.6

Bug fix / refinement: XTREE was converting quote characters within the data array to apostrophes. They are now preserved. Problem occurred only in the ATE environment, and the patch applies purely to the server side; no update needed for A-Shell or ATE clients. Same as 6.2.1425.3.

1508.0.5

Bug fix / refinement, ATE: when the transmission of a large response to the server is impeded by network congestion, the retry sequence is now more forgiving. Previously it gave up after 10 retries spaced some tens of milliseconds apart; now it keeps trying for several seconds. Same as 6.2.1425.4.

1508.0.4

Bug fix / refinement, LINUX: minor adjustment to terminal drivers to avoid a weakness in an optimized version of some string handling library calls introduced in -el6. No problems had been observed or reported though; the adjustment just reduces uncertainty in the library implementations. Same as 1426.1.

1508.0.3

Bug fix: fix bug in filehook system which may have allowed memory corruption under certain sequences of opens, closes, and hook operations. Same as 6.2.1426.1.

1508.0.2

Bug fix: fix bug in function call handler in which an unmapped array in the parameter list could corrupt the call/return stack. Same as 6.2.1426.0.

1508.0.1

Compiler (edit 761) optimization of PRIVATE_BEGIN/END logic so that the initialization is effectively "lazy", i.e. delayed until code within the module is executed. This eliminates unnecessary initializations that would otherwise occur if the ++include for the module is placed near the top of the parent program.