3 ms·
I suggested intersection format for the code generator part. Also, there is a huge amount of legacy code flying around. Write the fixed form parser as soon as
by gus_massa 8y ago
I suggested intersection format for the code generator part.
Also, there is a huge amount of legacy code flying around. Write the fixed form parser as soon as you can.
An example of legacy code with linenumbers is: (Extracted from real code, I only changed the variable names.)
do 1 i = 1 , n
do 1 j = 1 , n
if(x(i,j).ne.y(I,j)) print*,x(i,j),y(j,i)
1 continue
- certik 8y agoRegarding the fixed-form parser, I think that's a good idea. I just created an issue for it: https://gitlab.com/lfortran/lfortran/issues/82 https://gitlab.com/lfortran/lfortran/issues/82. I see what you mean --- that's just a for loop. I created an issue for it: https://gitlab.com/lfortran/lfortran/issues/83 https://gitlab.com/lfortran/lfortran/issues/83. Thanks for the feedback!
- gus_massa 8y agoI've also seen weird controlflow using linenumbers, I pick an easy but common one. I don't expect that the program can handle all the cases and produce something sane. But most of the cases I saw are easily fixable with an enddo or endif.