id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	difficulty
606	make-pathname always uses / separator char	Jim Ursetto	felix winkelmann	"Documentation says it uses the platform specific separator but it does not.  You need a second (maybe expensive) pass through normalize-pathname.  Is the documentation right or wrong?  If wrong, what is the point of make-pathname?

Note: at least on mingw it still works to access a file with mixed or redundant pathname separators, so it may be ugly but the practical impact is unknown.

{{{
;; bad
(make-pathname ""foo"" ""bar"")
 ; => ""foo/bar""
(make-pathname ""foo\\"" ""bar"")
 ; => ""foo\\/bar""

;; good
(normalize-pathname (make-pathname ""foo"" ""bar"")
 ; => ""foo\\bar""
(normalize-pathname (make-pathname ""foo\\"" ""bar"")
 ; => ""foo\\bar""
}}}"	defect	closed	major	4.9.0	core libraries	4.7.x	fixed