Skip to content

Define SUBROUTINE and FUNCTION argument typespec explicitely in HELP #24

@jnsebgosselin

Description

@jnsebgosselin

As mentionned in #22 (comment), arguments of each SUBROUTINE or FUNCTION should be explicitly defined. This is to avoid warning or the type vars2fortran: No typespec for argument "nt". Block: leap when compiling with f2py.

For example, the SUBROUTINE READIN does not produce such a warnings.

C      ************************* READIN *************************
C
C  SUBROUTINE READIN READS ET AND SOIL DESIGN DATA, AND WEATHER HEADERS
C
      SUBROUTINE READIN (fpath_precip, fpath_tasavg, fpath_solrad,
     1 fpath_evapo, fpath_soil)
      
      CHARACTER(len=260), INTENT(IN) :: fpath_precip
      CHARACTER(len=260), INTENT(IN) :: fpath_tasavg
      CHARACTER(len=260), INTENT(IN) :: fpath_solrad
      CHARACTER(len=260), INTENT(IN) :: fpath_evapo
      CHARACTER(len=260), INTENT(IN) :: fpath_soil

So I think this can be safely ignored for the moment.

Metadata

Metadata

Assignees

Labels

tag: HELP modifsWhen a PR or Issue inply changes to the FORTRAN base code of HELPtype: bugSomething isn't working

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions