Email list hosting service & mailing list manager

Per-process vs per-thread current-directory once more Lassi Kortela (02 Aug 2020 19:36 UTC)
Re: Per-process vs per-thread current-directory once more Marc Nieper-Wi├čkirchen (03 Aug 2020 07:30 UTC)
Re: Per-process vs per-thread current-directory once more Lassi Kortela (03 Aug 2020 08:04 UTC)
Re: Per-process vs per-thread current-directory once more Marc Nieper-Wi├čkirchen (03 Aug 2020 12:12 UTC)
Re: Per-process vs per-thread current-directory once more Lassi Kortela (03 Aug 2020 12:20 UTC)
Re: Per-process vs per-thread current-directory once more Lassi Kortela (03 Aug 2020 08:08 UTC)
Re: Per-process vs per-thread current-directory once more Lassi Kortela (03 Aug 2020 08:17 UTC)
Re: Per-process vs per-thread current-directory once more Lassi Kortela (03 Aug 2020 08:25 UTC)

Re: Per-process vs per-thread current-directory once more Lassi Kortela 03 Aug 2020 08:08 UTC

> There are big fat warnings in the current draft under set-umask! and
> set-current-directory! that use in multi-threaded programs has
> unpredictable results.  I think that is the best we can do.

The main point of the current-directory conundrum is not the
`current-directory` procedure itself. It's all the other procedures.

If RnRS procedures take filenames relative to a per-thread
current-directory, but SRFI 170 takes them relative to the OS CWD, I'd
expect that to be quite confusing to users.