[racket-users] Re: Testing for Packages

2020-05-26 Thread Alex Harsanyi
I am personally confused about what you think the problem is, so I just want to make sure that you know that you can develop and test a new package, or you can modify an existing package and test the modifications, without publishing the package. Basically in Racket you can: * create a new

Re: [racket-users] Testing for Packages

2020-05-26 Thread Alexis King
> On May 26, 2020, at 21:36, Robert Postill wrote: > > One thing that troubled me was that the tests seemed to be dependant on the > package already being installed. I think this is very common within the Racket ecosystem. I would guess that very few packages are consciously designed to be

[racket-users] Testing for Packages

2020-05-26 Thread Robert Postill
Hi, Inspired by the reply to https://stackoverflow.com/questions/62014612/how-to-test-a-racket-package-self-sufficiently, I decided to ask the question here. So a little background to the discussion. I've been looking at a racket package, and the package has a couple of collections. It's

[racket-users] pkgs.racket-lang.org Why are the links so inconsistent?

2020-05-26 Thread Simon Schlee
Hello, searching through a bunch of different packages I noticed that the code/download links are quite inconsistent. For some packages there is a download button clicking that button does nothing (in firefox) because it contains a git:// protocol url, here is an example package:

Re: [racket-users] Sandbox + 2htdp/image

2020-05-26 Thread Robby Findler
It might be easiest to just use the `image?` predicate from inside the sandbox. Get it out the same way you got the image itself out. Robby On Tue, May 26, 2020 at 6:22 PM Stephen Foster wrote: > The following returns #f and #t. How can I get it to return #t and #t? > > Context: I want to

[racket-users] Sandbox + 2htdp/image

2020-05-26 Thread Stephen Foster
The following returns #f and #t. How can I get it to return #t and #t? Context: I want to allow students to run Racket code on my server. But when I sandbox their code, I am getting back something that doesn't behave like a 2htdp/image object. I'm not exactly sure what it is. #lang racket

Re: [racket-users] Migrating from a "model-driven" language framework to Racket

2020-05-26 Thread Guillaume Savaton
Le mardi 26 mai 2020 21:45:21 UTC+2, johnbclements a écrit : > > In your case, the type checker would also be “resolving” lightweight > expressions like (assign (h1 a) a) into fully-decorated expressions like > (assign (port-ref half-adder h1 a) (port-ref full-adder a)) . > Does this make

Re: [racket-users] Migrating from a "model-driven" language framework to Racket

2020-05-26 Thread Guillaume Savaton
Le mardi 26 mai 2020 21:41:14 UTC+2, Sam Tobin-Hochstadt a écrit : > > I think the best way to implement what you describe for a "better > version" is as follows: > > Expand `(instance h1 half-adder-arch)` into something like > > (define-syntax h1 (half-adder-arch-info)) > I have seen this

Re: [racket-users] Migrating from a "model-driven" language framework to Racket

2020-05-26 Thread 'John Clements' via Racket Users
Okay, I could just be putting my foot in my mouth, here, but it sounds like you’re describing the kinds of things that are typically done by a type-checker. Have you considered adding a type-checking pass? It would contain an environment that maps names like “h1” to “types” that indicate that

Re: [racket-users] Migrating from a "model-driven" language framework to Racket

2020-05-26 Thread Sam Tobin-Hochstadt
I think the best way to implement what you describe for a "better version" is as follows: Expand `(instance h1 half-adder-arch)` into something like (define-syntax h1 (half-adder-arch-info)) Where `half-adder-arch-info` is an expansion-time structure describing half-adders. Then the `assign`

Re: [racket-users] Migrating from a "model-driven" language framework to Racket

2020-05-26 Thread Guillaume Savaton
Le mardi 26 mai 2020 03:59:59 UTC+2, johnbclements a écrit : > > > So far, I have made two attempts to work around these issues: (1) by > creating a metamodel-like data structure using Racket structs, and > transforming syntax objects into struct instances; or (2) using syntax > objects only

[racket-users] Re: GUI executable creating an annoying command line window

2020-05-26 Thread Philip Benade
Hi Alex I managed to get it working. Updating Dr.Racket to 7.7 did the trick. I should have thought of it sooner, but I became so wrapped up in looking for the problem in my code I didn't think of it. Thank you for your help. Regards Philip On Tuesday, 26 May 2020 11:50:58 UTC+2, Alex

Re: [racket-users] GUI executable creating an annoying command line window

2020-05-26 Thread Philip Benade
Hi Laurent Unfortunately no, nothing changes. Regards Philip On Tuesday, 26 May 2020 11:47:28 UTC+2, Laurent wrote: > > Does it change anything if you use #lang racket/gui instead of #lang > racket (require racket/gui)? > > On Tue, May 26, 2020 at 10:00 AM Philip Benade > wrote: > >> Hi All

[racket-users] Re: GUI executable creating an annoying command line window

2020-05-26 Thread Alex Harsanyi
I cannot reproduce this. If I create the executable from the command line using "raco exe --gui work-timer.rkt", or from DrRacket specifying GRacket as the "base", the console window does not show up. If I create the executable using "raco exe work-timer.rkt" or by specifying "Racket" as

Re: [racket-users] GUI executable creating an annoying command line window

2020-05-26 Thread Laurent
Does it change anything if you use #lang racket/gui instead of #lang racket (require racket/gui)? On Tue, May 26, 2020 at 10:00 AM Philip Benade wrote: > Hi All > > I have been trying to create a simple GUI with the racket/gui library. For > the most part it works but alongside my GUI it also

[racket-users] GUI executable creating an annoying command line window

2020-05-26 Thread Philip Benade
Hi All I have been trying to create a simple GUI with the racket/gui library. For the most part it works but alongside my GUI it also creates a command line window. You can see a screenshot of this in the attached picture. I found this discussion when I searched for a solution: