Issue DEFCLASS-READER-FUNCTION-NAME
Issue: DEFCLASS-READER-FUNCTION-NAME

Forum: Editorial

References: DEFCLASS

Category: CLARIFICATION/CHANGE

Edit history: 2004-07-20, Version 1 by Bruno Haible

Status: For CLiki consideration

Problem Description:

The specification for DEFCLASS is a bit strange - in particular the use of reader-function-name for both :reader and :accessor, with two different descriptions given.

Proposal (DEFCLASS-READER-FUNCTION-NAME:USE-ACCESSOR):

In DEFCLASS, use accessor-function-name in place of reader-function-name.

Test case:

Rationale:

Current practice:

Cost to Implementors:

Cost to Users:

Cost of Non-Adoption:

Benefits:

Clarity.

Aesthetics:

Discussion:
  • Bruno Haible supports USE-ACCESSOR.

This page is presently Uncategorized: please add appropriate topic markers and remove this text