> I've just noticed that KAPPA parget does not give you double precision
> numbers from _DOUBLE parameters.
I'll be surprised if it's always been that way. That's one of the
obvious checks.
> at parget.f this seems to be because dat_get1c is used. HDS seems to be
Unfortunately, I didn't document why the character conversions were
used. Convenience of not have to obtain the type and have lots of if
then else if clauses.
It seems to me the change should be in HDS.
> (and making the above change does actually lead to PARGET giving me the
> double precision value). Is the fear that the added precision will lead to
> buffer overflows?
If there is a good reason not to change the sprintf for the DAT__R case,
we could modify PARGET or have an HDS tuning parameter to control the
precision. I certainly want PARGET to report _DOUBLE values with
adequate digits for the precision.
> In that case I'd have to patch parget to do a get1D
> instead of get1c in the special case.
PARGET could also have a PREC parameter (defaulting to _DOUBLE) to
specify the reported precision of _DOUBLE values, in case you don't want
lots of digits.
Malcolm
|