(j3.2006) (SC22WG5.4411) [ukfortran] WG informal ballot
N.M. Maclaren
nmm1
Wed Mar 9 17:39:57 EST 2011
On Mar 9 2011, Van Snyder wrote:
>
>8. [5.2.1p3 9:19-21] Is there a good reason to prohibit a C source file
>from having any identifiers other than the ones gotten from
>ISO_Fortran_binding.h to begin with CFI_? A "google" search for "CFI"
>returned 6,320,000 results, so it is conceivable that a pre-existing C
>file might have identifiers beginning with CFI, and then someday need to
>be interoperable. For example, at http://www.gocfi.com we see "CFI
>provides Enterprise Asset Management, Computerized Maintenance
>Management System, Archibus, CMMS Software,...." If possible, delete
>this paragraph.
The reason is that not doing that means that any future extension
will break at least some valid C code. Worse, at least some valid
C code will change meaning, but not get a diagnostic.
It's a pain, I agree, but such restrictions are normal practice in
C interfaces, for that very reason. People have learnt from the
experience of not doing it!
Regards,
Nick.
More information about the J3
mailing list