[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: REQUIRE-PATHNAME-DEFAULTS (version 1)
- To: gz@spt.entity.com (Gail Zacharias)
- Subject: Re: Issue: REQUIRE-PATHNAME-DEFAULTS (version 1)
- From: masinter.pa@Xerox.COM
- Date: 14 Sep 88 01:20 PDT
- Cc: CL-Cleanup@SAIL.Stanford.EDU, KMP@STONY-BROOK.SCRC.Symbolics.COM, pierson%mist@MULTIMAX.ARPA
- In-reply-to: gz@spt.entity.com (Gail Zacharias)'s message of 14 Sep 88 02:11:45 EDT (Wed)
What I remember from a subcommittee meeting (that only included a small subset
of the people on the mailing list, unfortunately) is that we informally agreed
to do something of the sort; that is, to remove any operative definition of
PROVIDE and REQUIRE. The exact wording is tricky.
The issue I think is whether we think that programs that have recursive
requirements should be portable. I think so -- it is consistent with current
practice and the users issue.
I wonder if part of the way of handling this is to be more explicit about what
we all know: that LOAD, PROVIDE and REQUIRE have to cooperate to make this work
right.