[racket-users] Call for Participation: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

2017-09-20 Thread Andrei Chis
** Call for Participation ** 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Collocated with SPLASH 2017) http://conf.researchr.org/track/sle-

[racket-users] syntax-original? different in expanded code than during expansion

2017-09-20 Thread Spencer Florence
The program: ``` #lang racket (define-syntax (exp stx) (define a (local-expand (cadr (syntax->list stx)) 'expression '())) (define one (cadr (syntax->list a))) (displayln (list one (syntax-original? one))) a) (exp 1) ``` prints `(# #f)`. However if I open the macro stepper in and step

Re: [racket-users] syntax-original? different in expanded code than during expansion

2017-09-20 Thread Alexis King
To understand this, note that (syntax-original? stx) is only #t when *both* of the following things are true: 1. stx has the special, opaque syntax property that syntax-original? knows how to look for. 2. stx has no macro-introduction scopes. The first point is satisfied by read-syntax,

Re: [racket-users] syntax-original? different in expanded code than during expansion

2017-09-20 Thread Matthias Felleisen
Is it a good idea that we can synthesize “original looking code”? > On Sep 20, 2017, at 4:48 PM, Alexis King wrote: > > To understand this, note that (syntax-original? stx) is only #t when > *both* of the following things are true: > > 1. stx has the special, opaque syntax property that syn

Re: [racket-users] syntax-original? different in expanded code than during expansion

2017-09-20 Thread Robby Findler
In my opinion, it is too hard, not too easy to synthesize such syntax objects. After all, I can make ports and I can call read-syntax (which is what I end up doing sometimes, annoyingly). The point is that syntax-original? implies that DrRacket treats the syntax objects differently. Most of the tim