From a5c299e47c476a8f267ca1bc0a3636a349b41694 Mon Sep 17 00:00:00 2001 From: Kaz Kylheku Date: Fri, 28 Aug 2020 22:25:05 -0700 Subject: doc: rewrite multiple inheritance intro paragraph. * txr.1: Simplify the paragraph, and eliminate the introduction of the unnecessary term "strict single inheritance". --- txr.1 | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/txr.1 b/txr.1 index 5b401bfa..cf9514f3 100644 --- a/txr.1 +++ b/txr.1 @@ -26205,15 +26205,9 @@ This situation with two or more supertypes is called The contrasting term is .IR "single inheritance" , denoting the situation when a structure has exactly one supertype. -The term -.IR "strict single inheritance" -refers to the situation when a structure has exactly one supertype; -its supertype has at most one supertype; and, recursively, any additional -indirect supertypes all have at most one supertype. -Note: \*(TX 228 and older versions permitted only single inheritance, -thus programs were restricted to strict single inheritance. -\*(TL's multiple-inheritance is a straightforward extension of its -single inheritance semantics. +\*(TL's struct types initially permitted only single inheritance. +Multiple inheritance support was introduced in version 229, as a +straightforward extension of single inheritance semantics. In the .code make-struct-type -- cgit v1.2.3