scsh-users
[Top] [All Lists]

Re: Object IDs are good ( was: Object IDs are bad )

To: scsh-news@martigny.ai.mit.edu
Subject: Re: Object IDs are good ( was: Object IDs are bad )
From: doylep@ecf.toronto.edu (Patrick Doyle)
Date: Tue, 29 Apr 1997 18:09:36 GMT
Organization: University of Toronto, Engineering Computing Facility
In article <izpvvgcn5a.fsf@mocha.CS.Princeton.EDU>,
Matthias Blume <blume@mocha.cs.princeton.edu> wrote:
>In article <E9AxB1.7nA@ecf.toronto.edu> doylep@ecf.toronto.edu (Patrick Doyle) 
>writes:
>
>   In article <izhggvrukk.fsf@mocha.CS.Princeton.EDU>,
>   Matthias Blume <blume@mocha.cs.princeton.edu> wrote:
>   >
>   >   - Things that _actually_ look the same in each and every
>   >     respect_are_ the same.  Things that we can distinguish between
>   >     do _not_ look the same (by definition -- this is what we mean by
>   >     being able to distinguish).
>
>   I wouldn't necessarily agree.  The difficulty lies in mutable objects.  If
>   I have two mutable objects, alike in every way, and I change one, then the
>   other doesn't change.  [ ... ]
>
>Sorry, you are right, but you missed my point.  If there is an
>operation (here: modify one object and observe the change -- or
>rather: non-change -- in the other), that lets you distinguish between
>the two things, then they don't look the same (and never did).  It's a
>matter of what one means by "they look the same".

  Sounds a bit Orwellian to me.  :-)

>And moreover, if the language has both mutable _and_ immutable things,
>then it should support the concept of identity for the former and not
>for the latter.  Since that was what started the thread: ML is such a
>language, and it gets this issue exactly right.

  Interesting.  I must look into that language.

 -PD
-- 
--
Patrick Doyle
doylep@ecf.utoronto.ca

<Prev in Thread] Current Thread [Next in Thread>