#473 closed defect (fixed)
guard-procedure should not be reinvoked when restoring parameter value using `parameterize'
| Reported by: | felix winkelmann | Owned by: | felix winkelmann |
|---|---|---|---|
| Priority: | major | Milestone: | 4.9.0 |
| Component: | core libraries | Version: | 4.6.x |
| Keywords: | parameterize | Cc: | |
| Estimated difficulty: |
Description
(This was reported by Joo ChurlSoo)
Restoring the old value after execution of the body of a parameterize form will reinvoke the guard, which is incorrent, if it performs a conversion (for example number->string).
Change History (3)
comment:1 by , 15 years ago
| Milestone: | 4.7.0 → 4.8.0 |
|---|
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Possibly fixed. Parameter procedures now accept an optional 2nd argument that will skip the guard procedure, if it is true. This should also work for parameter-like procedures that do not explicitly check the argument count (and should be the case for all parameter-like procedures defined in the core libraries).