Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

identifier equivalence bug #151

Closed
SaitoAtsushi opened this issue Dec 31, 2013 · 3 comments
Closed

identifier equivalence bug #151

SaitoAtsushi opened this issue Dec 31, 2013 · 3 comments

Comments

@SaitoAtsushi
Copy link

Hello. I found a bug.
There is difference between expectation and behavior in case of following.

(let ((unquote 'foo)) `(,'bar))

expect:
(,'bar) or ((unquote (quote bar)))

behavior:
(bar)

@justinethier
Copy link
Owner

Thanks for the report. I see that Chibi and Chicken have the expected behavior, although Bigloo prints (bar).

Maybe I just need more time, but can you explain a bit more why you expect a result other than (bar)?

@SaitoAtsushi
Copy link
Author

See 4.2. "The constructs in this section are hygienic, as discussed in section 4.3."

This section contain quasiquote.

There is a concrete example for explain hygine in the later of section 4.3.2.

justinethier added a commit that referenced this issue Jan 1, 2014
Preserve macro hygiene when using code that contains explicit renaming macros contained within syntax-rules macros. The issue was that the syntax-rules system was not passing renamed variables across to the ER system, so an identifier could be renamed by syntax-rules but the ER macro would then have no knowledge of the rename and would be unable to use `rename` to make the identifier hygienic.
justinethier added a commit that referenced this issue Jan 1, 2014
@justinethier
Copy link
Owner

The issue was that the syntax-rules system was not passing renamed variables across to the explicit renaming macro system that is used to implement quasi-quotation. So an identifier could be renamed by syntax-rules but the ER macro would then be unable to use rename to make the identifier hygienic. This has been fixed.

Thanks again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants