Chris MacMackin

No, it doesn't do anything like that. It might be possible to filter/modify the source-code accordingly if you can design a regular expression which can pick out URLs. On 20/08/18...

This should be pretty trivial to implement. I'll add that as a feature with the next round of bug fixes.

This is unlikely to change until we have a new parser which can provide accurate source location information. Unfortunately a recent application for funding to develop such a parser was...

Ah. This had been a suggestion in the original feature request for the warnings. However, due to the way in which FORD processes files, this is nontrivial. The problem arises...

The 100-character width is just what fits on the page--it wasn't a conscious choice. I'll look at allowing custom display behaviour in the next feature release.

I can see the benefit of documenting namelists. However, I think it might be better to place the doc-comments around the actual namelist declaration. Internally FORD could then pull in...

That isn't desirable behaviour. However, I can't seem to reproduce it. Can your provide a reproducer?

Well, they're not volatile in the sense that they don't have the `volatile` attribute. But yes, they only exist inside the block. On 15-12-22 12:49 AM, Stefano Zaghi wrote: >...

I think for the upcoming release I'm just going to make FORD ignore variables declared in block constructs. I'll keep this thread open, though, in case anyone can suggest something...

By aliasing, do you mean the `associate` construct? As far as I could tell from the standard, the `block` construct is only for temporary variables. From what you're saying, it...