[cffi-devel] Re: %expand-type-to-foreign-dyn vs *runtime-translator-form*

Stephen Compall <s11@member.fsf.org> writes:

Wed Mar 15 12:48:04 CST 2006 Stephen Compall <scompall@nocandysw.com> * remove *runtime-translator-form* from the effective interface

Ok, so this looks good. I think I like using (call-next-method) instead of the *runtime-translator-form* special. This patch fails misc-types.expand.{1,2} though since these expect expand-to-foreign-dyn to use expand-to-foreign. As I mentioned before, I kind of like that behavior. Can you convince me that it's a bad idea? :-) -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt