ETAC Issues
Contents: Current ETAC Faults, Previous ETAC Faults.
This page contains matters concerning the ETAC programming language package that need attention. Such matters, or “issues”, include a list of known current faults in the latest ETAC package.
Current ETAC Faults
The following is the list of known current ETAC faults that exist in the latest ETAC package. Insignificant faults may not be listed below. The faults are intended to be resolved in the next ETAC release if possible.
The list below shows the ARN (action record number) of the fault or enhancement, and the date (YMD) that the entry was reported. The blue text is a summary of the fault or issue.
- No currently known issues.
Previous ETAC Faults
- E71 2019/06/12
Extend 'cmd_to_str' to convert linked comops to the corresponding dictionary item name.
Details: 'cmd_to_str' currently only converts unlinked comops. This could be extended to convert linked comops as well.
Implemented: ETAC_Installers_3-ena.zip. - C68 2019/06/11
The 'trunc' intrinsic command produces an incorrect value if the input argument has a value larger than 2147483647 or smaller than -2147483648.
Details: A value outside the said range cannot be represented as an ETAC integer, so the 'trunc' command produces a meaningless value for the output integer. The 'trunc' command should produce a decimal value if the input is outside the said range. Other affected commands are: frac, remd, round, randi, rand_num.
Fixed: EETAC_Installers_3-ena.zip. - J53 2019/02/21
RunETAC.exe and ETACCodeGen.exe crash on Windows 7 (x64) (and perhaps other Windows operating systems) unless Windows XP compatibility mode is set for the programs.
Details: The relevant coding appears to be correct for Windows XP but operates differently on Windows 7 (x64) and perhaps other Windows operating systems unless Windows XP compatibility mode is set in the properties of RunETAC.exe and ETACCodeGen.exe on those operating systems. The programs have been altered to be compatible with operating systems later than Windows XP (but only tested on Windows 7 (x64)).
Fixed: Amended in ETAC_Installers_2-ena.zip and ETACCodeGenEXE_Installer_1-ena.zip. - C50 2018/12/26
@DlgItemCmd() causes an error event if the command is :#TD_DI_SENDMSG:.
Details: The ETAC function call @DlgItemCmd(:#TD_DI_SENDMSG: ...) causes the error event 'FEW_STACK_ARGS' and the function fails.
Fixed: RunETAC_2-0-6-ena_Installer.exe and ETACSource_2-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- C49 2018/12/25
Generated text from default combo box code (M) creates incorrect size (DialogBoxMaker).
Details: A code in the layout when running the DialogBoxMaker ETAC utility program, such as M3---, generates a -1 for the default height of the combo box. The generated height should be a positive number.
Fixed: RunETAC_2-0-6-ena_Installer.exe and ETACSource_2-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- E31 2018/08/03
Change ETAC so that a break or error event occurring within the scope of a data object automatically removes the data dictionary.
Details: When the following code executes do {MyData1.{MyData2.{exitdo;};};}; the two data dictionaries remain on the dictionary stack. A change to ETAC should be made so that those data dictionaries are removed after the 'exitdo' (or other error event) executes.
Implemented: RunETAC_2-0-6-ena_Installer.exe and ETACSource_2-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- C11 2018/05/30
An error event occurs when calling @DefData() with more than one named base data object.
Details: For example, the following code @DefData("D1"){}; @DefData("D2"){}; @DefData("D3")["D1", "D2"]{}; causes an 'EMPTY_STACK' error. A different error event may occur depending on the state of the operator stack.
Fixed: RunETAC_2-0-6-ena_Installer.exe and ETACSource_2-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- C5 2018/05/26
TThe command line keyword, 'LOG_FILE=', is ignored by RunETAC.exe which uses the keyword itself as the argument.
Details: For example, if RunETAC.exe is executed via a command line (or a shortcut file) with the following RunETAC.exe SCRIPTS=MyScript.etac LOG_FILE="C:\Folder\MyLog.log" and MyScript.etac causes an error event, then the specified log file path is ignored, and instead, the log entries are written to a file named LOGFILE= in the current directory.
Fixed: RunETAC_2-0-6-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- C4 2018/05/23
SSome ETAC internal TAC library commands involving files may fail if given just a file name or a file path with the dot specification (ie: ./ or ../).
Details:/strong The ETAC internal TAC library commands that involve file paths may fail if given just a file name or given file paths beginning with ./ or ../.
Fixed: RunETAC_2-0-6-ena_Installer.exe in ETAC_Installers_2-ena.zip.
- C2 2018/05/23
The ETAC Compiler program fails to create a warnings file when run from a portable Run ETAC Scripts installation.
Details: This applies only to a portable Run ETAC Scripts installation when CheckETACFile.btac is run. If the ETAC Compiler files are copied to the portable installation directory, as stated in the ETAC_Preliminaries.pdf document, when CheckETACFile.btac is run (typically via the Syntax Check ETAC File shortcut file), the ETAC Compiler may issue an error message saying that it cannot create the warnings file (this is because the Data directory does not exist). The Data directory should be created automatically. This is not a critical problem and can be ignored.
Fixed: RunETAC_2-0-6-ena_Installer.exe in ETAC_Installers_2-ena.zip.