Re: Entity and Identity

Nilone wrote:

[...]
>> So what is your alternative for expressing dynamics (behavior)
>> in a disciplined,maintainable  way?  Is a big bag of procedures
>> that can query and update arbitrary data as they please *better*?
>>
>> --
>> Reinier
>
>I've already accepted that OO classes are appropriate for creating
>state machines, hence I'm not offering alternatives. Note that "a big
>bag of procedures that can query and update arbitrary data as they
>please" is an unfair characterization of procedural programming,
>similar to "a big bag of objects that can query and update each other
>as they please".

My question is: how do you propose to organize them? Do you agree that some disciplining in how code can access objects is required? What do you propose code should look like (you write 'relational all the way', what does relational GUI code look like - not that I can't imagine any).

-- 
Reinier