Bálint Aradi

Line length should be chosen IMHO by considering, what is the longest line length you can easily still scan with your eyes. I made good experience with 80 and 100...

> The foreign preprocessing notation in the example is horrifying. There is a template proposal before WG5 that would make this sort of awkwardness unnecessary. In general, a coding style...

@certik I could try to have a look at it (although I am not experienced with the CI in GitHub), but not earlier than end of next week...

@urbanjost The plan is to "ship" the library with the preprocessed proper Fortran standard files. The repository, however, should contain the sources with the un-preprocessed files. Otherwise, you get crazy...

@urbanjost Thanks for the example! Your approach is quite elegant and much shorter than the preprocessed version, I agree! One big disadvantage of any `class(*)` based solution is, however, that...

If there is interest, I am happy to clean it up a bit, so that it meets the stdlib coding standards. :wink:

Sure, I opened a separate issue for this (#220)

@MarDiehl Looks good to me. I'd propose to use `dir` instead of `directory` though (consistently everywhere) as "directory" is a very long word... @certik I really like your idea as...

I'd suggest to go with something more general, which allows also relative error. I like quite a lot [Numpy's isclose() function](https://docs.scipy.org/doc/numpy/reference/generated/numpy.isclose.html) which enables to specify both, absolute and relative error....

Indeed, currently that is not possible. Include events are handled during parsing, before any evaluation of variables or even conditionals. For example ``` #:if defined("INCLUDE_ME") #:include "me" #:endif ``` would...