Skip to content

Commit 2d2ae5e

Browse files
committed
fix(array_handling.md): edit section to inline style
For better readability and closer correspondence to the original document, a section was edited to provide snippets of code in inline style. Signed-off-by: Norwid Behrnd <[email protected]>
1 parent 0323bfa commit 2d2ae5e

File tree

1 file changed

+5
-20
lines changed

1 file changed

+5
-20
lines changed

source/learn/f95_features/array_handling.md

Lines changed: 5 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -292,26 +292,11 @@ we can declare an array of that type:
292292
type(fun_del), dimension(10, 20) :: tar
293293
```
294294

295-
and a reference like
296-
297-
```f90
298-
tar(n, 2)
299-
```
300-
301-
is an element (a scalar!) of type `fun_del`, but
302-
303-
```f90
304-
tar(n, 2)%du
305-
```
306-
307-
is an array of type `real`, and
308-
309-
```f90
310-
tar(n, 2)%du(2)
311-
```
312-
313-
is an element of it. The basic rule to remember is that an array element
314-
always has a subscript or subscripts qualifying at least the last name.
295+
A reference like `tar(n, 2)` is an element (a scalar!) of type
296+
`fun_del`, but `tar(n, 2)%du` is an array of type `real`, and
297+
`tar(n, 2)%du(2)` is an element of it. The basic rule to remember
298+
is that an array element always has a subscript or subscripts
299+
qualifying at least the last name.
315300

316301
## Array subobjects (sections)
317302

0 commit comments

Comments
 (0)