Re: more get-slot-value issues

Marco Baringer wrote:
> i'd like to change get-slot-value for sbcl so that it uses the type
> information (currently ignored) and avoids sap-alien allocation where
> possible, i'd like to change get-slot-value for mcl so that it evals
> all of its arguments. hopefully this should allow the same
> uffi:get-slot-value form to work everywhere, however:

On platforms where type information is ignored, the type is embedded in
the object. I've not found sap-alien allocation on SBCL or CMUCL using
CLSQL which makes intensive use of get-slot-value to extract data out
of foreign structions.

> 1) on sbcl we'd only use the type argument when it was a constant and
>    we'd eval it at compile time.

I'm not convinced this is necessary. But, if you supply a patch and
both the UFFI and CLSQL tests suites continue to pass all tests, I'll
certainly consider it for inclusion.

> 2) on mcl we'd do the eval'ing at compile time if both args are
>    constants, otherwise we'll take the speed penatly and do the
>    eval'ing (and intern'ing) at runtime.

That may be possible. I'm least familiar with openmcl's FFI.

> any issues with this? how often are non constant type and slot
> specifiers used with get-slot-value?

I don't use them in any of my UFFI applications. 

> p.s. - is the svn repository up?

No, I'm awaiting a security bug fix for subversion 1.0.6 to migrate to
Debian sarge before reactiving the public svn repository.

-- 
Kevin Rosenberg
kevin-HJRc7zDS/[email protected]