Re: caching on MPI handles

Eric Salo (salo@mrjones.engr.sgi.com)
Fri, 18 Oct 1996 14:37:31 -0700

>> 1) An attribute is cached on Datatype A
>> 2) Datatype A is used to create Datatype B
>> 3) The value of the attribute on Datatype A is altered.

> The behavior is what we define it to be. I will happily define it to
> be the simplest possible: The first time Datatype B is created, the
> behavior is defined by the copy function specified with the
> attribute. From then on, any changes to the attribute on Datatype A do
> not automatically get reflected on Datatype B.

I didn't think this would work, but now I can't remember why...

Are there any cases for which a non-null copy_fn would even be useful? If I
understand you correctly, all you really care about is the delete_fn, right?

-- 
Eric Salo         Silicon Graphics Inc.             "Do you know what the
(415)933-2998     2011 N. Shoreline Blvd, 8U-802     last Xon said, just
salo@sgi.com      Mountain View, CA   94043-1389     before he died?"