| commit | 2f1a6b94cbf431d7290c57c441a5a6c3b2a29be1 | |
| author | Douglas Katzman <dougk@google.com> | |
| Tue, 1 Sep 2015 01:06:03 +0000 (31 21:06 -0400) | ||
| committer | Douglas Katzman <dougk@google.com> | |
| Tue, 1 Sep 2015 01:43:49 +0000 (31 21:43 -0400) | ||
| tree | 14f8ac8a2dab3d519a1e29bee3d3d0de9922ce4a | treesnapshot (tar.gz zip) |
| parent | 9966d2d4ed16bd992a7b15c4f527fb30b97b47d3 | commitdiff |
Avoid forward references to PARSE-mumble-TYPE condition classes.
Also, since the debugger likes to print conditions, ensure that
obsolete conditions are not as recursively error inducing.
The interpretation taken is that technically it is allowed not
to signal an error on encountering an obsolete condition instance
(for the purpose of printing), because undefined behavior occurred
as soon as the condition class was incompatibly redefined,
therefore any behavior (such as not signaling) is permissible.
Also, since the debugger likes to print conditions, ensure that
obsolete conditions are not as recursively error inducing.
The interpretation taken is that technically it is allowed not
to signal an error on encountering an obsolete condition instance
(for the purpose of printing), because undefined behavior occurred
as soon as the condition class was incompatibly redefined,
therefore any behavior (such as not signaling) is permissible.