Cleanup Issue `BREAK-ON-WARNINGS-OBSOLETE`

Status: Passed, as amended, Mar 89 X3J13
Forum: Cleanup
Category: CLARIFICATION/CHANGE
References: *BREAK-ON-WARNINGS* (CLtL p432, CL Condition System p40) *BREAK-ON-SIGNALS* (CL Condition System p25)

With the advent of *BREAK-ON-SIGNALS*, *BREAK-ON-WARNINGS* is redundant and unnecessary.

Remove *BREAK-ON-WARNINGS*.

N/A

This will lead to simplification of the description of WARN.

Not only are the two variables overkill, but they have an effect in an identifiably but uselessly distinct place.

Most have *BREAK-ON-WARNINGS*.

slight.

Users will have to write (SETQ *BREAK-ON-SIGNALS* 'WARNING) rather than (SETQ *BREAK-ON-WARNINGS* T).

Since this is mainly done interactively and not in programs, the cost is slight.

The definition of WARN will be gratuitously cluttered.

Cost of non-adoption is avoided.

Slight improvement.

Pitman thinks this is a good idea, but doesn't think a lot of time should be wasted discussing the issue if there is strong opposition.

Cleanup Issue BREAK-ON-WARNINGS-OBSOLETE