Re: [racket-users] Why custom-display of printable<%> interface is called twice?

Someone had a very similar question about `printable<%>`, including both the confusion about multiple calls and the bug of failing to use the `out` port, on Stack Overflow recently: https://stackoverflow.com/questions/55975708/racket-equivalents-of-pythons-repr-and-str/56759937#56759937 Since thes

Re: [racket-users] Re: Racket2 possibilities

пятница, 26 июля 2019 г., 23:35:45 UTC+3 пользователь Hendrik Boom написал: > > One of the great things about Idris is its dependent types, and the > way they can be used for (constructive) formal logic. I was > experimenting with them in the 80's. > > To make them into a secure logic, however

Re: [racket-users] Directory-specific installation of packages?

On Sunday, July 28, 2019 at 3:48:24 PM UTC+8, james.geddes wrote: > > > My workaround is to tell my colleagues to use homebrew to install Racket; > then use `raco pkg` to install the app; and to specify `(define > racket-launcher-names …)` in the info.rkt file to make an executable. > It’s a wo

Re: [racket-users] Re: Racket2 possibilities

If anyone wants to collaborate on doing something novel related to visual programming, I've previously done industry R&D work on that, and am open to serious academic or commercial efforts. Atlas Atlas wrote on 7/28/19 6:53 PM: Found this interesting video on GopherCon https://www.youtube.com/

[racket-users] Re: Racket2 possibilities

Found this interesting video on GopherCon https://www.youtube.com/watch?v=Ps3mBPcjySE Speaker raises questions about what a program code is and how it should look -- You received this message because

Re: [racket-users] [FFI] malloc, maximum number of bytes

Okay, got to the bottom of it. racket-mode uses racket-memory-limit that is set to 2048 by default. Setting it to 0 makes it unlimited. On Sunday, July 28, 2019 at 8:19:11 PM UTC+2, Matthew Flatt wrote: > > Ah, it's possible that Racket mode sets a limit on Racket's memory use, > just like DrRac

Re: [racket-users] [FFI] malloc, maximum number of bytes

Ah, it's possible that Racket mode sets a limit on Racket's memory use, just like DrRacket does. That kind of memory limit (enforced within Racket, instead of by the OS) is based on GCable memory, so it doesn't limit 'raw allocation. At Sun, 28 Jul 2019 11:12:04 -0700 (PDT), Peter Samarin wrote: >

Re: [racket-users] [FFI] malloc, maximum number of bytes

I just rerun the example on the commandline and it works just fine with larger numbers of bytes. I use emacs and racket-mode by Greg Hendershot. I will check how that starts racket at some other time. Thanks Matthew! On Sunday, July 28, 2019 at 8:06:09 PM UTC+2, Matthew Flatt wrote: > > There sh

Re: [racket-users] [FFI] malloc, maximum number of bytes

There should be no special limit on 'atomic memory, and I haven't been able to replicate this behavior, yet. Can you say more about how you're running (e.g., in DrRacket versus command-line `racket`)? Also, although it's difficult to see how it could matter, which Linux distribution do you use? A

[racket-users] [FFI] malloc, maximum number of bytes

Hi all, I am using Racket v7.3, Linux x86_64 version. I want to allocate large (tens of gigabytes) chunks of memory with Racket's malloc and use them for some BLAS/LAPACK routines. The downloaded version of Racket lets me allocate only 2^31 "atomic" bytes. 2^31+1 bytes produce an "out of memory"

Re: [racket-users] Directory-specific installation of packages?

On Sun, Jul 28, 2019 at 08:48:20AM +0100, James Geddes wrote: > > In general, I now have the sense that there are OS-specific package managers, > and there are language-specific package managers, and they do not play nicely > with each other. This is a real problem. It's not clear what the sol

Re: [racket-users] Why custom-display of printable<%> interface is called twice?

Thanks, it works! On Sunday, July 28, 2019 at 5:54:06 PM UTC+8, Sorawee Porncharoenwase wrote: > > I’m not sure why it’s like that, but I know what’s the problem and how to > fix it. > > custom-display and custom-write provide the output port to you. You are > supposed to write to the port. > >

Re: [racket-users] Why custom-display of printable<%> interface is called twice?

I’m not sure why it’s like that, but I know what’s the problem and how to fix it. custom-display and custom-write provide the output port to you. You are supposed to write to the port. (define/public (custom-display out) (displayln "custom-display" out)) (define/public (custom-write

[racket-users] Why custom-display of printable<%> interface is called twice?

Hi, I created a simple class to test the printable<%> interface: (define my-class% (class* object% (printable<%>) (super-new) (define/public (custom-display out) (displayln "custom-display")) (define/public (custom-write out) (writeln "custom-write")) (define/public (

Re: [racket-users] Directory-specific installation of packages?

Tom, Stephen, Many thanks for the advice. In the end, I gave up on a single homebrew-able install. I could not find a way to have homebrew manage an app I created in Racket. During the homebrew-controlled installation process, Racket’s package manager tries to download other Racket packages; a