On Thu, Jul 10, 2008 at 06:50:51PM -0700, chromatic wrote:
> 
> Here's a first approach.  It breaks a couple of tests, but it's a start:
> 
> t/pmc/object-meths                 (Wstat: 1280 Tests: 37 Failed: 5)
>   Failed tests:  1-4, 16
> t/oo/proxy                         (Wstat: 256 Tests: 5 Failed: 1)
>   Failed test:  3
> 
> I believe a solution is to make a Class PMC stick the appropriate PMCProxy in 
> its attached NameSpace's class slot when created, but I haven't tested that 
> (and won't have a chance for a few hours).

Okay, that confuses me a bit.  I agree it makes sense to have the 
PMCProxy placed in the attached NameSpace's class slot... but IIUC
a PMCProxy isn't created until it's explicitly requested (e.g.,
via the 'get_class' or 'typeof' opcodes).  I don't think there's
anything that automatically builds PMCProxy objects for all of
the PMC types at initialization (i.e., "when created").

Pm

Reply via email to