[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: ARRAY-TYPE-ELEMENT-TYPE-SEMANTICS (Version 9)
- To: Jon L White <jonl@lucid.com>
- Subject: Re: Issue: ARRAY-TYPE-ELEMENT-TYPE-SEMANTICS (Version 9)
- From: masinter.pa@Xerox.COM
- Date: 10 Jan 89 14:41 PST
- Cc: masinter.pa@Xerox.COM, cl-cleanup@Sail.Stanford.Edu
- In-reply-to: Jon L White <jonl@lucid.com>'s message of Tue, 10 Jan 89 04:11:19 PST
Even though all implementations "must have some code" that does the
upgrading, the code need not be a Lisp function. For example, KCL might do
the upgrading in C, or an implementation might simply upgrade all array
element types to T.
There's a cost associated with adding functions to the LISP package,
including them in the documentation and specification beyond the cost of
requiring all implementations to write them -- the cost is in the overhead
of testing, documentation, user understanding, burden on implementation
model. The benefit of UPGRADE-ARRAY-ELEMENT-TYPE--namely, that it doesn't
CONS as much as the portable definition--seems very small and I don't think
it outweighs the cost.