Mitchell N Charity wrote:
(3) A new reflector/reference class.
void set_integer_native (INTVAL value) {
PMC *object_reflected = SELF-cache.pmc_val;
object_reflected-vtable-set_integer_native(...);
}
Question ONE - What parts of the above code, if any, need to be
changed,
Just so everyone doesn't have to go digging through the archives...
Here are links to the postings, and some extracts which seemed to
provide context for the current thread.
http://nntp.x.perl.org/group/perl.perl6.internals/12804
http://nntp.x.perl.org/group/perl.perl6.internals/12809
Mitchell N Charity wrote:
On a minor note, re
CALL_VTABLE_0(meth, interp, pmc)
CALL_VTABLE_1(meth, interp, pmc, arg1)
CALL_VTABLE_2(meth, interp, pmc, arg1, arg2)
I suggest reordering arguments to
CALL_VTABLE_1(interp, meth, pmc, arg1)
or CALL_VTABLE_1(interp, pmc, meth, arg1)
, to be sure the list archives catch it? Thanks.
Ok inlined here.
#include stddef.h
#include stdlib.h
#include stdio.h
#include malloc.h
/* test program, showing:
*
* - PMC/Buffer unification
* - variable/value vtable split
* - tied access to scalars
*
* compile and run like e.g. so:
*
* cc -Wall -o tt
Regards
base_vtable ... name, type, ...
var_vtable ... get_integer, set_integer, ...
val_vtable ... add, sub, ...
prop_vtable ... property functions (set/getprop are different, depending
on the existence of the property hash)
I think this might rephrase as
cite author=Dan date=2002-09-23
subject=Of variable, values, and vtables
...
*) Spec the vtable changes
...
The variable/vtable stuff should be done in the next day or two.
/cite
More threads with $subject:
- Variable/Value split prelims
- [RFC] Buffer/PMC unification, variable/value split,
On Mon, Dec 30, 2002 at 04:36:31PM +0100, Leopold Toetsch wrote:
- a variable consists of 3 parts: name, variable, value
- the 2 latter are now handled in one go in our vtable funcs
- variable and value access should be separate operations (think tie)
- 2-stage access
Nicholas Clark wrote:
base_vtable ... name, type, ...
var_vtable ... get_integer, set_integer, ...
val_vtable ... add, sub, ...
prop_vtable ... property functions (set/getprop are different, depending
on the existence of the property hash)
The vtable pieces and the _vtable
2)
Variable/value VTABLE split
As layed out by Dan, the access to a value inside a PMC has - in the
general form - to be done in 2 separate steps:
- get the variable PMC (+ handle side effects like tied variables)
- get the value out of this PMC
The same rule holds for setting a value inside a PMC
Leopold Toetsch wrote:
Attached is a test program showing some features, how a PMC could look
like in the future.
and where's the attachment?
cheers,
Aldo
__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;
Leopold Toetsch wrote:
Attached is a test program showing some features, how a PMC could look
like in the future.
Arg mozilla did show it.
11 matches
Mail list logo
