On 2014-10-13 08:05-0000 Arjen Markus wrote:
> [...] I would say, let's go for this [third argument of size] amendment. If
> some compiler out there
does not like it, there is a workaround possible, though I'd rather
not have to go that route :).
Hi Arjen:
Thanks for that clear direction including the suggested modification
of the change that will be required for the substantial subset of the size
cases that currently only have one argument. I will follow
exactly what you have suggested.
Also, I need further guidance on something else.
Could you comment on the backwards-incompatible changes in
module names that I have implemented? Those are the following:
plplot_types ==> plplot_graphics
plplot_flt ==> plplot_types
I assume a very small subset of our fortran users will be affected by
the first one, but I am a little concerned about the second one, and
if you think a substantial fraction of our fortran users were using
the explicit "use plplot_flt" rather than generic "use plplot", the
option exists to perpetually (ugh) keep the plplot_flt misnomer around
(which means an extra mod file to install indefinitely). I assume
that implementation would simply be
module plplot_flt
use plplot_types
end module
Anyhow, let me know what you think, and I will implement the above or
not depending on what you say.
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
__________________________
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel
