The documentation for module-compiled-exports says, "beware ... that
value bindings re-exported through a rename transformer are in the
syntax list instead of the value list."
Is it possible to identify which symbols in the syntax list represent
value bindings that were re-exported through a renam
I've been studying the numbers grammar in section 1.3.3 of the Racket
reference and I think I've spotted a few mistakes:
1. allows the imaginary part of an exact complex
number to be signed given that an exact rational may be signed:
::= []
::= /
::=i
The rule allows exact complex num
it repo, so it will be fixed in the next
> nightly build.
>
> Thanks for the report and test case!
>
> At Fri, 17 Jun 2011 17:33:56 +0100, milo arvidsson wrote:
>> (I'm using the latest build: mz-bin-i386-win32; version 5.1.1.6,
>> updated Friday, June 17 2011, 03
(I'm using the latest build: mz-bin-i386-win32; version 5.1.1.6,
updated Friday, June 17 2011, 03:50 EDT)
I've written versions of the following program using limited file,
string, and pipe ports with read-bytes-line-evt, read-char-evt,
read-line-evt, read-bytes-evt, read-string-evt, and regexp-ma
I'm getting contract violations when I use 'make-limited-input-port' with port
events.
For example, this program:
#lang racket/base
(require racket/port)
(define in (open-input-string "12345\n"))
(sync (read-line-evt (make-limited-input-port in 512)))
fails like this:
contract violation: expecte
In the following program, (sync (regexp-match-evt #rx"^..." in)) returns
'(#"123") but (file-position in) returns 0 instead of 3:
#lang racket/base
(require racket/port)
(define-values (in out) (make-pipe))
(display "12345" out)
(sync (regexp-match-evt #rx"^..." in))
(file-position in)
Tha
6 matches
Mail list logo