Re: Issue: REQUIRE-PATHNAME-DEFAULTS (Version 5)

[Dan L. Pierson <pierson@mist.encore.com>]

    Its a little late, but I just noticed: if you take out PROVIDE and REQUIRE,
    shouldn't you also remove *MODULES*?
    
OK, new version will be out in a minute.

    I don't know why the "safety net" idea isn't workable without forbidding
    REQUIRE from loading files.
    
Because people using implementations in which REQUIRE loads files
won't just use it as a safety net (because it doesn't act like one, in
fact it silently acts as just the opposite).  Then, when applications
 from such implementations are ported to "safety net" implementations
errors will occur.  While this does not mean the feature is bad, it
does mean that it will harm rather than aid code portability.  As
such, it does not belong in the standard, portable language.