[Chicken-janitors] #606: make-pathname always uses / separator char

[Chicken Trac]

#606: make-pathname always uses / separator char
----------------------------+-----------------------------------------------
 Reporter:  zbigniew        |       Owner:  felix
     Type:  defect          |      Status:  new  
 Priority:  major           |   Milestone:  4.8.0
Component:  core libraries  |     Version:  4.7.x
 Keywords:                  |  
----------------------------+-----------------------------------------------
 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"
 }}}

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/606>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.