On 5/9/19 6:22 AM, Lassi Kortela wrote:

> I have personally had a great experience with the Go/Python style "strings with a little convenience" pathname approach. It almost always does what you want. Common Lisp and Racket style heavy parsing of pathnames is an admirable goal, but in practice I have found it to be constantly confusing, very verbose and not really making code more portable or reliable.

Kawa has this API for paths: https://www.gnu.org/software/kawa/Paths.html
--
	--Per Bothner
xxxxxx@bothner.com   http://per.bothner.com/