Please enable JavaScript to view this site.

A-Shell Development History

Navigation: Version 6.5/7.0, builds 1600+

1753 — 12 January 2024

Scroll Prev Top Next More

1753.5

Fix

Ordmap iteration with a purely numeric starting key was failing.

1753.4.1

Fix

Adjust Xcall EXTRAI for change in xcall handling of F6 params. Introduced in 6.5.1628.

1753.4.2

Fix

Xcall LIBRE was returning values 512x too small due to confusion between blocks and bytes.

1753.3.1

EIR

PDFX refinement: workaround problem with //SETBRUSH HATCH mode lines being too dark as rendered by the PDF-XChange Standard (PDFX9) driver by converting it to a solid shaded background when outputting to that printer driver.

1753.3.2

Fix

DIR.LIT 3.4(175) bug fix: the page breaking with /W/P was off by one file.

1753.2.1

EIR

Xcall FTP2: The GET operation now manually replicates the file.ext from the hostfile parameter if the localpath parameter doesn't contain one, eliminating one obstacle to switching from FTP2 to FTPDLX. In most cases, the file.ext defaulting is handled by the FTP/SFTP service anyway, but there are scenarios, particularly with SFTP, where FTP2 was failing due to lack of an explicit file.ext in localpath.

1753.2.2

Fix

Xcall FTPDLX: resolve "Error pinging COM subroutine FTPDLX.SBR" error. Problem was introduced somewhere during the introduction of support for 64 bit and/or the 6.5/7.0 version transition.

1753.2.3

EIR

ZTXFER.LIT 1.4(110): /2 mode (FTP vs FTPDLX) is now the default. To force FTPDLX mode, a new /1 switch has been added.

1753.2.4

Fix

ZTXFER.LIT 1.4(111): wildcard transfers were incorrectly reverting to FTPDLX mode. Note that due to legacy compatibility restraints, the AG_FTP command used by ZTXFER only reports success or failure and thus cannot report the number of wildcard files transfered.

1753.2.5

Fix

AG_FTP: in FTP2 mode, it was confusingly reporting wildcard transfers as if an error had occurred (due to the non-zero return status), even though it correctly listed the files transferred.

1753.1.1

Fix

64-bit date processing. Problem only appeared on CentOS 8, but might have caused subtle problems on other platforms.

1753.1.2

Fix

64-bit adjustment to filidx parameter used by both XTREE and MX_FILEPOS.

1753.1.3

EIR

Add support for new $ variables in DO files.

1753.0.1

EIR

Job status tracking: add current SBX name to the job control block, taking the last ten bytes from the end of the message field, allowing utilities such as JSTAT.LIT to be able to see the currently executing SBX in another job.

1753.0.2

EIR

JSTAT.LIT 3.3(114): add the current SBX (if applicable) to the display.

1753.0.3

New

INSTR() refinement: add a new MIAME.INI directive to completely disable the possibility of a single-character pattern in INSTR(pos,subj,ptn,flags) being misinterpreted by the regular expression processor as a pre-compiled pattern:

OPTIONS = NOINSTRX_PCP     ; No INSTR precompiled patterns

Note that the issue was previously dealt with in 1752.4 which limited the range of possible precompiled pattern numbers to just five (ASCII 1 thru 5), and also introduced the PCREX_NOT_PRECOMPILED flag. This new option is mainly a convenience for developers who have a large number of INSTR() calls with externally supplied patterns and never user precompiled patterns (at least not with INSTR()), and want to completely eliminate all possibility of confusion, without having to review or recompile all of their code.

Also note that this does not affect the ability to use precompiled patterns in explicit XCALL REGEX or XCALL REGEX2 calls. It also does not interfere with the transclude feature which relies heavily on precompiled patterns.