On Wed, Jan 23, 2002 at 09:57:49PM +0100, Juergen Boemmels wrote:
> Ok, here is the updated schemepair-patch.
Thanks for this, but I'm afraid I'm not going to apply it. The reason
being:
> To implement nested pairs its nessary to introduce 2 new vtable functions
> and the acompaning core.ops to get and set the PMC value of the indexed
> element. I choosed set_p_p_i and set_p_i_p. The later one is inconsistent
> with indexed set operations set_p_i_i, set_p_n_i and set_p_s_i.
This isn't how we're doing indexing. Unfortunately, I'm still trying to
catch up on how we are doing indexing. There should certainly be indexed
versions of many of the PMC vtable entries, but I can't remember what
form this index would take. IIRC, it should be a KEY* structure, but I
may not RC. Anyone know where we got to?
--
"Rohypnol offers YOU the chance to see what your sex life will be like
after 10 years of marriage! Try it now and save the divorce money."
- Janet McKnight
