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
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
o
Hi Alan,
I get an error message with gfortran 4.6, but not with ifort.
The value is -2147483648, which is the largest negative number
that actually fits into a 32-bits twos-complement integer.
I think this is a bug in gfortran:
setting PL_FCI_MARK to -2147483647 and then printing PL_FCI_MARK-1
g
Hi Alan,
I will experiment with these BOZ issues - try a few different
compilers. I almost never use this myself, so I have to do it
the empirical way (which ought to please the physicist in me :)).
Regards,
Arjen
On 2011-01-27 11:11, Alan W. Irwin wrote:
> On 2011-01-27 01:20-0800 Alan W. Irwi
On 2011-01-27 01:20-0800 Alan W. Irwin wrote:
> Hi Arjen:
>
> I have the sed script almost working for f95. The only problematic
> statement generated is
>
> integer, parameter :: PL_FCI_MARK = z'8000'
>
> That z'8000' causes an integer overflow. The problem is that
> z'8000' i
On 2011-01-27 08:42+0100 Arjen Markus wrote:
> Hi Alan,
>
> wow, that is quite a set of changing. Yes, the examples were filled
> with local definitions of parameters like PL_PARSE_FULL and so on.
> Having them in a single include file will make it easier for our users.
> I agree that a similar ro
Hi Alan,
wow, that is quite a set of changing. Yes, the examples were filled
with local definitions of parameters like PL_PARSE_FULL and so on.
Having them in a single include file will make it easier for our users.
I agree that a similar route be taken for Fortran 95, even though we
can rely on t
Hi Arjen:
Recently (i.e., the series of revisions up to revision 11509) I have
made the following changes to the f77 bindings and examples:
* I have taken your idea of having a central place to express
PLplot-related f77 parameters and expanded it. Those parameters now
reside in bindings/f
