35-logObsAndProps #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).