1331.1 |
Debugging refinement: recursive SBXs are now logged. These are potentially problematic if they contain STATIC variables; logging them is a temporary aid to identifying the problems. |
1331.0.1 |
New Linux feature: USPSBS.SBR (US Postal "Intelligent Bar Code") now works under Linux. |
1331.0.2 |
Log file refinement: All ashlog messages now include the program location counter (appended to the program or sbx name). This should be helpful in matching non-error traces to the source code (provided you have the LSX file). |
1331.0.3 |
Bug fix/performance refinement: Use of DIMX within a RUN or SBX no longer causes the module to be flushed from memory on exit. This eliminates the problem where indirect SBX recursion could lead to the module being removed from memory while it was still running (generally leading to illegal syntax code error). It also eliminates unnecessary SBX reloading from disk. Warning: There is still a potential SBX recursion problem in that a recursive SBX execution will clear the module's "in use" flag on exit, leaving the module vulnerable to an explicit request to clear the memory module, even though a higher-level instance of the SBX could still be executing. (This will be addressed later.) |
1331.0.4 |
SQL.SBR tracing enhancement: You can now set the environment variable ASQLTRACE=1 to activate detailed tracing of SQL.SBR operations. This is equivalent to, but probably more convenient than, setting the SQLCONF_TRACE flag in the SQLOP_LIB_INIT call. |
1331.0.5 |
TABX control bug fix: label colors were not being set correctly. |