Urs Liska <[email protected]> writes:
> Am 25.01.2016 um 10:07 schrieb David Kastrup:
>
>> What actual problem are you trying to address here?
>
> LilyPond will consider "C:\\some\\path" an absolute path when compiled
> under Windows, but not when compiled under Linux/Mac. So this means: it
> works according to the current OS.
>
> But LilyPond will consider "/some/path" an absolute path regardless of
> the OS.
>
> I think LilyPond should either *always* act corresponding to the OS
> (so "/some/path" will be considered absolute only on *NIX) or it
> should always return true to *all* possible ways of specifying an
> absolute path.
Why? I repeat: What actual problem are you trying to address here?
With "actual" meaning something affecting a user in a negative and/or
unexpected way. As far as I remember, / cannot ever be in the name part
of a file name with either Unix or Windows. According to Microsoft:
Which characters can't be used in a file name?
You can't use any of the following characters in a file name: \ / ?
: * " > < |
In Unix, there are only two forbidden characters, / and NUL. But at any
rate, there does not seem to be _any_ potential for a problem/confusion
here.
What actual problem are you trying to address here?
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
