Summary

guard-procedure should not be reinvoked when restoring parameter value using `parameterize'

Metadata

• Id: 4c232b0bae42d024eb30b6016b4ed314ac7daf15
• Trac id: 473
• Type: defect
• Reporter: felix
• Owner: felix
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: fixed
• Priority: major
• Milestone: 4.9.0
• Version: 4.6.x
• Changetime: 2012-09-24 21:47:48 UTC
• Created: 2011-01-06 14:24:34 UTC
• Keywords: parameterize

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`).

Changes and comments

[2011-03-28 09:30:29 UTC] felix changed milestone from 4.7.0 to 4.8.0

[2011-08-01 09:08:44 UTC] felix changed status from new to closed

[2011-08-01 09:08:44 UTC] felix set resolution to fixed

[2011-08-01 09:08:44 UTC] felix wrote:

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).

[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0

[2012-09-24 21:47:48 UTC] felix wrote:

Milestone 4.8.0 deleted