Issue DEFCONSTANT-PREVIOUS-VALUE
Issue: DEFCONSTANT-PREVIOUS-VALUE
Forum: Editorial
References: DEFCONSTANT
Category: CLARIFICATION/CHANGE
Edit history: 2004-07-20, Version 1 by Bruno Haible
Status: For CLiki consideration
- Problem Description:
- DEFCONSTANT says "The consequences are undefined if there are any bindings of the variable named by name at the time defconstant is executed or if the value is not eql to the value of initial-value." It is not clear what "the value" is.
- Proposal (DEFCONSTANT-PREVIOUS-VALUE:CLARIFY):
- Clarify "...or the symbol-value of name...", or equivalent.
- Test case:
-
- Rationale:
-
- Current practice:
-
- Cost to Implementors:
- None.
- Cost to Users:
- None.
- Cost of Non-Adoption:
-
- Benefits:
- Clarity.
- Aesthetics:
- Discussion:
- Bruno Haible supports proposal CLARIFY.
This page is linked from: Proposed ANSI Revisions and Clarifications
CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively