ludovic.cour...@inria.fr (Ludovic Courtès) skribis:
> manuel.serr...@inria.fr skribis:
>
>>> Problem is that objects may have a different ‘hop_serialize_context_def’
>>> property, yet be otherwise equal at the Scheme level.
>>>
>>> Shouldn’t the above code skip ‘hop_serialize_context_def’, and perhaps
>>> ‘hop_serialize_context_key’?
>> I don't know. What is the meaning of equal? if the object are not really
>> equal?. The more I think about it, the less I think it makes sense to
>> implement equal? for plain JavaScript objects. It is important to have
>> equal? for Hop class instances but for plain JS objects, I really don't know.
>
> No I’m only concerned about ‘equal?’ for Scheme objects used on the
> client side.
>
> Shouldn’t ‘sc_isEqual’ skip special properties like
> ‘hop_bigloo_serialize_object’ does? That is:
>
> for( var p in item ) {
> if( p !== "hop_bigloo_serialize" &&
> p !== "hop_classname" &&
> p !== "hop_circle_forced" &&
> p !== "hop_serialize_context_key" &&
> p !== "hop_serialize_context_def" &&
> p !== "hop_classhash" ) {
> len++;
> args += hop_bigloo_serialize_context( item[ p ] );
> }
> }
Any update on that one?
Thanks,
Ludo’.
