10-10-2024, 12:23 PM
From digging into a little more in our Dev channel on Discord:
It looks like a bug/unintentional to me, KILL/FILES/_FILES$ all call into the same logic to do the file searching which has a static `DIR *`, so calling one of them resets the state of `_FILES$`. Presumably it should have it's own separate state.
**************
So it's something likely to change and be fixed in a future release. Until then though, reading it into an array would let you work around the issue.
It looks like a bug/unintentional to me, KILL/FILES/_FILES$ all call into the same logic to do the file searching which has a static `DIR *`, so calling one of them resets the state of `_FILES$`. Presumably it should have it's own separate state.
**************
So it's something likely to change and be fixed in a future release. Until then though, reading it into an array would let you work around the issue.