On Mon, Dec 15, 2008 at 12:00 PM, chromatic <[email protected]> wrote: > On Monday 15 December 2008 08:08:12 Will Coleda wrote: > >> > Thanks to chromatic, we know what the problem is. >> > In short: >> > Subs need to use ATTRs >> > >> > The fix is pretty invasive, its NOT going to get fixed pre-release. >> >> Can we back out the change that introduced the problem instead? > > We could put a guard clause in the NameSpace PMC never to call PMC_sub() on > anything that's a PMCProxy or ParrotClass instead, at least temporarily. > > -- c >
Would that avoid my problem? If so, great, and we can potentially remove it later if things are fixed the right way. (We should note so on the ticket if we add code we expect to remove later.) To respond to a previous email from Kevin; As a HLL implementor (as opposed to any of the parrot hats I wear) I don't really care that the particular patch didn't *cause* the problem, but I do very much care that it *exposed* the problem. It's a distinction without a difference from a non-core developer's standpoint. It may have only happened to work before, but it *did work before*, on all of parrot's core platforms. I'd *really* like partcl to be able to target parrot releases, rather than a particular SVN revision. (Unless that revision is much closer to HEAD than it is now.). Regards. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
