On Jan 26, 2006, at 5:35, Chip Salzenberg wrote:
Ah yes, of *course*. PMCs have methods, and the methods need to be
found
somewhere, so the default place to look should be vtable->namespace.
Is there a problem with killing vtable->namespace_name and replacing
its
usages with the existing vt
On Thu, Jan 26, 2006 at 02:12:41AM +0100, Leopold Toetsch wrote:
> On Jan 25, 2006, at 21:21, Chip Salzenberg wrote:
> >On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
> >>*) what is vtable->package? A pointer to the namespace PMC of this
> >>class? (It's currently unused)
> >
> >B
On Jan 25, 2006, at 21:21, Chip Salzenberg wrote:
On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
*) what is vtable->package? A pointer to the namespace PMC of this
class? (It's currently unused)
Beats me. Vtables don't have namespaces. Pleaes just comment it as
"WTF?"
On Tue, Jan 24, 2006 at 05:43:25PM +0100, Leopold Toetsch wrote:
> *) what is Stash.parent_stash? (It's currently unused)
Historically, "stash" is perl5-guts-speak for "namespace". However, I see
in Parrot the Stash structure which seems quite different. From its usage,
I gather it's an attempt
*) what is Stash.parent_stash? (It's currently unused)
*) I presume that the stash_hash is the thing, that holds the top-level
namespace.
*) what is vtable->package? A pointer to the namespace PMC of this
class? (It's currently unused)
*) what is Parrot_Context.current_package? Shoudn't that bet
