Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release candidate fpm.F90 uses gfortran-specific backslash line continuations #1023

Closed
sscalpone opened this issue Apr 24, 2024 · 1 comment · Fixed by #1024
Closed

Release candidate fpm.F90 uses gfortran-specific backslash line continuations #1023

sscalpone opened this issue Apr 24, 2024 · 1 comment · Fixed by #1024
Labels
bug Something isn't working

Comments

@sscalpone
Copy link

Description

I pulled fpm.F90 from the Fpm version v0.10.1 pre-release.

The fpm.F90 source uses backslashes as continuations for a few lines. This behavior seems to be unique to gfortran and then only when preprocessing is enabled.

I used wget to pull this file:

https://github.com/fortran-lang/fpm/releases/download/current/fpm.F90

See the backslashes:

28745     call run('git archive '//ref//' &
28746         --format='//archive_format// &
28747         add_files//' \
28748         -o '//destination, \
28749         echo=verbose, \
28750         exitstat=stat)
28751     if (stat /= 0) then
28752       call fatal_error(error, "Error packing '"//source//"'."); return
28753     end if
28754   end

Expected Behaviour

The code would use standard fortran continuation lines.

Version of fpm

Fpm version v0.10.1

Platform and Architecture

Linux

Additional Information

% cksum fpm.F90
3410678574 1553216 fpm.F90
@sscalpone sscalpone added the bug Something isn't working label Apr 24, 2024
henilp105 added a commit to henilp105/fpm that referenced this issue Apr 27, 2024
@henilp105
Copy link
Member

fixed in #1024.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants