Hello, a while back I ran into a problem with gfortran: it boils down to "disjoint" memory between the program and the PLplot DLL. A COMMON block /plplot/ that is defined in the program and in the DLL turns out not to point to the same memory.
As this is a bug in gfortran (there are workarounds, but not within the confines of FORTRAN 77), I have introduced a new routine, plsettransform, to copy the transformation parameters into the COMMON block for later use. This bug does not occur in the Fortran 95 bindings, as we use a different method to transfer the transformation parameters. I am not sure if this workaround should be promoted to be the preferred method, though it does give the opportunity to hide some implementation details that are now blatantly in the user code. Anyway I will commit this change today. 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. ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
