On Tuesday, May 22, 2018 at 7:56:21 AM UTC-4, Matthew Flatt wrote: > > To build paths for a convention other than the current machine's > convention, you have to work in bytes instead of strings. > > (define (bs->p bs) (bytes->path bs 'unix)) > (build-path/convention-type 'unix (bs->p #"/") (bs->p #"foo") (bs->p > #"bar")) > > Roughly, strings don't work, because they have to be converted to bytes > using the locale's default encoding. Although strings are allowed for > the current platform's convention on the assumption that the current > locale's encoding is the right one, we've avoided building in any > assumption about the encoding for the other convention. > > Why is this the case? For that matter, why are strings and paths even separate datatypes? Racket is the only language I've ever seen that does this, and I can't figure out what the value add is. Especially since most 'path' functions will accept either paths or strings, it's clear that Racket *can* do all the relevant things without needing the 'path' type. Certainly the 'path' type causes a lot of friction when serializing or persisting.
> At Tue, 22 May 2018 03:51:03 -0700 (PDT), Alex Harsanyi wrote: > > I am trying to create a path named "/foo/bar" in Racket on a windows > > machine. build-path produces "/foo\\bar" and build-path/convention-type > > does not seem to work: > > > > > (path->string (build-path "/" "foo" "bar")) > > "/foo\\bar" ; I am running on a Windows machine, so this is expected > > > (path->string (build-path/convention-type 'windows "/" "foo" > "bar")) > > "/foo\\bar" > > > (path->string (build-path/convention-type 'unix "/" "foo" "bar")) > > ; build-path/convention-type: specified convention incompatible with > > string path element > > ; path element: "/" > > ; convention: 'unix > > > (path->string (build-path/convention-type 'unix "/foo" "bar")) > > ; build-path/convention-type: specified convention incompatible with > > string path element > > ; path element: "/foo" > > ; convention: 'unix > > > > It seems that I cannot specify the root path, "/", when the convention > type > > is set to 'unix. Technically, the error is correct, as "/" is not a > valid > > directory name, but I am not sure what to replace it with. The empty > string > > does not work either. The unix convention type seems to be more strict > > than the windows one: > > > > > (path->string (build-path/convention-type 'windows "./foo/" > "bar")) > > "./foo/bar" > > > (path->string (build-path/convention-type 'unix "./foo/" "bar")) > > ; build-path/convention-type: specified convention incompatible with > > string path element > > ; path element: "./foo/" > > ; convention: 'unix > > > > Is this a bug, or I am missing something? > > > > Alex. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Racket Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to racket-users...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
