On 2016-04-28 06:35-0000 Arjen Markus wrote: > Hi Alan, Wadud, > >> -----Original Message----- >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] >> Sent: Wednesday, April 27, 2016 11:22 PM >> To: Wadud Miah >> Cc: Arjen Markus; plplot-devel@lists.sourceforge.net >> 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. That argument sounds reasonable to me, but you are the expert here. So please implement this further change yourself. >> @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. I look forward to those comprehensive test results on both platforms. You can constrain those tests to just test the Fortran, C, and the ps device driver components of PLplot (with the script arguments I have indicated) for speed because even that limited result should thoroughly test creating temporary files. I recommend you make that further change you outlined above before these constrained comprehensive tests so you can summarize these tests in the Tested by: paragraph in the commit message. Once I see that commit from you, I plan to follow up by redoing my own constrained Fortran comprehensive test (since it only takes 7 minutes). Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
