On 2011-01-27 16:14+0100 Arjen Markus wrote: > Hi Alan, > > the way to get the desired bit pattern is (for instance): > > integer, parameter :: PL_FCI_MARK = ishft(1,31) > > It shift the single bit of 1 into the 32nd position leaving > a trail of zero bits. (It should even work on ones-complement > machines, though I do not think I have ever been close to > one and knew about it.)
As of revision 11513; I have checked in the sed script, a change in the CMake logic to create a (Unix) custom target called check_f95_parameters to use that sed script to check that f95/plplot_parameters.h was consistent with the #defines in bindings/swig-support/plplotcapi.i, and a consistent version of f95/plplot_parameters.h. In the sed script I have used the above ishft(1,31) suggestion to generate PL_FCI_MARK as a parameter that is now available to our Fortran 95 users. In revision 11514 I added descriptions in README.release of the Fortran 95 work (and also future Fortran 77 work) to make PLplot constants available for Fortran users That commit should terminate my current Fortran 95 work unless you (or anyone else) finds a compiler that doesn't like either the ishift or BOZ form of parameter statements. The other trailing issue for Fortran 95 is that the following parameters (taken from a subset of a recent diff) - integer, parameter :: PL_JUST_NONE = -1 - integer, parameter :: PL_JUST_OPTIMAL = 0 - integer, parameter :: PL_JUST_SAME = 1 - integer, parameter :: PL_JUST_ISOMETRIC = 2 - - integer, parameter :: PL_AXIS_NOTHING = -2 - integer, parameter :: PL_AXIS_BOX_ONLY = -1 - integer, parameter :: PL_AXIS_NORMAL = 0 - integer, parameter :: PL_AXIS_ATZERO = 1 - integer, parameter :: PL_AXIS_MAJORGRID = 2 - integer, parameter :: PL_AXIS_MINORGRID = 3 - integer, parameter :: PL_AXIS_LOGX = 10 - integer, parameter :: PL_AXIS_LOGY = 20 - integer, parameter :: PL_AXIS_LOGXY = 30 - - integer, parameter :: PL_FONT_STANDARD = 0 - integer, parameter :: PL_FONT_EXTENDED = 1 are no longer available to our Fortran 95 users. They were never used in our examples so I don't think this change will have a bad impact on our users. However, bindings/f95/readme_f95.txt does document some of these so at one point at least you felt some of these dropped parameters might be important. If you still feel that way, I suggest you make the appropriate documented #defines in include/plplot.h and bindings/swig-support/plplotcapi.i so they are automatically available for C, C++, python, java, lua, octave, and Fortran 95. (Also Fortran 77 once I create the appropriate sed script and check_f77_parameters target in that case as well). At the same time, you will probably want to update bindings/f95/readme_f95.txt to simply refer to the documentation of the various constants that are #defined in include/plplot.h and bindings/swig-support/plplotcapi.i. 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); PLplot scientific plotting software package (plplot.org); 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 __________________________ ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel