The main difficulty with file naming lies in the fact that files or even whole directories may move after CM has already partially (but not fully) processed them. For example, this happens when the autoloader (see Section 4.2) has been invoked and the session (including CM's internal state) is then frozen (i.e., saved to a file) via SMLofNJ.exportML.
CM's configurable path anchor mechanism enables it to resume such a session even when operating in a different environment, perhaps on a different machine with different file systems mounted, or a different location of the SML/NJ installation. Evaluation of path anchors always takes place as late as possible, and CM will re-evaluate path anchors as this becomes necessary due to changes to their configuration.