You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 159 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
I am using ocaml-3.00 under Windows. According to the documentation
for the Filename module, dirname and basename should satisfy the
following property:
concat (dirname name) (basename name)
returns a file name which is equivalent to name.
But:
dirname "c:/windows" = "c:",
basename "c:/" = "windows"
and "c:windows" is a relative pathname to the file windows in
the current directory (provided it is on the c: drive)
Similarly:
dirname "c:/" = "c:",
basename "c:/" = ""
and "c:" is the current directory, not "c:/"
(It doesn't matter whether / or \ is used, the results are the same.)
-Trevor
The text was updated successfully, but these errors were encountered:
I am using ocaml-3.00 under Windows. According to the documentation
for the Filename module, dirname and basename should satisfy the
following property:
concat (dirname name) (basename name)
returns a file name which is equivalent to name.
But:
dirname "c:/windows" = "c:",
basename "c:/" = "windows"
and "c:windows" is a relative pathname to the file windows in
the current directory (provided it is on the c: drive)
Well spotted. I just fixed Filename.dirname so that it doesn't strip
the "/" or "" immediately following a drive specification.
Original bug ID: 159
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
I am using ocaml-3.00 under Windows. According to the documentation
for the Filename module, dirname and basename should satisfy the
following property:
But:
Similarly:
(It doesn't matter whether / or \ is used, the results are the same.)
-Trevor
The text was updated successfully, but these errors were encountered: