From 74bf1b29b8cef573908180e6ab00cfeb6f324b46 Mon Sep 17 00:00:00 2001 From: Mark Wooding Date: Sat, 27 Jul 2019 17:21:16 +0100 Subject: [PATCH] doc/structures.tex, lib/sod-structs.3: Fix unclear language. --- doc/structures.tex | 6 +++--- lib/sod-structs.3 | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/structures.tex b/doc/structures.tex index 6532dbd..37ca9e3 100644 --- a/doc/structures.tex +++ b/doc/structures.tex @@ -450,9 +450,9 @@ superclass in the same chain, and each slot must be stored in exactly one place. The layout of vtables doesn't have this second requirement: it doesn't matter that there are multiple method entry pointers for the same effective method as long as they all work correctly. Indeed, it's essential -that they do, because each chain's method entry function will need to apply a -different offset to the receiver pointer before invoking the effective -method. +that there are multiple entry pointers, because each chain's method entry +function will need to apply a different offset to the receiver pointer before +invoking the effective method. A vtable for a class $C$ with chain head $H$ has the following general structure. diff --git a/lib/sod-structs.3 b/lib/sod-structs.3 index 11134c8..161fc4e 100644 --- a/lib/sod-structs.3 +++ b/lib/sod-structs.3 @@ -705,7 +705,7 @@ it doesn't matter that there are multiple method entry pointers for the same effective method as long as they all work correctly. -Indeed, it's essential that they do, +Indeed, it's essential that there are multiple entry pointers, because each chain's method entry function will need to apply a different offset to the receiver pointer before invoking the effective method. -- 2.11.0