@mflatt @stamourv @ryanc And/or whoever maintains racket these days: it looks like Racket 7’s gui isn’t working on OSX 10.7: https://stackoverflow.com/questions/51698819/cant-run-drracket-or-gracket-7-0

maintains the racket distribution process*

If we do have a minimum os x version requirement, we should probably document it somewhere (unless we already have and I just missed it.)

https://github.com/racket/racket/issues/2215

Okay cool, thanks.

I think the intended system requirements used to be listed on the download page, but we lost that somewhere along the way.

ya, I don’t see them anywhere. Would it make sense for one of us to add them back?

I have a (hopefully quick) question.. if that is an appropriate place to ask…

I am trying my hand at macros and ran into the following: http://pasterack.org/pastes/82625

@redwynskaja Try this out (requires Racket 7): (define-syntax (def-par stx) (syntax-parse stx [(_ name:id {~seq par:id val} ...) #:with [par-str ...] (map (compose symbol->string syntax-e) (syntax->list #'[par ...])) #'(define name (hash {~@ 'par-str val} ...))]))

That’s a nice solution! The construct ~@ is a nice trick.

That’s the part that needs Racket 7. :)

wow… thanks!

i will work through to understand

(map symbol->string (syntax->datum #’(par …))) hides the syntax-e

one question more :slightly_smiling_face:. the {} are used to match a certain pattern but without actually matching parentheses?

Oh, the curly braces are interchangeable with parens, just as square brackets are. Perhaps I shouldn’t have let my (nonstandard) stylistic choice leak into my example!

You could replace them with parens and it would work just fine. I just use the braces to highlight that I’m not actually matching or constructing a list.

Thanks again!