[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

functions that return nonstandard extra values

To: DCP@SCRC-QUABBIN.ARPA
Subject: functions that return nonstandard extra values
From: "George J. Carrette" <GJC@MIT-MC.ARPA>
Date: Mon, 4 Nov 85 22:00:48 EST
Cc: common-lisp@SU-AI.ARPA, AS%hplabs.csnet@CSNET-RELAY.ARPA
In-reply-to: Msg of Mon 4 Nov 85 19:25 EST from David C. Plummer <DCP at SCRC-QUABBIN.ARPA>

On the bright side, the existence of a standard helps system maintainers
to resist users continually asking for changes to the language that
have but minor benefit, such as this gethash thing. With only
a minor change in efficiency the user could store (CONS <key> <value>)
in the hash table, and get what he wanted, the EQ'ified key and
the value. If a user was really interested in efficiency he wouldnt
use the hairy system-provided hash table implementations anyway.

Follow-Ups:
- functions that return nonstandard extra values
  - From: Daniel L. Weinreb <DLW@SCRC-QUABBIN.ARPA>
- functions that return nonstandard extra values
  - From: David C. Plummer <DCP@SCRC-QUABBIN.ARPA>

Prev by Date: functions that return nonstandard extra values
Next by Date: Declaring Functions
Previous by thread: functions that return nonstandard extra values
Next by thread: functions that return nonstandard extra values
Index(es):
- Date
- Thread