Re: 'constant functions' and access constant params (was Re: Array of Variant Records Question...)

["Matthew Heaney" <matthew_heaney@acm.org>]

In article <wcchfkk2ocx.fsf@world.std.com> , Robert A Duff 
<bobduff@world.std.com>  wrote:

> "Matthew Heaney" <matthew_heaney@acm.org> writes:
>
>> 2) For private types, I say the "stability of X" is a meaningless statement.
>> A supplier's only obligation is to satisfy the postcondition, which has
>> nothing to say about internal state changes.
>
> Please define exactly what you mean by "internal" state change.

External = public state  = partial view of type
Internal = private state = full view of type

For example, in Ada.Text_IO, the type is declared as

  type File_Type is limited private;

There is no external state.  The only thing I know (publicly) about File_Type
is what operations are available for it.

You could loosely refer to selector functions like Name or Is_Open as "external
state," but I'm not doing that here.  In a postcondition, I would state what
values those functions should return, but that's not quite what I mean by
external state (it's more like external "behavior").


> How can one tell the difference between internal and external
> state changes?

For a private type, there is no such thing as "external state," so this
question goes away.

Actually, that's a bit of a lie, since I could declare a tagged type this way:

  type T_Public is
    abstract tagged limited record
      I : Integer;
    end record;

  type T is
    new T_Public with private;

Here, objects of type T have some state that's external, namely component I.
But then it's easy to say what happens to the external state (I) in the
postcondition.


--
It is impossible to feel great confidence in a negative theory which has always
rested its main support on the weak points of its opponent.

Joseph Needham, "A Mechanistic Criticism of Vitalism"