Re: [racket-users] Re: Readers and Namespaces

2017-08-17 Thread Sam Waxman
On Friday, August 18, 2017 at 1:11:16 AM UTC-4, Alexis King wrote: > > On Aug 17, 2017, at 21:52, Sam Waxman wrote: > > > > On a related note, I've read that read-syntax is supposed to return a > > syntax-object whose lexical context is stripped. Why is that? Doesn't > > that make it impossible f

Re: [racket-users] Re: Readers and Namespaces

2017-08-17 Thread Alexis King
> On Aug 17, 2017, at 21:52, Sam Waxman wrote: > > On a related note, I've read that read-syntax is supposed to return a > syntax-object whose lexical context is stripped. Why is that? Doesn't > that make it impossible for the language to know the difference > between the let I used in an earlier

[racket-users] Re: Readers and Namespaces

2017-08-17 Thread Sam Waxman
On Friday, August 18, 2017 at 12:47:45 AM UTC-4, Sam Waxman wrote: > I've recently run into some ambiguous identifier errors while writing a > reader, and I'm not sure how to solve them. > > The situation is as follows: > > I've created a version of "let" in one file. I'd like my reader to call

[racket-users] Readers and Namespaces

2017-08-17 Thread Sam Waxman
I've recently run into some ambiguous identifier errors while writing a reader, and I'm not sure how to solve them. The situation is as follows: I've created a version of "let" in one file. I'd like my reader to call it whenever the user types something like a = 3 body ... which should be rea

Re: [racket-users] Raising multiple nonfatal errors without stopping evaluation

2017-08-17 Thread George Neuner
On 8/17/2017 11:47 AM, David Storrs wrote: On Thu, Aug 17, 2017 at 2:44 AM, Sam Waxman > wrote: Hey all, One of the things that confuses me most in Racket is good error handling, and the continuations that are involved. Is it possible to raise an

[racket-users] MrLib Terminal contract violation

2017-08-17 Thread James
According to the documentation, below, the #:container parameter for the in-terminal function can either be a container object or #f but I get a contract violation if I explicitly pass #f to it. Is the documentation wrong or do I not understand? http://web.mit.edu/racket_v68/amd64_ubuntu1404/r

Re: [racket-users] Raising multiple nonfatal errors without stopping evaluation

2017-08-17 Thread David Storrs
On Thu, Aug 17, 2017 at 2:44 AM, Sam Waxman wrote: > Hey all, > > One of the things that confuses me most in Racket is good error handling, > and the continuations that are involved. > > Is it possible to raise an error, have the user see it, but then still go > on running the code? I can current

Re: [racket-users] Running a program in multiple languages at once

2017-08-17 Thread Jens Axel Søgaard
2017-08-17 8:40 GMT+02:00 Sam Waxman : > Hey all, I ended up figuring this out. > The solution was essentially to make a reader that looked like this: > > (define (read-syntax input-port) > (let ([copy1 (copy input-port)] > [copy2 (copy input-port)]) > (with-syntax ([mod1 (Lang1-rea