[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: PACKAGE-CLUTTER (Version 2)
- To: Moon@STONY-BROOK.SCRC.Symbolics.COM
- Subject: Issue: PACKAGE-CLUTTER (Version 2)
- From: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Tue, 27 Sep 88 13:04 EDT
- Cc: CL-Cleanup@SAIL.Stanford.EDU
- In-reply-to: <19880927040206.4.MOON@EUPHRATES.SCRC.Symbolics.COM>
I'm concerned about things mentioned in the spec as functions
which turn out to also be variables and vice versa. Ditto for
types. If either the system or any user application defines such,
it gets forced down everyone's throat and potentially clobbers
someone else's supposedly private application. It also reduces
the level of error checking provided to users who think they're
getting strict CLtL by just using things on LISP.
How would you feel about something like the following. It's
broader, but still tries to be specific...
Symbols on the LISP package may have function or macro
definitions, variable definitions or SPECIAL proclamations, or
type definitions only if explicitly permitted in the specification.
Neither users nor implementors are permitted to add new kinds of
definitions for these symbols.