Re: [racket] htdp: functions of section 19 violate the grammar of section 8

It makes sense, yes. I mean, the overall message. But I'm trying to pinpoint where the grammar of section 8 tells me "no, you cannot put a function name in an argument of an application". I read again the entire section 8, am reading section 19 again and I still don't see it. I'll write my argument

Re: [racket] possibility of defining recontract-all-from-out

For a project last year, I developed a suite of syntactic abstractions that expand into contracted provides. With the core abstract you specify a header-file-like 'thing' and the exporting module(s) can then require this 'thing' to export identifiers. A re-export would work the same way. If my a

Re: [racket] error writing to stream port (Broken pipe; errno=32)

(with-handlers ((exn:fail? (lambda (x) "let's throw away the exception from a closed port")) ... do stuff with ports and pipes ...) [[ You probably need to provide more context to get truly useful answers. ]] On Sep 11, 2014, at 7:18 AM, Wolfgang Hukriede wrote: > Do I need to install a sig

Re: [racket] error writing to stream port (Broken pipe; errno=32)

Do I need to install a signal handler catching SIGPIPE? (Or replace the existing signal-handler?) Thanks! Racket Users list: http://lists.racket-lang.org/users

Re: [racket] error writing to stream port (Broken pipe; errno=32)

To expand a bit: the handling of the broken pipe seems okay to me, I just don't want to see the error message. Thanks! Racket Users list: http://lists.racket-lang.org/users

[racket] error writing to stream port (Broken pipe; errno=32)

How am I supposed to catch: error writing to stream port (Broken pipe; errno=32) ? Thanks, Wolfgang Racket Users list: http://lists.racket-lang.org/users