Bryan Olson <[EMAIL PROTECTED]> writes:
> Mike Meyer wrote:
>> Bryan Olson writes:
>>>[EMAIL PROTECTED] wrote:
>>>
>>>>The reason is that I am still trying to figure out
>>>>what a value is myself. Do all objects have values?
>>>Yes.
>> Can you justify this, other than by quoting the manual whose problems
>> caused this question to be raised in the first place?
> The Python manual's claim there is solidly grounded. The logic
> of 'types' is reasonably well-defined in the discipline. Each
> instance of a type takes exactly one element from the type's
> set of values (at least at a particular time).
References?
>>>>What the value of object()? A few weeks ago I turned
>>>>to that page for enlightenment, with the results I reported.
>>>I think type 'object' has only one value, so that's it.
>> In that case, they should all be equal, right?
>>>>>object() == object()
>> False
>> Looks like they have different values to me.
> Whether the '==' operation conforms to your idea of what equality
> means is unclear.
Care to say what it does mean, then?
> Maybe I was wrong, and the object's identity
> is part of its abstract state.
Is abstract state always part of the value?
>> Or maybe an object is valueless, in spite of what the manual says.
> We know that's not true.
You claim it's not true, but didn't provide anything to back up those
claims, or even alternatives to explain the apparent discrepancy in
behavior.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
--
http://mail.python.org/mailman/listinfo/python-list
