Re: Issue: TEST-NOT-IF-NOT (Version 1)

[Dan L. Pierson <pierson%mist@multimax.ARPA>]

I like the combination of FUNCTION-COMPOSITION and removing :TEST-NOT
and -IF-NOT from the language but am a little worried about breaking
existing programs.  Maybe this is place where we should formally
depricate a feature.  This would mean that:

    1. Implementations would be required to support :TEST-NOT and
       -IF-NOT until the next revision of the standard.
    2. The feature would appear in a special backwards compatability
       section of the standard.
    3. Textbooks and instructors would be encouraged not to teach
       the feature.
    4. Users would be warned not to use the feature for new code and
       to migrate existing code away from it.

Since most existing implementations will probably feel required to do
this sort of thing anyway for the convenience of their current
customer base, maybe we should make it official.

On the other hand, if everyone else just wants to dump this feature,
I'll go along.