Re: [racket-users] ssl-connect: requested protocol not supported ('auto)

> On Sep 19, 2015, at 11:44 AM, John B. Clements > wrote: > > >> On Sep 19, 2015, at 11:40 AM, 'John B. Clements' via users-redirect >> wrote: >> >> I’m trying to use an older OS (Debian Squeeze) to compile my shared >> libraries (to make

Re: [racket-users] Re: typed/racket + rackunit = trouble

that's great! Robby On Sat, Sep 19, 2015 at 4:38 PM, Gustavo Massaccesi wrote: > There is something very strange with memq vs member: > http://pasterack.org/pastes/80845 (note: I added one 0 to the loop > constants) > > I used two mutable variables eq?? and equal?? to avoid

Re: [racket-users] Re: typed/racket + rackunit = trouble

Probably the difference is caused by the diference of the Racket version in your machine and in PasteRack. In my machine: *** Using Racket 6.2 cpu time: 687 real time: 702 gc time: 0 cpu time: 14352 real time: 14838 gc time: 0 cpu time: 3619 real time: 3674 gc time: 0 cpu time: 5429 real time:

Re: [racket-users] Re: typed/racket + rackunit = trouble

There is something very strange with memq vs member: http://pasterack.org/pastes/80845 (note: I added one 0 to the loop constants) I used two mutable variables eq?? and equal?? to avoid (most of) the optimizations and I get that the time with equal? is 2x than the time with eq?. This is closer

Re: [racket-users] Re: typed/racket + rackunit = trouble

Impressive optimization! I wonder what it was that changed specifically. Sam On Sat, Sep 19, 2015 at 9:02 PM, Gustavo Massaccesi wrote: > Probably the difference is caused by the diference of the Racket > version in your machine and in PasteRack. In my machine: > > *** Using

Re: [racket-users] Re: typed/racket + rackunit = trouble

When I run my original program on my own machine (instead of Pasterack), the difference is more like 2-3x. So my original email overstated the speed difference a bunch. I don't know what's going on that makes it so different on pasterack. An interesting side note -- we tried this program in

[racket-users] ssl-connect: requested protocol not supported ('auto)

I’m trying to use an older OS (Debian Squeeze) to compile my shared libraries (to make sure that they run on all machines), and I’m running into an interesting error when I try to use ‘raco pkg install’: clements@li96-50:/lib$ raco pkg install memoize Resolving "memoize" via

[racket-users] Eval namespace revisited ...again

Hi all, I'm working on a generic solution to distributed computing/ IoT/ M2M/ scheduled task handling etc. basing on messaging. The emphasis is on usability so it is essential to allow running functions identically despite of where they are run. The obvious thing to expect is that when sending an

Re: [racket-users] embedded Racket + runtime paths = ?

I've added a `--runtime ` argument to `raco ctool --cmods`, which gathers runtime files into and makes the embedded modules refer to them in (which is expected to be relative to the executable, but see also the `--runtime-access` option). The embedding executable must call scheme_set_exec_cmd()

Re: [racket-users] Busy waiting?

I've pushed a repair that's intended to fix this problem. The bug was in internal handling of file descriptors in the case that poll() is available and epoll() isn't. In case it's useful, I also added `--enable-racket=auto` support`, which automates the step of building a Racket executable for

[racket-users] Redex: call for alpha-equivalence beta testers

Paul Stansifer has been implementing the ideas from his dissertation work in Redex and is now ready to share them with the world. Thanks to Paul, Redex languages now understand binding structure, meaning that if you write a substitution function that just blindly substitutes, it will actually

Re: [racket-users] Redex: call for alpha-equivalence beta testers

> and then get Paul's version: > > cd redex > git remote add paul https://github.com/paulstansifer/redex-1.git > git checkout public > raco setup This didn't quite work for me the first time I tried it, I needed to run `git fetch paul` before the checkout to make it work. Looking forward