[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MISMATCH/MAXPREFIX/MAXSUFFIX
- To: Common-Lisp%SU-AI@USC-ECL
- Subject: MISMATCH/MAXPREFIX/MAXSUFFIX
- From: Skef Wholey <Wholey@CMU-CS-C>
- Date: Fri, 22 Apr 1983 20:19:00 -0000
- Cc: Bernard S. Greenberg <BSG%SCRC-TENEX@MIT-MC>
- In-reply-to: Msg of 22 Apr 1983 09:20-EST from Bernard S. Greenberg <BSG%SCRC-TENEX at MIT-MC>
- Mail-from: ARPANET site SU-AI rcvd at 22-Apr-83 1334-PST
Having implemented these losers several times (as the manual changed in
creative ways), I'd be overjoyed to see them flushed forever. Leonard Zubkoff
told me that he suggested them to Guy as functions one might use in an editor's
redisplay. The editor Rob MacLachlan and I are writing have not used these
things at all -- the amount of time it takes to decide which function with
which keywords to use, and what the value returned means is far greater than
the time it takes to write a loop that does exactly the right thing (but this
is a different problem). I can understand REMOVE, DELETE, MEMBER, and REDUCE
being generic sequence functions, but if MAXPREFIX and MAXSUFFIX aren't
flushed, perhaps they should be made into string-only functions.