Re: Understanding SWI's relationship with a C++ app's working directory.

> If nobody messes with it anyway, caching it cannot be a bad idea.

I'm troubled by the fact that I can't set what I am thinking of as being
the "SWI Prolog WD" without that automatically affecting the WD of the
entire app, i.e. that there is no concept of a WD just for the SWI session
(presumably it is too complex and/or time-consuming to use this approach).
Am I perhaps taking a completely wrong-headed approach by setting the WD at
all?
-------------- next part --------------
HTML attachment scrubbed and removed