-
Discussions with NEMO developers have highlighted the fact that they really do not want to change their source code. In this issue we will investigate the feasibility (or otherwise) of adapting PSyclo…
-
According to R1102 the PROGRAM statement must have an associated name. However, if fparser2 encounters e.g.
program
write(*,*) "Hello"
end program
then it crashes with:
…
-
When parsing the following Fortran:
MODULE continuity_a030e_mod
IMPLICIT NONE
TYPE, EXTENDS(kernel_type) :: continuity_a030e_type
TYPE(arg), DIMENSION(10) :: meta_args = …
-
Apparently, `use module_name, only:` is valid Fortran. The example used is below.
```
program test_module_name
use module_name, only:
implicit none
integer :: i1, i2, i3
i1 = 1; i2 = 2; …
-
LFRic code uses preprocessing statements (Physics code and unit testing for now but there are likely to be more) and fparser2 is not able to parse them. For example,
```
#ifdef UM_PHYSICS
! UM BL…
-
fparser2 is mostly written in a single file which is unwieldy. It might be beneficial to split it into the different sections (rules) defined in the Fortran specification document and a generic file. …
-
The following fails to compile with fparser2 (but it works correctly with intel and gfortran):
```fortran
module mymod
use, intrinsic :: ISO_C_BINDING
implicit none
private
int…
-
Last commit to fparser that works was: 92c4c21d70ccebcc28ce4133dede187fa7769371:
Merge: 9cab778 d450724
Author: Andy Porter
Date: Wed Jun 27 10:24:46 2018 +0100
Merge pull r…
-
Hello All,
I am trying to build a conda package for OpenMC for conda-forge. I am running into many errors of the form:
```
[ 71%] Building Fortran object CMakeFiles/openmc.dir/src/angle_distributi…
-
I've been working with @wbinventor to build openmc. We have run into an issue compiling the code with gfortran and the latest v1.8.16 of HDF5 (not parallel). In particular, I see the following compila…