Another weird error:
#lang racket/base
(require racket/stxparam (for-syntax racket/base))
(define-syntax-parameter add (make-rename-transformer #'+))
(define-syntax add1 (make-rename-transformer #'add))
add1
;add1: identifier's binding is ambiguous
; context.:
; matching binding.:
; matching bi
>An imperative API makes functional abstraction harder. What are the main
>selling points for Scheme/Racket now?
I am a big believer in functional programming (and static types) for large
projects, but there is an undeniable bit of awkwardness compared to just
imperatively poking things for sma
1. On my Mac, I get the canvas, I see the circle, it sleeps for a second, the
circle goes away --- precisely because paint-callback is called and it draws
emptiness.
2. If you don't see this, I think you're encountering a bug. This behavior
should be the same across platforms. Report
3 matches
Mail list logo