Get and set current directory

Show/hide message thread

Observations from the process of implementing some of the SRFI in Chibi Scheme hga@xxxxxx (20 Jul 2019 19:44 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme John Cowan (21 Jul 2019 05:47 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme hga@xxxxxx (21 Jul 2019 12:16 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme Lassi Kortela (21 Jul 2019 12:21 UTC)

Get and set current directory Lassi Kortela (21 Jul 2019 12:26 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme Marc Feeley (21 Jul 2019 12:27 UTC)

Get and set current directory Lassi Kortela (21 Jul 2019 12:40 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme Duy Nguyen (21 Jul 2019 12:41 UTC)

Re: Observations from the process of implementing some of the SRFI in Chibi Scheme Marc Feeley (21 Jul 2019 13:21 UTC)

Re: Get and set current directory Lassi Kortela (21 Jul 2019 13:44 UTC)

Re: Get and set current directory Lassi Kortela (21 Jul 2019 13:59 UTC)

Re: Get and set current directory Marc Feeley (21 Jul 2019 14:25 UTC)

Re: Get and set current directory Lassi Kortela (21 Jul 2019 14:56 UTC)

Re: Get and set current directory Shiro Kawai (21 Jul 2019 20:59 UTC)

Re: Get and set current directory John Cowan (21 Jul 2019 22:35 UTC)

Get and set current directory Lassi Kortela 21 Jul 2019 12:26 UTC

> (set-current-directory! string)

This has two problems:

- (get-current-directory) always returns an absolute pathname, but
(set-current-directory!) can also take a relative pathname and turn it
absolute. As a general convention, are get and set! procedures supposed
to work so that a get following a set will always get the same value
that was given to set?

- The bang ! is for mutable variables, but not necessarily for things
that mutate the environment in other ways?