Search results

Parsing error with names starting as: "DO_" (Fortran_2003)

Status: Open.

#313 In camfort/fortran-src;

· NicolasAnquetil opened on Jul 4, 2025

Support legacy mode constructs but in free form lexing (Fortran 90)

Status: Open.

#307 In camfort/fortran-src;

· dorchard opened on Apr 1, 2025

[meta issue] preserving syntax trivia and comments

Status: Open.

#306 In camfort/fortran-src;

· smoothdeveloper opened on Mar 7, 2025

support for deprecated or proprietary constructs? <code>record //</code> and <code>structure //</code>.

Status: Open.

#303 In camfort/fortran-src;

· smoothdeveloper opened on Feb 15, 2025

Improve parse and lexing errors, especially for cases involving module files.

Type: Enhancement

Status: Open.

#297 In camfort/fortran-src;

· dorchard opened on Jan 14, 2025

Add pre-built binaries.

Status: Open.

#296 In camfort/fortran-src;

· dorchard opened on Jan 14, 2025

fortran-src-0.16.3 testsuite failed on stackage nightly

Status: Open.

#293 In camfort/fortran-src;

· juhp opened on Oct 21, 2024

Failed to parse this statement: <code>write(6,'(10(e12.5,a))') ((array(i),' '), i=1,nb)</code>

Status: Open.

#281 In camfort/fortran-src;

· uNouss opened on Jan 23, 2024

Use '.' to separate scope from variable name instead of '_'.

Status: Open.

#280 In camfort/fortran-src;

· dorchard opened on Nov 17, 2023

Why is renaming under <code>Analysis</code> and not <code>Transformation</code>?

Status: Open.

#279 In camfort/fortran-src;

· dorchard opened on Nov 17, 2023

DOUBLE COMPLEX is not understood, COMPLEX*16 works

Status: Open.

#278 In camfort/fortran-src;

· dmikushin opened on Nov 16, 2023

Parsers likely contain list span mistakes

Status: Open.

#277 In camfort/fortran-src;

· raehik opened on Jul 28, 2023