[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: REQUIRE-PATHNAME-DEFAULTS (Version 3)
- To: firstname.lastname@example.org
- Subject: Issue: REQUIRE-PATHNAME-DEFAULTS (Version 3)
- From: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Mon, 14 Nov 88 09:19 EST
- Cc: email@example.com.COM, firstname.lastname@example.org, cl-cleanup@SAIL.STANFORD.EDU, Bartley@mips.csc.ti.com
- In-reply-to: <8811140201.AA19970@bhopal>
I think the key is in this concept of deprecation.
The problem Gregor has indicated is that REQUIRE's presence there
means he has to put up with people saying he shouldn't be writing
DEFSYSTEM stuff but rather should be using REQUIRE/PROVIDE since
``they wouldn't be there if you weren't intended to use them.''
I have to say I've run into this same attitude.
I think it's acceptable to retain the 1-argument case in the spec
for sake of compatibility, but that we should throw it into the
deprecated bin so that it's clear that its mere presence there is
not an endorsement.