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
>
Just like with current Racket, both futures and places run in a single
process.
Sam
On Tue, May 22, 2018, 2:39 AM Piyush Katariya
wrote:
> Thanks Sam.
>
> When you say Racket 7's "cs" variant can use Future and Places to leverage
> multiple CPU cores, is it one OS process or multiple ?
>
> --
>
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
Hello all! Sorry for the cross-post, but I've been doing more
development in Racket lately from GuixSD... and who wouldn't want a
scheme-based distribution and a scheme language's tooling to get along
better?
Unfortunately when I try to install packages with "raco pkg install"
I get errors like t
On Mon, May 21, 2018 at 11:21 AM Jay McCarthy
wrote:
> This is very cute! Can you point to a fun example? I looked through
> the repo and it wasn't obvious where some tests and examples were.
>
> Jay
>
Here's a variety of small examples.
Sometimes, I just want to wait until a bunch of stuff is
I'm sure I'm not the only one who would like to see these (and other examples
you have handy) added to your `event-lang` docs.
> On May 22, 2018, at 7:29 AM, Eric Griffis wrote:
>
> Here's a variety of small examples.
--
You received this message because you are subscribed to the Google Grou
Hi Matthew,
Thanks for clarifying this.
It seems to me that `build-path/convention-type` is very difficult to use
correctly: it is very easy for someone working on a Linux machine to just
use this function with a 'unix convention and plain strings, under the
assumption that it will work corre
FYI, I made another potentially breaking change to `html-parsing`, and
so have incremented the major version number, to 6.0.
Sorawee Porncharoenwase found a case in which the parser was doing the
wrong thing for a real-world example of contemporary HTML. It turned
out to be in some 17 year-ol
8 matches
Mail list logo
