This addresses issue #35: the logmode "w" (intentionally using lowercase to avoid excessive file-activity when using default modes ⎕A) gathers information about ∆W* activity in a file. Path and filename are hardcodes to keep things easy (at least in this initial phase).
LOGMODES can now be set with a env/cfg variable named "EWC_LOGMODES" - so that any tests that want to use this info can control the setting as needed. Note that any calling program which activated that setting has to take care of removing the logfile itself.
Also: this log is not directly readable with ⎕JSON because it contains a list of records. The calling program needs to initialise this file with "[" and finally append a "]". (see Test/eWC_test.aplf for an actual use case).
This addresses issue #35: the logmode "w" (intentionally using lowercase to avoid excessive file-activity when using default modes ⎕A) gathers information about ∆W* activity in a file. Path and filename are hardcodes to keep things easy (at least in this initial phase). LOGMODES can now be set with a env/cfg variable named "EWC_LOGMODES" - so that any tests that want to use this info can control the setting as needed. Note that any calling program which activated that setting has to take care of removing the logfile itself. Also: this log is not directly readable with ⎕JSON because it contains a list of records. The calling program needs to initialise this file with "[" and finally append a "]". (see Test/eWC_test.aplf for an actual use case).