From 0c40d5a1328b878ffc0cb71ae05b913b9ca8f683 Mon Sep 17 00:00:00 2001 From: Norwid Behrnd Date: Fri, 28 Feb 2025 16:32:00 +0100 Subject: [PATCH] fix(object_based_programming_techniques.md): correct typos A correction based on Beliavsky's reading.[1] [1] https://github.com/fortran-lang/webpage/issues/526 Signed-off-by: Norwid Behrnd --- .../object_based_programming_techniques.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/learn/oop_features_in_fortran/object_based_programming_techniques.md b/source/learn/oop_features_in_fortran/object_based_programming_techniques.md index a366b15ccb5..bfb0da458e4 100644 --- a/source/learn/oop_features_in_fortran/object_based_programming_techniques.md +++ b/source/learn/oop_features_in_fortran/object_based_programming_techniques.md @@ -151,9 +151,9 @@ to be aware of: 1. If all type components have the `private` attribute i.e., the type is **opaque** (not a Fortran term), it can only be used if the type declaration is accessed by host association (this is the same as for - nonallocatable/nonpointer components); -2. especially for container-like types, its semantics may be - incompatible with the programmers intentions for how the objects + nonallocatable/nonpointer components). +2. Especially for container-like types, its semantics may be + incompatible with the programmer's intentions for how the objects should be used. Item 2 is illustrated by the above object setups, specifically: @@ -479,7 +479,7 @@ case of polymorphic objects. ### Implementing move semantics Sometimes it may be necessary to make use of move instead of copy -semantics i.e., create a copy of an object and then getting rid of the +semantics i.e., create a copy of an object and then get rid of the original. The simplest way of doing this is to make use of allocatable (scalar or array) objects,