Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(object_based_programming_techniques.md): correct typos #534

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix(object_based_programming_techniques.md): correct typos #534

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c40d5a
fix(object_based_programming_techniques.md): correct typos
nbehrnd Feb 28, 2025
285fe37
Merge branch 'main' into main
nbehrnd Mar 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/learn/oop_features_in_fortran/object_based_programming_techniques.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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,

Expand Down