From: Arjen M. <Arj...@de...> - 2016-01-21 07:43:59
|
Hi Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > > I was pretty proud of that implementation, but there is a "slight" problem with it > which is it does not work! :-( > Well, the idea was a good one, pity about the failure. > So the question is whether this peculiar behaviour is due to a gfortran bug or due to > an issue with the Fortran standard for disambiguation, and I hope you will continue > to pursue that question with your Fortran contacts. > > Meanwhile, I will throw away the above "good" idea and continue with the (double- > precision only) status quo for plstransform (and plslabelfunc). > I know of one way to solve this: the procedure arguments should be functions that return data of a distinguishable type. For instance: the transform callback should return the new coordinates as an array of two reals (either single or double precision). That is much less natural for the label function. We could require that that too returns some single/double precision value, for instance the argument that came in, but it feels like a kludge. The whole thing is evolving - in Fortran 2015 more is possible (currently there is a thread on the Intel Forum where this is discussed), but that is no solution for the moment. In view of all this, I think we should either use the "only double precision" solution or go for the function solution, however kludgy that feels. 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. |