From owner-sc22wg5@open-std.org Thu Mar 10 01:08:17 2011 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www2.open-std.org Received: by www2.open-std.org (Postfix, from userid 521) id A601DC178E7; Thu, 10 Mar 2011 01:08:17 +0100 (CET) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 432 seconds by postgrey-1.18 at www2.open-std.org; Thu, 10 Mar 2011 01:08:16 CET Received: from proofpoint2.lanl.gov (proofpoint2.lanl.gov [204.121.3.26]) by www2.open-std.org (Postfix) with ESMTP id B0625C178E4 for ; Thu, 10 Mar 2011 01:08:16 +0100 (CET) Received: from mailrelay2.lanl.gov (mailrelay2.lanl.gov [128.165.4.103]) by proofpoint2.lanl.gov (8.14.3/8.14.3) with ESMTP id p2A1bVwJ018322; Wed, 9 Mar 2011 18:37:31 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by mailrelay2.lanl.gov (Postfix) with ESMTP id 69B1715CB05A; Wed, 9 Mar 2011 17:00:58 -0700 (MST) X-NIE-2-Virus-Scanner: amavisd-new at mailrelay2.lanl.gov Received: from LANLHT01.win.lanl.gov (lanlht01.win.lanl.gov [128.165.4.59]) by mailrelay2.lanl.gov (Postfix) with ESMTP id 5636715CB00D; Wed, 9 Mar 2011 17:00:58 -0700 (MST) Received: from EMAIL01.win.lanl.gov ([128.165.222.165]) by LANLHT01.win.lanl.gov ([128.165.4.59]) with mapi; Wed, 9 Mar 2011 17:00:58 -0700 From: "Rasmussen, Craig E" To: fortran standards email list for J3 Cc: "Van.Snyder@jpl.nasa.gov" , "sc22wg5@open-std.org" Date: Wed, 9 Mar 2011 17:00:57 -0700 Subject: Re: (j3.2006) (SC22WG5.4411) [ukfortran] WG informal ballot Thread-Topic: (j3.2006) (SC22WG5.4411) [ukfortran] WG informal ballot Thread-Index: AcvetjuO3NbleOoNSF64qcJJyrFXgA== Message-ID: <9E4329B4-99C1-479C-AB5F-D25615E93FED@lanl.gov> References: <20110304095000.610DEC3BA01@www2.open-std.org> <20110309215128.C3BFEC178E4@www2.open-std.org> <20110309230125.C204AC178E4@www2.open-std.org> In-Reply-To: <20110309230125.C204AC178E4@www2.open-std.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15,1.0.148,0.0.0000 definitions=2011-03-09_09:2011-03-09,2011-03-09,1970-01-01 signatures=0 Sender: owner-sc22wg5@open-std.org Precedence: bulk I'm with Nick on this one. -craig On Mar 9, 2011, at 3:39 PM, N.M. Maclaren wrote: > On Mar 9 2011, Van Snyder wrote: >>=20 >> 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. >=20 > 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. >=20 > 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! >=20 > Regards, > Nick. >=20 > _______________________________________________ > J3 mailing list > J3@j3-fortran.org > http://j3-fortran.org/mailman/listinfo/j3