Jeremie Vandenplas

> Any luck? @jvdp1 No :( And then the holidays arrived. It is also difficult to run tests as I don't have a MacOS computer. Anyone with a MaCOS to...

> How about a function to return an array of strings instead? It is easy enough to query the size of the returned array and it saves actually reading the...

Thank you all for this work. The first specs were based on the document of the Fortran standard. The "class" section is required in the Fortran Standard, because the interface...

> Regarding the class, in the first para of your post, are you suggesting that we keep it or merely explaining why we have it? I understand that the first...

> It's cleaner but to me it looks a lot like function calls. What do you think about this: > > ```fortran > function linspace(start, end, n) result(res) > {integer(*),...

> I do not really like that there are three SPEC_*.md document on the top level, I am not sure to understand what you mean with "three SPEC_*.md"

> Where are you on indenting bodies of program units? I use 1-space for indenting subroutines/functions, but also interfaces, derived types,... I am fine with 2-space indents, and 80 (soft)-/132(hard)-character...

@urbanjost Thank you for spotting the errors and for the suggestions. I support this idea of an automati tester. Maybe the automatic tester could be also added to CMake and...

> For cases where the preprocessor is not being used for conditional selection of a programming environment but to expand a template or allow for single-file source with documentation and...

Thanks @urbanjost for the `class` example. I like `class` and use it for some specific things. However, I would argue against it for the implementation of `mean` for mainly three...