Re: [racket-users] Seeking a graphviz like, diagramming language for Racket

You might be interested in some of the line-drawing/edge-finding code here: https://github.com/samth/edinburgh-2017/blob/edinburgh-2017/lib.rkt#L144 Sam On Fri, Aug 25, 2017 at 7:12 PM, Andrew Gwozdziewycz wrote: > As promised, I mocked up my original vs a quick iteration

Re: [racket-users] Seeking a graphviz like, diagramming language for Racket

As promised, I mocked up my original vs a quick iteration using pict. It's not nearly as time consuming as I thought it'd be (took about 30 minutes not being familiar with the pict api): https://gist.github.com/apg/e193b3f4b1626397ebb3065947a6ae8a It's obviously not visually the same, but the

Re: [racket-users] 2htdp place world frame on screen

> On Aug 25, 2017, at 7:43 AM, Laurent wrote: > > Hi all, > > 2htdp is really neat and very useful, so thank you designers and programmers > of 2htdp! > > Sometimes I wish to place the window/frame on the screen at a particular > position, but the default sets it

Re: [racket-users] Unit tests for a #lang implementation

I forgot to explain why this fails: At Fri, 25 Aug 2017 14:59:14 +0200, Konrad Hinsen wrote: > (eval-syntax > (parameterize ([read-accept-lang #t] > [read-accept-reader #t]) > (read-syntax "test-module" > (open-input-string "#lang >

Re: [racket-users] 2htdp place world frame on screen

It's about non-teaching, which I suspect will not be in my favour :) On Fri, Aug 25, 2017 at 1:31 PM, Matthias Felleisen wrote: > > On Aug 25, 2017, at 7:43 AM, Laurent wrote: > > Hi all, > > 2htdp is really neat and very useful, so thank you

[racket-users] 2htdp place world frame on screen

Hi all, 2htdp is really neat and very useful, so thank you designers and programmers of 2htdp! Sometimes I wish to place the window/frame on the screen at a particular position, but the default sets it to (2, 2) as defined here:

[racket-users] Unit tests for a #lang implementation

Hi all, I have been trying for a while to write proper unit tests for a language implementation I am working on. By "proper" tests I mean tests that are run using raco test just like any other tests. Until now, I have a separate shell-script based testing framework that runs scripts written

Re: [racket-users] Unit tests for a #lang implementation

I'd say that using `eval` or `eval-syntax` is the right idea, but: * It's better to use `make-base-namespace` instead of `module->namespace`, since `(module->namespace 'racket/base)` gives you a namespace for the inside of `racket/base` instead of a top-level namespace that has imported

Re: [racket-users] 2htdp place world frame on screen

If you are interested in non-teaching and something LIKE 2htdp/world, then I suggest my package, lux. It uses generics (rather than classes for OO) and exposes a lot more options in the gui. (It doesn't expose starting position, but it would be appropriate to add them to lux/chaos/gui's make-gui.)

Re: [racket-users] Unit tests for a #lang implementation

At Fri, 25 Aug 2017 16:04:01 +0200, Konrad Hinsen wrote: > > Putting those together, and using `current-namespace` so that both > > `eval-syntax` and check-module-form` use the same namespace: > > Thanks, that works! > > At least to the point of not getting any error message. I can't say if a >

Re: [racket-users] Unit tests for a #lang implementation

Konrad, Matthew’s response is probably all you want in principle, but I think that your ‘unit test’ looks like another person’s ‘integration tests’. Both are useful. Wouldn’t you want to use unit tests to validate the parser independently of the macros that expand the S-expression syntax

Re: [racket-users] 2htdp place world frame on screen

:-) That’s not what I meant. I think that I need to figure out how to produce two version of ‘universe’ for the non-teaching world w/o completely forking the repo: — a functional one — an object-oriented one >From what I can tell, 2htdp/universe + image has some appeal as as simple

Re: [racket-users] Unit tests for a #lang implementation

Matthew, Putting those together, and using `current-namespace` so that both `eval-syntax` and check-module-form` use the same namespace: Thanks, that works! At least to the point of not getting any error message. I can't say if a module is actually defined. A plain (require

Re: [racket-users] Unit tests for a #lang implementation

Matthias, Matthew’s response is probably all you want in principle, but I think that your ‘unit test’ looks like another person’s ‘integration tests’. Both are useful. Wouldn’t you want to use unit tests to validate the parser independently of the macros that expand the S-expression syntax you

Re: [racket-users] Unit tests for a #lang implementation

On 25/08/2017 16:30, Matthew Flatt wrote: At Fri, 25 Aug 2017 16:04:01 +0200, Konrad Hinsen wrote: Putting those together, and using `current-namespace` so that both `eval-syntax` and check-module-form` use the same namespace: Thanks, that works! At least to the point of not getting any

Re: [racket-users] 2htdp place world frame on screen

On Fri, Aug 25, 2017 at 2:44 PM, Matthias Felleisen wrote: > > :-) > > That’s not what I meant. I think that I need to figure out > how to produce two version of ‘universe’ for the non-teaching > world w/o completely forking the repo: > > — a functional one > — an

[racket-users] Racket PPA updated for v6.10

Hi all, The Ubuntu PPA has been updated for v6.10. Sorry for the delay this time around and also for skipping a release! The PPA is available here: https://launchpad.net/~plt/+archive/ubuntu/racket for trusty, xenial, and zesty. The packaging repo (which tracks Debian's upstream repo) is

Re: [racket-users] 2htdp place world frame on screen

Great, thanks, I'll take a look this weekend. On Fri, Aug 25, 2017 at 6:01 PM, Jay McCarthy wrote: > On Fri, Aug 25, 2017 at 11:46 AM, Laurent > wrote: > > Jay: Oh that's right, I'd forgotten about Lux! Thanks for the reminder, I > > guess I

Re: [racket-users] 2htdp place world frame on screen

On Fri, Aug 25, 2017 at 11:46 AM, Laurent wrote: > Jay: Oh that's right, I'd forgotten about Lux! Thanks for the reminder, I > guess I should switch to that at some point. Correct me if I'm wrong, but it > seems to integrate well with 2htdp/image also. The default way