<br><div class="gmail_quote">On Sun, Jan 11, 2009 at 6:49 AM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu">mflatt@cs.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="Wj3C7c"><br></div></div>Since most of the functions provided by `scheme/path' manipulate paths<br> without consulting the filesystem, I've changed them to work with paths<br> of any kind. (The exceptions are `normalize-path' and<br> `simple-form-path', which rely on the filesystem.)<br> </blockquote><div><br>Thanks for the changes Matthew.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'm less certain that it would be a good idea to change `string->path'<br> and `path->string' to allow with paths for a different system kind. The<br> problem is that string<->path conversions are inherently approximate;<br> some paths cannot be represented as strings</blockquote><div><br>I didn't realize that there are paths that cannot be written as strings.  What types of paths are those (or do you happen to have a link)? <br> <br></div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">, and for Unix paths, the<br> conversion depends on a locale-specific encoding. If you're<br> manipulating paths for a different system and you're forced to start<br> and end with strings, though, then UTF-8 is probably the right choice.<br> So I've added `string->some-system-path' and `some-system-path->string'<br> to `scheme/path'.<br> <font color="#888888"></font></blockquote><div><br>That'll be great help.  Thanks again, <br>yc<br><br></div></div>