Filename.dirname on Win32 UNC paths #7912
Comments
|
Comment author: @dbuenzli I guess you already know that Windows paths are hairy. Here's a good reference about them: https://docs.racket-lang.org/reference/windowspaths.html The which I ported from the Fpath library should determine the start of a windows path using |
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Original bug ID: 7912
Reporter: @alainfrisch
Status: new
Resolution: open
Priority: normal
Severity: minor
Category: standard library
Monitored by: @nojb @dbuenzli
Bug description
# let s = "\\\\foo" in Filename.(dirname s, basename s);; - : string * string = ("\\", "foo") # let s = "\\\\foo" in Filename.(concat (dirname s) (basename s));; - : string = "\\foo"Note that the initial double backslash has been transformed to a single-one, such changing the original path (an absolute one) to a path relative to the current drive. The doc claims that :
Technically, \foo is not a valid file name, but it is a valid path.
Filename.dirname has some special logic under Win32 to extract the "drive" component. Shouldn't something similar be done for such UNC server component, which are also "roots"?
The text was updated successfully, but these errors were encountered: