J3/99-274r2 Date: 1999/12/3 To: J3 From: /interop Subject: Issues 87 and 88 Edits and references are to J3/99-007r2. Issue 87: [84: 18-27] Issue 88: [88: 16-25] This paper discusses issues related to argument passing between Fortran and C. 1. Issue 87 Issue 87 mentions that part of the description of the VALUE attribute might be better put in the form of a constraint, since it is compile-time checkable. The constraint is added to the section on the VALUE statement and to the general section on the type declaration statement. Edits: [84:15-16] Delete first sentence of paragraph. [88:13+] Add: Constraint: The VALUE attribute shall be specified only for a scalar dummy argument of a subprogram or interface body that has a . [71:19+] Add: Constraint: The VALUE attribute shall be specified only for a scalar dummy argument of a subprogram or interface body that has a . [84:18-27] Delete J3 note 2. Issue 88 Editor proposes to delete constraints, which are already covered by a syntax-rule. This implies that syntax rules are diagnosed by the processor. Edits: [88:14-15] Delete [84:42-43] Delete [85:8-9] Delete [88:16-25] Delete J3 note 3. Misc. Section 16.2.6 has missed one requirement on interoperation between Fortran procedures and C functions, viz. that dummy arguments are not allowed to have the OPTIONAL attribute. The list item needs also to be converted to explicit constraints. Edits: [85:7+] Constraint: The shall not be a dummy argument of a subprogram or interface body that has a . [86:45+] Constraint: The shall not be a dummy argument of a subprogram or interface body that has a . [87:11+] Constraint: The shall not be a dummy argument of a subprogram or interface body that has a . [410:15-16] Delete ", none of which have either the POINTER or ALLOCATABLE attribute"