Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
F
f2cl
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • f2cl
  • f2cl
  • Issues
  • #4

Closed
Open
Opened Nov 22, 2018 by Raymond Toy@rtoyOwner

PARAMETER variables may be arranged incorrectly

PARAMETER variables may not be arranged correctly. This may require some hand-tweaking of the output lisp file. This manifests itself if the value of a PARAMETER variable is computed from the value(s) of other PARAMETER variables.

The order is not important in Fortran, but when converted, the order is important in Lisp. Sometimes f2cl gets it wrong. Reordering the PARAMETER variables in Fortran will usually make it work for Lisp.

(From https://trac.common-lisp.net/f2cl/ticket/3)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: f2cl/f2cl#4