On Sun Mar 16 09:20:55 2008, [EMAIL PROTECTED] wrote:
> On Mon Mar 12 05:40:14 2007, [EMAIL PROTECTED] wrote:
> > I'm still working on my use case, but it appears the new MetaClass PMC
> > (src/pmc/metaclass.pmc) could use this vtable method as well;
currently it
> > only has an add_attribute PMETH
On Mon Mar 12 05:40:14 2007, [EMAIL PROTECTED] wrote:
> I'm still working on my use case, but it appears the new MetaClass PMC
> (src/pmc/metaclass.pmc) could use this vtable method as well; currently it
> only has an add_attribute PMETHOD.
>
Alek, Are you still planning work on this patch? (No
I'm still working on my use case, but it appears the new MetaClass PMC
(src/pmc/metaclass.pmc) could use this vtable method as well; currently it
only has an add_attribute PMETHOD.
On 3/4/07, Alek Storm <[EMAIL PROTECTED]> wrote:
Hmm, no, these deal with normal object attributes. I believe you
Hmm, no, these deal with normal object attributes. I believe you're
thinking of properties. I'll put together some sketch code with what
I already have and post that.
Thanks,
Alek Storm
On 3/5/07, chromatic <[EMAIL PROTECTED]> wrote:
On Sunday 04 March 2007 19:13, Alek Storm wrote:
> In fact
On Sunday 04 March 2007 19:13, Alek Storm wrote:
> In fact, these vtable methods *encourage* the use of many languages in
> a single application. For example, without these methods, programmers
> have to be aware of the semantics of the Smalltalk object system and
> use extra code when dealing wi
The same questions are solved for all PMCs - the vtable provides an
abstracted interface that everyone can use seamlessly. Because tcl
and Java use the same interface (opcodes), there's no problem. I
honestly cannot see a difference between these and any other vtable
method. The fact that Perl
On Mar 4, 2007, at 12:40 PM, Alek Storm wrote:
For the same reason we have set_attr, set_attr_str, get_attr, and
get_attr_str, even though they're only used by ParrotObject - it
allows for
multiple, concurrent object systems. This goal is mentioned in PDD
15, in
"What The Bytecode Sees". Why
For the same reason we have set_attr, set_attr_str, get_attr, and
get_attr_str, even though they're only used by ParrotObject - it allows for
multiple, concurrent object systems. This goal is mentioned in PDD 15, in
"What The Bytecode Sees". Why tie programmers into the default way of doing
thin
Alek Storm (via RT) wrote:
This patch adds the add_attr, rem_attr, and rem_attr_str vtable
methods. These will come in handy for Ruby's metaclasses or
Smalltalk's class objects. The only PMC currently affected by this is
ParrotClass, and the rem_attr and rem_attr_str methods are still
unimplem
Alek Storm wrote:
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #41619]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41619 >
This patch adds the add_attr, rem_attr, and rem_attr_str vtable
meth
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #41619]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41619 >
This patch adds the add_attr, rem_attr, and rem_attr_str vtable
methods. These will com
11 matches
Mail list logo
