You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a Fortran line is continued across multiple lines and contains a relation that is going to be replaced, linebreaks are not correct and the output is wrong (only tested in one direction, don't see why the other should be ok). Take as example:
adds (or subtracts) characters. So linebreak_pos would need to be updated (or populated later on). But I don't speak enough Python to see how to fix this right now.
The text was updated successfully, but these errors were encountered:
This is a sort of brute-force workaround to avoid fortran-lang#153. Likely not up to
the standard of `fprettify` but 'works-for-me'.
Test amended to cover the corner case, I think.
dbroemmel
added a commit
to dbroemmel/fprettify
that referenced
this issue
Jul 4, 2023
This is a sort of brute-force workaround to avoid fortran-lang#153. Likely not up to
the standard of `fprettify` but 'works-for-me'.
Test amended to cover the corner case, I think.
If a Fortran line is continued across multiple lines and contains a relation that is going to be replaced, linebreaks are not correct and the output is wrong (only tested in one direction, don't see why the other should be ok). Take as example:
and process via
fprettify --enable-replacements
, then linebreaks will be off by 2 characters. This will produceinstead of
This can break code.
I believe the error occurs because https://github.com/pseewald/fprettify/blob/c177742851f95c6ce6078027719f0edff5db5ad2/fprettify/__init__.py#L1557
is called on the original lines, while the following https://github.com/pseewald/fprettify/blob/c177742851f95c6ce6078027719f0edff5db5ad2/fprettify/__init__.py#L1561-L1562
adds (or subtracts) characters. So
linebreak_pos
would need to be updated (or populated later on). But I don't speak enough Python to see how to fix this right now.The text was updated successfully, but these errors were encountered: