Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28446 Discussions

error #5082: Syntax error, found ',' when expecting one of: => = . [ % (

ab1
Beginner
7,935 Views

I have following error while compliing codes using ifort.

 

error #5082: Syntax error, found ',' when expecting one of: => = . [ % (
           icalir(iIR), ipw, enev(iene)
----------------------^
xyx.f90(285): error #5082: Syntax error, found END-OF-STATEMENT when expecting one of: ] ,
           icalir(iIR), ipw, enev(iene)
---------------------------------------^
compilation aborted for xyz.f90 (code 1)
make: *** [xyz] Error 1

the part of code is reproduced below.

 

             ALLOCATE (icalir(nirs))

             CALL INT_VOL(icalir(iir),np,nstab,ek)
 
!-----------------------------------------------------------------------
!**** Create file for Chase int.
!
     do i=1,np
       write(91,'(4e19.10)') (km(i,j),j=1,np)
     end do
!-----------------------------------------------------------------------
 
!-----------------------------------------------------------------------
!**** Create file for poly
!
      lwrite=17
      ipw=ioffl(lwrite+1,icalir(iir))-1
      write (90+iene, '(2i10, e16.8)')
     $      icalir(iir), ipw, enev(iene)
      do i = 1, ipw
        write (90+iene, '(e20.10, 3e19.10)') (km(j, i),j = 1, ipw)
      end do

how to overcome. what should i write in my codes

 

ab

0 Kudos
1 Reply
jimdempseyatthecove
Honored Contributor III
7,934 Views

The source file being compiled is named xyx.f90
File types of .f90 are free form.

The line bolded in your pasted code, (please use {...} button to paste sample code)
is not a continuation line in free form. It may have been a continuation line in fixed form, when the source file was named xyx.f

 write (90+iene, '(2i10, e16.8)') & ! The ampersand indicates line to be continued
           icalir(iir), ipw, enev(iene)   ! first non-comment line is continuation line

See the IVF documentation to see rules for continuing long character literals.

Jim Dempsey

0 Kudos
Reply