These commits pull code from scheme-lib/lalily/parser-location.scm into ly/_internal/utilities/os-path.ily.
This module is loaded implicitly with openLilyLib
To some extent this file is similar to Python's os.path module.
When collecting code from this lalily module it became clear that there are quite some inconsistencies and redundancies in the lalily modules, and this Pull Request tries to leverage this issue. However this means that the interface changes significantly, and therefore I haven't removed the old functions yet. Instead the only thing is a warning that is printed whenever the old file is included.
Someone should take a look at possible dependencies and decide wheter the content of scheme-lib/lalily/parser-location.scm can be removed.
@jpvoigt I don't want to pass the responsibility to merge this to you, but I'd be thankful if you could take a look and tell me about anything you notice.
These commits pull code from
scheme-lib/lalily/parser-location.scm
intoly/_internal/utilities/os-path.ily
. This module is loaded implicitly with openLilyLibTo some extent this file is similar to Python's os.path module.
When collecting code from this lalily module it became clear that there are quite some inconsistencies and redundancies in the lalily modules, and this Pull Request tries to leverage this issue. However this means that the interface changes significantly, and therefore I haven't removed the old functions yet. Instead the only thing is a warning that is printed whenever the old file is included.
Someone should take a look at possible dependencies and decide wheter the content of
scheme-lib/lalily/parser-location.scm
can be removed.