Ivan Pribec

Thanks @everythingfunctional for the explanation. I suggest we shift to #249 to figure out a specification.

The discussion in #249 suggested we separate between one-way and two-way build scripts. *This* issue is for one-way build scripts. The suggestion from @awvwgk was to use the following manifest...

> > Where should the archives be placed? Should it be a sub-folder in `/build/_/` meaning the build script would receive an environment variable with the output folder name? Cargo...

Would this imply the convention that a simple build script only produce one library (archive)? Or are you referring here to an `fpm` package as it's own entity. Concerning your...

In some way the problem of free- and fixed-form is really just a problem of language classification. Given the large strides made in [natural language processing](https://en.wikipedia.org/wiki/Natural_language_processing) (NLP) in the past...

Down the road this would break most of Fortran syntax highlighting. At least during a short transition period (likely on the order of decades), code editors would become forced to...

> You can't reliably auto-detect - it is possible to write code that is correct whether you interpret it as free form or fixed form. I realize such cases might...

Upon reading some more about programming language classification, the most likely useful feature used to separate between the two forms are comments (`C` vs `!`). Since the language tokens are...

Can you clarify how would TAP be detected automatically? I presume the test main program would import the module definitions with `use tap` (or `use fpm_tap` if we could implement...

That sounds reasonable, but I don't think the interest in TAP among all FPM users will be big enough to make it enabled by default. The explicit approach sounds better...