From: Arjen M. <Arj...@de...> - 2016-04-28 06:35:13
|
Hi Alan, Wadud, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Wednesday, April 27, 2016 11:22 PM > To: Wadud Miah > Cc: Arjen Markus; plp...@li... > Subject: RE: [Plplot-devel] PLplot Fortran bindings > > To Wadud and Arjen: > > @Arjen: > Since you have been unable to answer my quick question in a timely manner > concerning adopting selected_int_kind(9) rather than 4 for private_plint, > private_plbool, and private_plunicode, I have decided to just go ahead with that > change (commit 3442bac). > Yesterday was a national holiday here, so I paid little attention to my inbox :). However, considering the portability of these two types, why don't we use C_INT32_T from ISO_C_BINDING? This maps to C's int32_t type (for the companion C compiler to be precise). Essentially the same thing, except if the platform does not have 32 bits integers, I'd say, but it conveys the one-to-one relation between the Fortran and C side. This does not rely on the Fortran 2008 standard, only on the Fortran 2003 standard and we require that for the new binding anyway. > > @Arjen and Wadud: I suspect the kind=4 logic we were using before only worked > by a historical accident that that particular kind value corresponded for most Fortran > compilers to the 4-byte integers we desired for these private types. So I am much > more comfortable with the present selected_int_kind(9) fix for that situation, but that > fix does need testing on more than just my (Debian jessie) platform. > Quite possibly, something like unit 5 in Fortran being attached to the keyboard and unit 6 to the console. Nothing that is 100% guaranteerd, but so likely that you begin to think it is guaranteed. > > @Arjen: Could you follow up with similar test results for the latest git master tip for > both your Cygwin and MinGW-w64/MSYS2 platforms? > That wiki table documents your previous (good) Cygwin Fortran result. > Previously you also sent me your good MinGW-w64/MSYS2 platform results for > Fortran, but I was holding off on posting that result to our wiki because that report > also revealed a MinGW-w64/MSYS2 installation update issue that requires you to > reinstall the MinGW-w64/MSYS2 platform to get access to the much more > convenient/reliable updating available for the latest version of that platform. > Will do. I should have time today to do that. That testing should cover the other issue (the temporary files) as well. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |