Summary
DSSSL extended lambda lists are unhygienic
Metadata
- Id: 0afd2ddefd510c2827ccb6b05edfe7287dd114f3
- Trac id: 806
- Type: defect
- Reporter: syn
- Owner:
- Cc:
- Status: closed
- Component: core libraries
- Estimated difficulty:
- Resolution: fixed
- Priority: minor
- Milestone: 5.1
- Version: 4.7.x
- Changetime: 2016-06-23 11:55:36 UTC
- Created: 2012-03-25 16:45:17 UTC
- Keywords:
Attachments
- 0afd2ddefd510c2827ccb6b05edfe7287dd114f3/attachments/0001-Add-test-case-for-DSSSL-extended-lambda-list-hygiene.patch
Description
There are a few hygiene problems with the DSSSL extended lambda lists. I was able to fix one but am stuck with the rest of them which seems to be related to macro-alias not resolving to the correct symbol name. Attached is a patch which adds a test case as well as the fix I was able to make.
Changes and comments
[2012-03-25 16:46:23 UTC] syn attached 0001-Add-test-case-for-DSSSL-extended-lambda-list-hygiene.patch (description=#f)
[2012-04-06 18:20:10 UTC] ckeen wrote:
I have committed the ##core#quote part of this patch to master as commit c75cc04a5e6cf570b83ab4df40834583aa5ed369, the issue remains open as macro-alias does not seem to rename macros at all
[2012-05-18 12:47:01 UTC] felix removed milestone 4.8.0
[2016-02-20 13:06:03 UTC] sjamaan set milestone to 5.1
[2016-02-20 13:06:03 UTC] sjamaan wrote:
Maybe worth investigating for 5.1, because 5.0 is probably more hygieniec
[2016-06-23 11:55:36 UTC] sjamaan changed status from new to closed
[2016-06-23 11:55:36 UTC] sjamaan set resolution to fixed
[2016-06-23 11:55:36 UTC] sjamaan wrote:
Fixed (hopefully completely) by 83198fc / 7d88987.