Re: small numerical differences in floating point result between

Rich Townsend <rhdt@barVOIDtol.udel.edu> writes:

> However, I remain very surprised that the *private*
> components of a derived type can be accessed in this (nonportable)
> manner.

Don't mistake the PRIVATE attribute as having anything to do with
protecting things from malicious attack.  It doesn't.  That's just
not what it is about and it is not even close to an appropriate
design for such purposes. I've had to remind even people on J3
of this, when some proposals were criticized as opening PRIVATE
data up to attack.  It is already wide open; there's no door to
close.

The PRIVATE attribute helps in managing namespace issues.  And
it helps avoid some significant classes of mistakes.  If you think
that it has anything to do with security against intentional
subversion... then I hope you aren't writing security-sensitive
code.  :-(

--
Richard Maine                       |  Good judgment comes from experience;
email: my first.last at org.domain  |  experience comes from bad judgment.
org: nasa, domain: gov              |        -- Mark Twain