Closed mbaas2 closed 3 years ago
Hey Michael
Acre is supposed to fail in the event of an invalid config file[i] with either Command Execution Failed: Cannot ascertain encoding of filename (the file must start with "{" (JSON), ":Namespace" (APLSCRIPT) or "[" (APLAN)[ii] with JSON as default) or Command Execution Failed: Problem reading filename (the content is invalid for the encoding, whichever it is)
If you have ]udebug on
it will stop at the point of error as above due to the overriding of the trapping in ⎕SE.UCMD.
[i] If there is no file called "acre.config" acre will continue with defaults for all config parameters. [ii] at some time in the future this may be replaced with Dyalog's dialect of array/space notation when implemented as a part of the interpreter; or dropped altogether.
Phil
@norberturkiewicz has discovered a problem with ⎕JSON in latest build that might explain this.
I'll investigate tomorrow
Omission: "... latest Dyalog build ..."
Latest commit and push
]acre.version
Acre 8.2.0+331 2020-10-04 21:27
now contains a workaround for ⎕JSON's failure to accept a charmat argument on import which problem I have reported to Dyalog support.
Thanks - it works now!
I am attempting to open a local clone of https://github.com/steveman7/TamStat